INDUSTRY FIELD GUIDE
Facilities service handoff records for AI workflow evaluation
A facilities provider may coordinate housekeeping, maintenance and on-site contractors under different responsibilities.
NAICS 561210 · Facilities Support Services
A facilities provider may coordinate housekeeping, maintenance and on-site contractors under different responsibilities. A useful dataset shows how a request crosses teams and where the decision authority changes. Appen’s enterprise offering describes interest in role handoffs and escalation paths. NIST’s building digitization work illustrates how structured building information can support workflows. Confirm demand for the particular handoff. Appen enterprise data · NIST building digitization
Model one failed handoff
Build a fictional issue that starts with a housekeeping report, passes to a maintenance dispatcher and then requires a site owner’s authorization. Use generic room and asset IDs. Include the current service matrix, time stamps, the assigned role and proof that the owner approved the next step. A second case can have the same symptom but a different service contract. Score whether an assistant identifies the responsible team and cites the right agreement.
The target is workflow routing across providers. Detailed repair and facility-control decisions belong in a separate evaluation with its own scope.
Avoid access and security material
Keep credentials, tenant lists, precise floor plans, building control access and sensitive incident reports out of the first example. Ask the facility owner and contractor who can authorize the approved record set. Use a fabricated service matrix and no connection to operating systems.
Start with one handoff, a responsibility matrix and an exception. Describe a dataset
Original Fiund exercise
A service matrix selects the next authority, while dispatch does not prove owner approval
An original fictional issue concerns a loose inert sign on a mock room prop. It includes no credentials, tenant, actual plan, building control or repair procedure.
| Record | Source | What it records |
|---|---|---|
| FH1 | Contract C1 matrix | Housekeeping reports the issue; dispatcher may assign review. Replacement action needs site-owner approval. Matrix explicitly applies to mock site A. |
| FH2 | Site A timeline | Housekeeping report R, dispatcher assignment D and owner approval O explicitly link the same issue I. No actual replacement event supplied. |
| FH3 | Site B packet | Similar sign issue under contract C2 requires contractor-manager approval. Only a dispatcher assignment exists; no manager approval. C1 owner signature copied as an attachment. |
Question for the model
Which authority handoff is supported at A, and why does the same symptom or copied approval not resolve B?
Show the reference answer and checks
FH1 and FH2 support A's report, dispatch and required owner approval for issue I, while replacement completion remains undocumented. FH3 uses a different contract requiring contractor-manager approval; its dispatch and copied C1 owner signature do not satisfy that stated matrix. Route B's missing approval to the named role rather than generalize from the symptom or another site's authority. This fixture evaluates routing, not facility-control or repair decisions.
- Applying one site's responsibility matrix to a similar issue under another contract.
- Treating assignment or another site's approval as permission for the next action.
Fields to preserve
- Site, contract and issue
- Selects the responsibility matrix.
- Current role and required approval
- Defines the handoff.
- Linked authority source and completion state
- Separates permission from execution.
Test another case
Add B's manager acknowledgment saying review pending. Require the correct role match without calling it approval.
Use fabricated matrices and inert props. Exclude access details, real incidents and operating systems; facility and contractor rights need separate review.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.