Property operations field guide

A guided reading path: understand the process, apply a template and test the workflow.

What this guide helps you do

A practical way to connect properties, responsibilities and evidence without creating more administration. Work through the reading and the practical checks below with the people responsible for the process.

1. Read the practical method

Write down the decisions your team makes in a normal week: which home needs a visit, who is cleaning it, which repair needs approval and what owners need to know. These decisions tell you which records must be reliable. A dashboard is only useful if it helps someone make one of them.

2. Review these decisions with your team

1. Agree the record that everyone uses

   Give every property a stable name and reference. Link the owner, units and essential information to that record. A task should point back to the property rather than repeat the address in free text. This makes corrections easier and gives a new colleague a useful starting point.

2. Define a complete job

   A job needs a responsible person, an expected outcome and a date when timing matters. Write checklists as observable actions. “Check bathroom” is vague; “confirm the shower drains and record any leak” gives the worker a useful standard.

3. Make the daily review short

   Start with overdue work and critical repairs. Review owner approvals next, then upcoming cleaning and inspections. For each item, choose a next action: assign, schedule, resolve or ask for missing information. The review should change the work, not merely describe it.

4. Roll out in a controlled sequence

   Load active properties first, then owners and open work. Check the new queue against the old spreadsheet with the people responsible for it. Keep the old system read-only during a short validation period so that discrepancies can be resolved without running two competing sources of truth.

3. Try one complete workflow

Choose one property and a normal operational job. Name the responsible person, record the expected outcome and work through the process. Check that the next person can understand what happened without a separate explanation.

4. Review before expanding

Record missing information, unclear handovers and permission problems. Correct them at the source, then repeat the pilot. Invite owners only after checking their access with an appropriate test account.