Key points
- Identify devices and record issue, condition and return.
- Check the authorised session before using operational information.
- Resolve unavailable devices and charging issues before the next handover.
1. Give every device an identity and a state
The device coordinator assigns a readable code to each phone and its storage position. States distinguish available, issued, charging, awaiting inspection and unavailable. A phone sitting on a charger is not automatically ready for work: its condition, charge and access need checks under the property’s local rules.
The list identifies the using department, required accessories and problem-reporting contact. Cleaning and charging follow manufacturer instructions and approved procedures. A device or cable showing an abnormal condition is removed from use and reported; staff should not improvise a repair to rescue the start of a shift. Keep an authorised alternative ready where the operation needs one.
2. Keep an issue-and-return log
| Field | At issue | At return |
|---|---|---|
| Equipment identity | Device code and accessories | Matching code and returned accessories |
| Responsibility | Person or team under the approved rule | Person accepting the return |
| Timing | Issue time | Actual return time |
| Condition | Charge and reported visible defect | New issue and required follow-up |
| Session | Authorised access checked | Session ended under the configured process |
| Next step | Replacement allocated if needed | Charging, inspection or unavailable |
The equipment log must contain no passwords. Any signature confirms an issue or return, rather than proving the absence of every technical fault. Limit personal information to what is necessary for custody and restrict access to authorised people. Make the record easy to complete at the handover point so entries do not depend on memory later.
3. Separate a shared device from a user account
CNIL recommends individual identifiers and controls shared-account exceptions. The IT lead defines how people start and end their sessions on common devices. Recording a team as the equipment custodian does not, by itself, justify a collective application account. Physical sharing and logical access need separate decisions.
Before starting work, the user checks that the visible information matches their role. An unexpected session triggers the approved process and a support contact. Device management, remote locking or remote wiping options must be confirmed by the administrator; this log does not attribute any such capability to RoomChecking. Avoid placing instructions containing credentials beside the charging station.
4. Prepare the next shift with genuinely available stock
Fictional example: the next shift needs six phones. The fleet contains eight, but one is awaiting inspection and two have insufficient charge under the local threshold. Only five are usable: eight physical devices therefore do not mean eight available devices. The coordinator arranges an authorised alternative before assignments are distributed.
At handover, each return goes to its identified position. The coordinator checks charging state and updates the available count. Unusually fast battery discharge is reported with the device code and observed circumstances, without an improvised technical diagnosis. The aim is to remove uncertainty before the next team leaves for the floors, rather than discover shortages during the first assignment.
5. Close exceptions and missing-device incidents
When a device is missing, consult its latest issue record and contact the expected custodian under property rules. IT assesses appropriate protective action. Equipment loss and possible data exposure require coordinated handling, without posting sensitive details to a general messaging group. Record who is following up and which replacement is being used.
Close the incident once the device is recovered or handled under an authorised decision, its state is current and service continuity is arranged. This equipment routine supports digitising housekeeping operations by making tools available each shift, alongside the separate task of training staff to use operational functions.
Frequently asked questions
Does every employee need an individual phone?
The requirement depends on simultaneous users, charging time and observed unavailability. The log helps size a usable fleet without confusing total headcount with people working at the same time.
Who closes a handover when shifts overlap?
The designated coordinator records an explicit transfer between custodians or a return to the issue point. An informal hand-to-hand exchange leaves responsibility unclear if the phone goes missing.
