Facilities Service Request Intake Template: Capture the Issue, Access and Next Action

A facilities service request intake template turns a reported condition into enough reliable information for safe triage. It should capture what was observed, where, when, who is affected, how access works and which authorized owner will respond next.

The intake is not a technical diagnosis, safety clearance or permission to perform work. Requesters should protect people, use approved emergency routes when necessary and leave inspection and repair decisions to qualified, authorized personnel.

Define the intake route and service promise

Publish one primary route for routine facilities requests and separate routes for emergencies, security incidents and IT issues. State staffed hours, expected acknowledgment, who triages and how requesters receive updates. A mailbox without ownership is not a service process.

Define roles clearly. The requester reports observable conditions and availability. The intake coordinator checks completeness and duplicates. The facilities duty owner determines routing and priority. A qualified technician or vendor diagnoses and performs authorized work. The operational owner confirms whether service was restored.

Avoid promising a repair date before scope, resources, parts and access are understood. Promise the next update that the team can control.

Copy this facilities service request intake template

FACILITIES SERVICE REQUEST INTAKE

Request reference / received date and channel:
Requester / safe contact method:
Site / building / floor / exact location:

OBSERVED CONDITION
What was seen, heard, smelled or experienced:
When first observed / current status:
Operational or occupant effect:
Immediate protective action already taken:

EVIDENCE
Authorized photo or document reference:
Related asset label if safely visible:
Previous request reference:

ACCESS AND CONSTRAINTS
Occupied area / access hours:
Escort, permit or authorization needed:
Known restricted or sensitive conditions:

TRIAGE
Initial category / basis:
Duty owner / assigned team:
Next action / next update time:
Escalation trigger and route:

CLOSURE
Work-order reference:
Completion evidence / operational confirmation:
Requester update / reviewer / date:

Make fields optional when information is genuinely unavailable. Do not encourage a requester to approach a hazardous condition merely to complete the form.

Describe observations without diagnosing

Ask for sensory and operational facts: water is visible below a ceiling tile; a door does not latch; a room is warmer than its usual setting; a light is flickering. Include time, frequency and current state. Avoid forcing the requester to choose a technical cause.

Location detail should let an authorized responder find the condition: site, floor, room, zone, nearby landmark and asset label if safely visible. For moving or intermittent issues, describe where and when they occur.

Use a facilities inspection checklist for planned condition reviews across multiple areas. Intake should remain quick enough that staff report issues promptly rather than postponing them for a perfect narrative.

Capture impact and urgency evidence

Ask what activity is affected, whether the area remains usable, how many locations are involved and whether the condition is changing. The requester supplies observed impact; the authorized duty owner applies priority criteria.

Do not use emotional wording or job seniority as a proxy for urgency. Likewise, do not downgrade an issue simply because the requester cannot explain the technical consequence. Triage should consider approved safety, accessibility, service, asset-protection and operational criteria.

Where evidence is incomplete, record uncertainty and set an inspection checkpoint. A missing photo is not a reason to ignore a credible concern. Conversely, an image may not show hidden scope or prove the proposed cause.

Ask whether the condition is isolated or visible elsewhere, but do not instruct an untrained requester to search restricted areas. Note recent changes that the requester directly knows about, such as a room move, delivery or approved building work, without treating correlation as causation. The triage owner decides whether that context warrants further review.

Accessibility and essential-service effects should be described concretely. Record which route, room or function is unavailable and what approved alternative currently exists. Do not include a person’s diagnosis or private circumstances when the operational barrier alone gives facilities enough information to act.

Route immediate hazards correctly

The form should display a clear instruction for conditions that require an emergency, security, fire, life-safety or other urgent route. Requesters should not wait for an email acknowledgment when policy requires immediate contact. They should not touch, isolate or test equipment unless trained and authorized.

The intake coordinator records when an emergency route was activated and who accepted it. Do not investigate or pronounce the area safe through the request form. Qualified responders control exclusion, shutdown, inspection and re-entry decisions.

An event incident report template is appropriate when an event caused harm, damage or a defined near miss requiring a separate timeline and review. Link the records without duplicating restricted details.

Collect access and scheduling constraints

Good triage includes when the area is occupied, who can grant access, whether an escort is required and which approved permits or controls may apply. Record operational blackout periods and accessibility needs without collecting unrelated personal information.

