Maintenance
Intake, prioritize, assign, and close maintenance requests with complete traceability.
Maintenance workflows protect service quality and tenant trust. Every request must have clear ownership and completion evidence.
Maintenance outcomes
These outcomes define effective maintenance operations.
- Requests are triaged quickly with the right priority.
- Ownership is explicit at every stage of the lifecycle.
- Resolution evidence is complete before closure.
Intake-to-close workflow
Use this sequence to keep request handling consistent.
Create request with clear issue description and location context.
Set priority and assign responsible owner.
Track status updates, notes, and attachments throughout execution.
Close only after verifying completion and required evidence.
Priority guidance
Use priority levels consistently so response expectations are predictable.
| Priority | Response expectation | Typical scenario |
|---|---|---|
| Critical | Immediate triage | Safety risk or severe interruption |
| High | Same-day action | Major operational impact |
| Medium | Planned scheduling | Important but non-urgent issues |
| Low | Backlog scheduling | Minor, non-blocking requests |
Operational guardrails
Apply these guardrails to avoid premature closure and hidden backlog.
- Do not close requests without completion notes.
- Keep assignee ownership current after every handoff.
- Use tags or categories for trend analysis and prevention planning.
- Link relevant media for proof and future reference.
Next steps
- Store evidence in Media.
- Capture financial effects in Transactions.
- Use Troubleshooting for stuck workflows.
Last updated on