# Daily operations brief

ARK360 · Free working template · No software required

Building: __________________  Date / time: __________________
Prepared by: _______________  Incoming team: ________________

## 1. What needs attention today?
For each open issue, capture:
- Issue and location:
- Current status / last verified update and time:
- What is still unresolved:
- Next action / owner / due time:
- Source reference (keep the record in your existing system):
- What would count as resolved:

## 2. What was promised?
- Commitment / who made it / when:
- Confirmation received or still needed:
- Next follow-up / owner / due time:

## 3. What must survive the handover?
- Change since the last shift:
- Context the incoming person needs:
- Decision required and decision-maker:
- Uncertainty to verify:
- Incoming owner / acknowledgement:

## 4. Close the loop
- Updates returned to the system of record:
- Outstanding actions handed to named people:
- Next review time:

Use issue references rather than resident personal details. Follow your existing
emergency, safety and escalation procedures; this template does not replace them.

Illustrative example, fictional data: Wattle House / garden door repair.
Contractor attended Tuesday. Afternoon handover still reports catching.
Next: building team to confirm return visit and request an updated repair note.
Sources: sample work order #1042 and sample Tuesday handover, not customer records.

Discuss a recurring workflow: https://meetings-na2.hubspot.com/james-park
james.park@ark360.com.au · https://www.ark360.com.au