Access information does not authorize entry. Facilities staff and vendors must still follow site rules, identity checks, permits and safe systems of work. Never place keys, alarm codes or credentials in a general request description.

If the work may disrupt service, assign an operational contact to approve the window and communicate with affected people. The technician owns technical execution; the business or site owner manages operational readiness and acceptance.

Convert requests into controlled work

After triage, link the intake to the authorized work record. One request may produce several work orders, or several duplicate requests may map to one underlying issue. Preserve the relationship so requesters receive consistent updates.

Define the status mapping between systems. Accepted, assigned, attended, temporarily restored, completed and verified are different states. A technician’s departure does not necessarily mean the service is restored, and operational confirmation does not replace required technical closeout. Make the next responsible owner visible at each transition.

Where a temporary repair is approved, state its limits, inspection frequency, expiry or replacement plan and escalation trigger. Do not close the underlying work merely because immediate symptoms reduced. Qualified reviewers must confirm whether monitoring is sufficient and when permanent work is required.

The maintenance work order template can capture scope, trade, permits, parts, labor, completion evidence and technical closeout. Do not silently turn the requester’s suspected cause into the work-order diagnosis.

Record rejected, redirected or duplicate requests with a reason and the correct destination. A status label alone is insufficient. The intake owner remains responsible for telling the requester what happens next.

Assign owners and communication checkpoints

Every accepted request needs one duty owner and a next update time. The assigned technician may change, but the service owner should remain visible. Dependencies such as landlord approval, specialist attendance, parts or access receive separate owners and review dates.

Escalation triggers may include worsening conditions, missed acknowledgment, inability to secure an area, repeated recurrence or no dependency response by the checkpoint. Use the approved route and record who accepted the escalation.

Use meeting follow-up principles after a coordination call: preserve the reviewed action, owner and date in the service record rather than relying on private messages or an unverified transcript.

Protect sensitive building information

Limit access to floor plans, security systems, access controls, occupant information and critical infrastructure details. A routine requester may need status but not technical or security-sensitive evidence. Store attachments in approved locations and apply retention rules.

Photographs should avoid people, screens, badges and unrelated private spaces. Explain what the image depicts and when it was taken. Do not publish or broadly forward request evidence.

Apply the same restraint to free-text descriptions. Building vulnerabilities, security routines and critical asset details should not appear in notifications sent to broad distribution lists. The duty owner can provide a requester with a useful status update while keeping restricted diagnostic and infrastructure information inside the controlled work record.

If an external contractor needs evidence, confirm the approved sharing route, recipient and purpose. Remove unrelated information and record the transfer where policy requires it. Convenience is not a sufficient reason to move sensitive records into an unmanaged chat or personal account.

If a request concerns an individual’s health, workplace adjustment or personal circumstance, capture only what facilities needs and route the broader matter through the authorized function. The form should not become a shadow personnel or medical record.

Use recordings and AI with boundaries

Record an intake conversation only when authorized, necessary and transparent, with notice and agreement where required, a practical alternative, controlled access and retention.

For an authorized facilities intake conversation with visible, consented capture, Kuno can help draft the observed condition and next actions for human review. It does not diagnose equipment, set safety status or authorize work. Explore Kuno

AI may invent a cause, omit a negative or confuse a requested action with an approved one. The intake coordinator and duty owner must verify the draft, and qualified personnel must make all technical and safety judgments.

Complete final QA and closure

Before routing, confirm:

• Site, exact location, time and current condition are clear.
• Observations are separate from suspected causes.
• Impact and uncertainty are recorded without an unsupported priority verdict.
• Immediate hazards used the approved urgent route.
• Evidence was collected safely and stored appropriately.
• Access information is sufficient but contains no credentials.
• One duty owner and next update time are visible.
• Dependencies and escalation triggers have owners.
• The work-order relationship is traceable.
• AI-assisted text received responsible human review.

Close the intake only when the service process reaches its defined endpoint, the requester receives an update and operational confirmation is documented. Technical completion, area re-entry and business acceptance may require different authorized reviewers; do not collapse them into one unchecked box.

Turn a reported condition into a reviewable intake, not an automated diagnosis. Kuno can support authorized conversations while facilities professionals retain responsibility for triage, safe work and final verification. See Kuno