Request a consultation
Property leadership topic

Operations and maintenance

Trace service requests and maintenance work from intake to tested completion.

A connected decision sequence

Use the guides in the order that matches your current decision. Keep the evidence, approval, and next action connected as work moves between the board, management, vendors, and specialists.

  1. Establish an operating baselineWhich assets or services are critical?
  2. Map assets and resident service workflowsWhat does verified completion look like?
  3. Report exceptions and test recoveryWhere does work wait without an accountable owner?

Guides in this topic

Build the decision record

For the issue in front of you, name the responsible sponsor, collect the current source records, list material gaps, and identify the acceptance test. Retain a version of the evidence used at the decision date so later changes remain explainable.

These resources provide operational frameworks. Property-specific technical conclusions, deadlines, funding authority, and coverage decisions need the applicable records and appropriate professional review.

Explore the resource library

Need help connecting the evidence and the decision?

Discuss a focused review

Trace service from request to verified delivery

Connect the asset, task, responsible person and user impact. Start with conditions and service history, then identify where work waits for access, approval, materials or specialist advice. A backlog total alone rarely explains the failure.

Interpretation checks

  • Acknowledgement, repair completion and resident-facing closure are different steps. Keep status definitions consistent across systems.
  • Equipment priorities depend on service consequence and recovery arrangements. Price alone does not establish criticality.

Questions for this decision area

Should every work order have the same target?

Set priorities from service impact, applicable requirements and contracted arrangements. Urgent conditions and routine tasks can need different response rules.

When is a repair complete?

Use acceptance evidence appropriate to the system, then confirm the user-facing result. Retain continuing restrictions and follow-up work separately.

Follow a connected review · Check terminology

Evidence at each handoff

What permits the next step?

A task being finished does not establish that its output is ready for the next team. Use these checkpoints to keep the evidence, responsibility and release condition connected.

  1. Define service consequence

    Record to obtain
    Affected assets, users, current restrictions and incident history
    Suggested coordination role
    Operations coordinator
    Check before release
    Priority grounded in actual consequence and continuity options

  2. Release authorized work

    Record to obtain
    Scope, access, competence and upstream dependencies
    Suggested coordination role
    Task owner
    Check before release
    Required permissions and prerequisites established

  3. Test the user outcome

    Record to obtain
    Service test, receiving-team observation and remaining restrictions
    Suggested coordination role
    Receiving reviewer
    Check before release
    Work activity and usable restoration recorded separately

  4. Review recurrence

    Record to obtain
    Follow-up window and comparable service records
    Suggested coordination role
    Service owner
    Check before release
    Effectiveness assessed without hiding reopening or deferred work

Proposed operating workflow, not a universal legal sequence. Confirm authority, professional requirements and permitted parallel work for your property.

Work through a decision in this area

Use this when the same service failure returns after completed work orders or no one owns the next step.

Hypothetical example: A pump fault returns after two repairs. The brief lists the observed incidents and technician records, separates diagnosis from speculation and asks for a qualified investigation before another replacement is approved.

What would demonstrate closure?

Retain the qualified completion test and user-facing restoration evidence. Schedule an effectiveness review against comparable operating conditions; a closed ticket alone does not show that recurrence was prevented.

Review the decision brief structure
A number, its evidence and the decision

Read schedule completion alongside unresolved defects

Completing scheduled work and restoring an asset are different outcomes. Track both: a completed inspection can reveal a defect that still needs a corrective work order.

  1. Asset

    Identify location, task and frequency source.

  2. Execution

    Record who performed the task and when.

  3. Finding

    Separate a normal result from an open defect.

  4. Acceptance

    Verify the repair and restore service.

A worked example with visible assumptions

A fictional property has 40 preventive tasks due and completes 32 on time: 80%. If five completed inspections reveal defects, those findings remain open corrective work. An 80% schedule result does not imply that 80% of the equipment is safe or reliable.

Original hypothetical arithmetic example. The amounts describe a fictional scenario, not observed property performance or a recommended target.

Continue with Maintenance Backlog Triage: Consequence, Readiness and Age

Explore the calculation

Enter non-negative values using the same scope and period. This calculation stays in your browser tab.

Use the example values or enter your own, then calculate.

Check critical exceptions first

An overdue critical test may matter more than several late appearance tasks. Review consequence and required instructions before a blended percentage.

Identify displaced work

If emergency work consumes planned capacity, record what slipped, the asset affected and the recovery arrangement.

Follow the finding

A service visit proves attendance. A dated reading, failed-test record and corrective verification establish a stronger chain of evidence.