PROPERTY AND OPERATIONS · FACILITIES MANAGEMENT
Keep external facilities work connected from instruction to return.
Give workplace and facilities teams one controlled record for a scoped service instruction, the provider response and the completion information returned.
Designed for: Facilities directors, workplace leads, contract managers and FM helpdesk teams coordinating external service providers across buildings.

THE OPERATING PROBLEM
Where the record becomes fragmented.
An FM team may oversee cleaning, fabric, mechanical, electrical and specialist services while requests arrive through helpdesks, email and local building teams.
The operational gap appears when the approved scope, intended provider, acceptance and returned information live in different places. A later reviewer can see messages but not one attributable sequence.
SUITABLE WORKFLOW
From bounded instruction to accepted return.
- 01
Create a tenant-bound instruction with building, service line, scope and intended provider.
- 02
The provider accepts or declines through the controlled response route.
- 03
The provider returns declared completion information and evidence metadata.
- 04
The requester accepts the submission or rejects it with a correction request; the final receipt identifies the accepted version.
WHAT IS RECORDED
- instruction version and requester
- intended provider and response
- declared completion notes and evidence metadata
- rejection, correction and final requester decision
WHAT IS NOT PROVED
- personal identity
- physical attendance
- condition or quality of the facility
- statutory compliance
- truth of uploaded evidence
EXISTING SYSTEMS
A bounded record—not a system replacement.
Verified Dispatch can sit beside CAFM, IWMS, helpdesk, procurement and asset systems. Those systems remain the source for asset registers, schedules, costs and statutory controls; the dispatch record covers the bounded external handoff.
Read the factual product referencePRACTICAL SCENARIOS
Where this workflow can be useful.
Specialist plant callout
Record the exact plant reference and access context sent to a specialist without treating the return as an engineering certification.
Multi-provider service desk
Separate what the FM helpdesk asked from what each service provider accepted and returned.
Corrective visit
Reject an incomplete return, request a specific correction and retain the accepted version without overwriting the first submission.
WHOLLY SYNTHETIC EXAMPLE · VD-FM-218
Northbank Workplace Services
No organisation, property, person, claim or work order in this example is real.
Instruction created
Inspect a reported air-handling fault at the fictional Calder Exchange and return declared fault notes plus the evidence-file metadata requested.
Intended recipient
Aster Mechanical Services
Provider response
Accepted by the provider response route at 09:18.
Returned information
Declared diagnosis, action note and metadata for two synthetic image files.
Requester review
The requester rejected version 1 because the plant reference was missing; version 2 added AHU-C4 and was accepted.
Final versioned receipt
Receipt VD-FM-218-R2 records requester acceptance of provider submission v2.
Explicit boundary
The receipt records the accepted declaration. It does not prove attendance, diagnosis, repair quality or compliance.
PRACTICAL FAQ
Questions from facilities management teams.
Does this replace a CAFM or IWMS platform?
No. It is designed to preserve a bounded instruction-and-return record alongside systems that manage assets, planned work and service operations.
Can the requester ask for a corrected return?
Yes. A rejection can state what needs correction, and the corrected submission receives a new version.
Does a receipt certify that the facility is safe?
No. Safety, compliance and technical certification remain with the responsible people and systems.
RELATED AUDIENCES
Compare the neighbouring workflow.
CONTROLLED PILOT
Discuss a controlled FM workflow pilot
Define one bounded workflow, synthetic or approved pilot data, named roles, success criteria and explicit claim limits.
Start a pilot conversation →