Planning & controls
Set up a project and hand it over
Take a job from the very first setup right through to handover. Create it, price the work,…
5 steps20 minOpen
Cases / Planning & controls
Planning & controls
Run a progress meeting and drive the actions
Chair a site progress meeting, capture the decisions, turn each into an owned action or RFI, then issue the minutes.
How it works, step by step
4 steps across the platform - what you do at each one, and why it matters.
1
Chair the meeting and log the minutes
MeetingsOpen the meeting, work the agenda, and record attendance, minutes and every decision as they are made.
Why: A meeting with no written record gets re-argued next week, and a verbal decision does not hold up in a dispute.
InMeeting agendaAttendeesOutLogged minutesRecorded decisions
2
Turn decisions into owned actions
TasksRaise a task for each action coming out of the meeting, each with a named owner and a due date.
Why: An action with no owner and no date never gets done. Naming both is what makes progress trackable and someone accountable.
InRecorded decisionsNamed ownersOutOwned tasksDue dates set
3
Raise RFIs for open questions
RFIFor every unresolved technical question, raise a formal RFI to the designer so the answer is logged and dated.
Why: A question left in the notes stalls the works and gets forgotten. A formal RFI forces a dated answer on the record.
InUnresolved questionsMeeting minutesOutFormal RFIsDated RFI log
4
Issue the minutes and actions
ReportsGenerate the minutes and the open-actions list and send them to everyone who attended.
Why: Minutes only bind people once they are issued. Circulating the actions closes the loop and starts the clock on every due date.
InLogged minutesOpen actionsOutIssued minutesCirculated actions
Modules in this playbook
4 / 184 platform modules