Operations & Support
Setting Booking Rules for a Shared Laboratory Instrument
Distinguish requests from confirmed slots, record users and duration, and manage shared-instrument schedule changes under laboratory procedures.
Published October 9, 2026
An instrument shared by several teams needs more than an empty calendar. Users need to know whether a slot has merely been requested or approved, who may change it, and how the next team is informed when timing shifts.
Booking rules coordinate time rather than grant technical permission to operate equipment. User authorisation, equipment readiness, and work execution still follow laboratory procedures and instructions applicable to the instrument.
Distinguish scheduling from equipment status
An empty time on the calendar does not prove equipment is ready. The unit may await a manager’s decision or have other activities affecting availability. Connect scheduling with the status assigned by authorised personnel rather than only free calendar cells.
Use a unit code matching the asset register. If two instruments have the same model, the calendar needs to identify the intended unit. A model name alone can direct a request to different equipment.
Identify who updates equipment status and who manages scheduling. These may be the same person or different roles under the organisation’s arrangements. Users need to know whom to ask before assuming a time is usable.
Assign request and approval responsibilities
Define which users may request bookings and through which channel. A request does not automatically mean permission to use the instrument. Where competency or authorisation requirements exist, checks follow the established process.
Assign slot confirmation and explain how users receive an answer. Avoid relying on private conversations invisible to other managers. One status list accessible to authorised users helps keep information consistent.
If certain work has priority, identify the decision owner and handling process. Do not assume first arrival always takes priority when organisational procedures use other considerations. Explain the rule before conflicts occur.
Record enough information to schedule
A request should identify the unit, user, proposed time, and needs affecting the slot. Include information the manager actually requires without placing sensitive job details in a shared calendar that does not need them.
| Information | Coordination purpose |
|---|---|
| Unit code | Identifies the requested instrument |
| User and team | Identifies whom to contact |
| Proposed time | Allows potential conflicts to be checked |
| Estimated duration | Supports allocation appropriate to the work |
| Request status | Distinguishes pending from confirmed |
| Manager contact | Provides a route for changes or questions |
Duration estimates should follow known needs and procedures. Mark uncertainty for discussion. Do not prescribe a universal buffer or completion time; preparation and closing activities differ by instrument and job.
Make changes understandable
Define how to cancel or change a time. Users need to know when to communicate, who receives the information, and when a change counts as confirmed. Sending a message does not necessarily mean the shared schedule has been updated.
A fictional example: team A expects to finish later than planned. They contact the manager before changing team B’s slot. The manager discusses the effect and updates the agreed schedule. This illustrates coordination rather than a universal laboratory priority rule.
Record a brief reason if needed for follow-up. Avoid sharing unnecessary job details. The purpose is to let the next party understand the time’s status and decisions already accepted.
Separate planned and actual use
A booked slot represents a plan. Actual usage records show when work happened under the laboratory’s system. If both are recorded, preserve their separate meanings rather than assuming every slot was used exactly as shown.
Different duration can prompt discussion rather than an immediate conclusion that the user made an error. Ask for context through a manager who understands the process. Recurring needs differing from initial estimates may justify planning changes.
Connect required records with the unit’s documentation system. The WHO equipment-archive guidance provides context for storing equipment records. A shared calendar retains its coordination role rather than replacing all operational records.
Review one conflict example
Use an example of two teams requesting the same time. Check whether the manager can identify the unit, requester, status, and decision route. Also try a cancellation and duration change with sample data without disrupting operational bookings.
If information is difficult to find, improve unclear fields or responsibilities. Avoid extending the form before understanding the confusion. Concise rules people can follow are more useful than many columns without owners.
When discussing shared-instrument requirements with Tri Anugerah Sejati, describe the number of user teams and known usage patterns. That supports procurement and management conversations, while the laboratory remains responsible for booking rules and operational decisions.