Library · Playbook
Operations and facilities playbook
Day-to-day custody, work history, and handoffs for teams that keep buildings and equipment running.
Key takeaways
What to remember
- Facilities work spans buildings, equipment, vendors, and occupants — the register must survive that mix.
- Closing a work order without custody context leaves the next shift guessing.
- Operations playbooks stick when they sit on the same EALM registry finance and audit will ask about later.
Day-to-day custody, work history, and handoffs for teams that keep buildings and equipment running.
The facilities reality
Operations teams move between rooms, plants, campuses, and contractor handoffs. Assets are chillers, access systems, lab benches, and IT closet gear someone needs tomorrow. A register that ignores that texture forces people back to tribal knowledge.
This playbook is the evergreen operating layer: rituals and handoffs that keep custody and work on one identity.
Daily rituals
Keep the register honest in the flow of the day:
- Open the shift with exceptions that matter: missing, found-not-on-register, or stale custody flags in your zone
- Log moves when they happen — do not batch “we’ll update the spreadsheet Friday”
- Close work with location and condition notes on the same asset ID the next shift will open
- Escalate identity collisions early (two tags, one thing) before they become audit noise
Weekly rituals
Use a short weekly loop so drift does not wait for year-end:
- Review open custody transfers and staging assets that never reached an in-service location
- Spot-check a sample of high-value or regulated assets against the register
- Reconcile vendor or contractor returns that left the site without a disposal or transfer event
- Confirm onboarding and offboarding hardware lists hit the register, not only the ticket queue
Handoff steps that must not break
When work and custody travel together, the next person inherits history instead of guessing:
- Shift handoff: open exceptions + assets in motion, not only open tickets
- Site handoff: location and custodian update before the truck leaves
- Vendor handoff: loaner or remove-and-replace events write to the same ID
- Role handoff: offboarding closes custody; onboarding opens it — both on the register
Role-shaped product view
Continue to Solutions for Operations when you want the product framing for the day-to-day job. This Library playbook stays the evergreen reading layer for rituals and handoffs.
Related on AssetZA
More guides
Keep exploring the Library
Frequently asked questions
Why call this a playbook?
It is organised around daily and weekly rituals and handoff steps — not a product brochure. Use it as operating reference; open Solutions for Operations for the product view.
How does this connect to audit?
Custody and work history written during operations become the evidence audit checks later. See the Audit and reconciliation readiness guide for the compliance twin.
Is this the same as Insights?
No. Library playbooks are evergreen. Insights is dated commentary.