MaintenanceOS
checking Adoption —
OPERATIONS

Good afternoon

Focus on the exceptions. Automation handles the routine.

Needs attention—
Emergency—
Waiting approval—
No vendor—
Open—
On your desk—

Attention queue

Ordered by operational risk, not ticket age.

Loading work orders…

Connect & Mirror

Keep your PMS as system of record. Move maintenance progressively.

Network readiness

Use your existing vendors first; source only measured coverage gaps.

Measuring coverage…

Review vendor network →

Create maintenance request

Set up your authenticator

Approval rules, adding colleagues and recording door codes all require a second factor. Scan or type this into an authenticator app, then enter the code it shows.

Confirming signs you out everywhere, including here, so you can sign in with the new factor.

Author a policy version

Policy is append-only: this writes a new version rather than editing the one in force, so every past decision keeps the rules it was actually made under.

What it governs

Spending limits
Who may do the work
Automatic dispatch

Off unless this version turns it on, for exactly what this version governs. The system offers the job to the best-ranked eligible provider with an expiry; a decline or lapse moves it to the next; every stop lands in the attention queue with its reason. Every automatic act is attributed to this policy version.

Add a property

Add a unit

Add a resident

One of email or phone is required — it is where they are told the repair was received, who is coming, and when.

Add an owner

Owners see what was spent on their property and answer the approvals your policy sends them.

Add a provider

One of email or phone is required — it is how a job is offered to them.

Import a CSV

Nothing is written yet. You will see exactly what it would create and change before anything happens.