Operating framework

Four layers of operating support.

Give each question a useful home.

Purpose. Responsibility. Steps. Checks. Connect the help people need, then let them start where the work demands it.

Explore a make-ready example ↓Get the starter pack ↓

An operating framework by Steven Rea

Domain overviewWhy does ready matter?
SOPWho decides it’s ready?
Work instructionHow do I record release?
Job aidWhat must I check?
One make-ready. Four kinds of help.

One home. A connected set of support.

Follow the make-ready, explore the four layers, and open the actual sample documents.

A connected example

From vacant home to move-in ready.

Illustrative make-ready example. These sample roles, rules, and the fictional Turn Board tool are not NorthPoint procedures. The SOP shows the full process; the two work instructions and job aids expand selected tasks within it.

  1. 1Scope
  2. 2Approve
  3. 3Complete
  4. 4Pressure test
  5. 5Release
Failed check? Correct the work, then reinspect.

Work complete does not mean home ready. Release follows verification.

See how the documents connect.

Choose a sample to see what belongs in each layer.

Sets the purpose and ownership
One procedure, different roles
Checks beside the task
Checks beside the task

The lines show relationships between documents, not a required order for writing them.

Follow readiness from the domain’s purpose to the release decision and the evidence behind it.

SOPIllustrative sample · excerpt

Unit make-ready once vacant

What happens from the initial scope walk through the decision to release the home?

Vacant unit and entry cleared. Create scope, then review approval. If not approved, resolve questions and revise scope. If approved, assign and complete work, then pressure test. Failed checks return to corrections and another pressure test. Passed checks proceed to authorized release and leasing notification.
One process with two decision points. Approval and a passed pressure test are required before release. Open full-size image ↗

Read the complete sample and follow its links to related guidance.

Reading: SOP

SOP Illustrative document

Unit make-ready once vacant

Coordinate the work, resolve exceptions, and release the home only after its readiness has been verified.

Process owner
Property operations manager
Roles
Coordinator, trades, property manager, leasing
Begins
Unit vacant; possession and access confirmed
Ends
Verified release recorded; leasing informed
This document answersWhat happens from the initial scope walk through the decision to release the home?
Process flowchart
Vacant unit and entry cleared. Create scope, then review approval. If not approved, resolve questions and revise scope. If approved, assign and complete work, then pressure test. Failed checks return to corrections and another pressure test. Passed checks proceed to authorized release and leasing notification.
One process with two decision points. Approval and a passed pressure test are required before release. Open full-size image ↗
Before the scope walk

The property manager confirms the unit is vacant, possession is established, and entry is permitted under the applicable company rules. The maintenance coordinator opens the home’s turn record with its target ready date and current condition marked Not ready. The target is a planning date, not a release.

The readiness rule

Completed work orders do not make the home Ready. The property manager must verify the approved scope and applicable readiness standard, resolve required punch items, and record the authorized release. Until then, the home stays Not ready.

The coordinator owns follow-up on unfinished work. The property manager owns the release decision. Leasing uses the saved release status when communicating readiness.

Milestones and responsibilities
1
Assess the home and record the scope

Maintenance coordinator

Walk the home after entry is cleared. Record each finding, proposed work, evidence, and missing decision. Submit the scope for review.

2
Approve the scope and assign the plan

Property manager + maintenance coordinator

The property manager confirms approval within the applicable spending authority or obtains the required authorization. The coordinator assigns each approved item to a trade or vendor, records its target completion, and sequences repairs, cleaning, and inspection. Share the current target ready date with leasing.

3
Complete and document the work

Assigned trades or vendors; coordinator follows up

Each assigned person completes approved work and records the result and required evidence. The coordinator checks remaining items and dependencies. New findings return for scope review; delays trigger a revised plan and an update to the property manager and leasing.

4
Pressure test and resolve the punch list

Property manager; coordinator assigns corrections

After required work and cleaning are recorded complete, pressure test the home against the approved scope and readiness standard. Record failed checks as punch items with an owner and target date. Reinspect corrections before release.

5
Authorize release and inform leasing

Property manager

When all required checks pass, save the release with the inspection evidence, decision owner, and date. Verify the saved Ready status, then tell leasing which home has been released and link the record.

When the process stops or changes
  • Entry or possession unclear: stop the scope walk and return the issue to the property manager.
  • Unapproved work or a new finding: the coordinator records it and seeks the required approval before that work proceeds.
  • A missed target or failed final check: keep Not ready, assign the remaining work, and update the target and leasing’s expectations.
  • Readiness standard unclear: the property operations manager resolves the expectation. A target date or move-in commitment does not waive a required check.
Procedure complete

The saved record contains the approved scope, work completion evidence, passed pressure test, resolved required punch items, and the property manager’s release. Leasing has received the release reference.

Teaching example · Read with the connected documents
You can begin anywhere.

Start with the instruction or job aid your team needs now. You do not need to write the whole set first.

Take it into your business

Operating Support Starter Pack

Choose one task. Start with the help your team needs. Includes a starting guide, four editable templates, and the completed make-ready example.

Download editable Word pack ↓Download reference PDF ↓

Both versions contain the complete pack. Copy the template you need, adapt it to your company, and have a teammate try it during the work.

Start with the question that keeps coming back.

Check the help people already have. Is it missing, buried, out of date, or unclear?

Why do we do this?

Domain overview

Explain the purpose and boundaries.

Who does what, when?

SOP

Include a flowchart of the phases, handoffs, and decision points alongside the responsibilities.

How do I do this task?

Work instruction

Pair the steps with screenshots. Highlight the relevant fields or controls and show what the result should look like.

What must I remember?

Job aid

Put the check beside the work.

If experienced people disagree about what should happen, settle the operating expectation before documenting it.

See what changes

When something changes, follow the connections.

Choose a change. See which layers need attention and which can stay valid.

What changed?

The “Release home” button moves.

Domain overview
Still valid
SOP
Still valid
Work instruction
Update
Job aid
Check dependencies

A screen change can require new instructions while the expectation behind them remains valid.

Why these layers?

The steps in the tool have changed. The company still expects the same work, from the same role, at the same point in the process.

  • Domain overview: The purpose and scope of the area have not changed.
  • SOP: The milestone, responsibility, and handoff still apply.
  • Work instruction: Replace the affected tool steps and check the completion signal.
  • Job aid: Update any reminders, references, or templates that depend on the old steps.

Check revisions with someone doing the work, then share the current answer with the people who need it.

Make the first useful piece

Start with “show us how you do it.”

Asking teammates to explain their work and structure the documents at the same time slowed Steven’s early effort. Capture what they know in a form they can readily share.

Explore Discovery Day: start by seeing the work →

  1. Show the work.

    The practitioner talks, records, or shares notes—including exceptions.

  2. Shape the support.

    The support owner organizes it into a useful, findable piece.

  3. Try it together.

    Let someone use it. Find the gaps and revise before making more.

← Back to the library