The meeting ends with several promises: check a delivery date, confirm a drawing reference and arrange a review. A week later, everyone remembers the discussion differently. For a construction project coordinator, a useful action register connects that conversation to a named person, a clear next step and evidence of completion. It also makes unresolved decisions visible before the next meeting.
This guide offers a practical learning method for following up coordination meetings. Use your employer’s approved system and meeting procedures. The examples are hypothetical; an action register does not replace safety processes, design approvals, contractual notices or formal change control.
1. Separate information, decisions and actions
Not every note needs an action number. “Delivery discussed” records a topic but gives nobody a task. “The supplier has proposed Thursday” is an update, not a confirmed decision. “Procurement coordinator to obtain written confirmation of the delivery date” is an action with an observable result.
Keep the meeting record as the account of what was discussed. Use the register to track outstanding work, linking each entry back to the meeting date and agenda item. Record a decision separately, including who made it and where it is documented. If authority or agreement is unclear, mark it for confirmation rather than writing an assumption as an approved instruction.
2. Write each action as a small, checkable outcome
Start with a verb and name the deliverable. Replace “follow up drawings” with “confirm the current issued drawing reference for the loading area and circulate its location in the document system”. Avoid combining several unrelated deliverables in one line: different owners or completion dates usually need separate entries.
For a simple register, include these fields:
- Unique reference: a stable identifier that survives later meetings.
- Source: the meeting date, agenda item and relevant document reference.
- Action and result: what needs to happen and what completion will look like.
- Owner: one person responsible for coordinating that next step.
- Agreed due date: confirmed with the owner, with any dependency noted.
- Status and latest update: a dated account of progress or the blocker.
- Completion evidence and review: a link or reference, plus who checks closure under your process.
These are suggested fields, not a universal industry template. Keep confidential information in approved systems and give access only to the people who need it.
3. Confirm ownership and dates before circulating
“Site team” is rarely a useful owner because several people may assume someone else will respond. Ask the meeting chair to confirm a named owner and check that the person understands the action. Ownership of follow-up does not grant authority to approve a design, commit spending or direct changed work.
Distinguish the date an action is due from the date an answer is needed for another activity. For example, a delivery confirmation might be needed before a logistics review. Record that dependency and ask the responsible manager to assess any programme impact. Do not invent a contractual response period or present your target date as an agreed obligation.
4. Make a blocked action useful to the next reader
Hypothetical example: a coordination meeting discusses a delivery needed for a future work area. The initial note says “check delivery”. A clearer entry would read:
Reference: ACT-018, coordination meeting 13 October, item 4.
Action: Procurement coordinator to obtain the supplier’s written delivery confirmation and file it with the current order record.
Owner and timing: Named procurement coordinator; target 15 October, agreed in the meeting, ahead of the 16 October logistics review.
Update: Awaiting supplier response. Owner will follow up on 14 October and advise the project manager if the information will not be available for the review.
Closure evidence: Reference to the filed confirmation, with the coordinator’s check recorded. Delivery itself remains a separate activity.
This entry defines a manageable task without claiming the delivery is guaranteed. If the supplier changes the date, preserve the update history and refer the possible impact to the appropriate decision-maker. Do not quietly overwrite the original commitment.
5. Review open items and close them with evidence
Before the next meeting, ask owners for a short update: what has changed, what remains unresolved and what help is needed? Bring overdue or blocked items to the agreed escalation route with facts, not blame. A useful escalation identifies the missing information, affected activity and decision required.
Use statuses that your team understands, such as open, in progress, blocked and complete pending review. “Email sent” may show effort but does not prove the required answer arrived. Check the stated result and its evidence before closing the action. Record cancellation or replacement explicitly so that unfinished work does not simply disappear.
Some meeting items need another workflow. For missing technical information, use the construction RFI checklist. For a proposed change affecting scope, time or cost, the project change record can help organise the information for review. Keep the action reference connected to the formal record.
Build the skill with a short practice exercise
Write five fictional meeting notes, convert them into actions and ask a supervisor to check whether the owner, result and closure evidence are clear. Explore the project coordinator career pathway or the career assessment to identify another capability to practise.
For structured learning, review the current WBS BSB50820 Diploma of Project Management information or enquire about your study needs. The course covers project information and communication; completing this practice exercise is not evidence of assessed competency. The qualification does not grant a construction licence or guarantee employment or promotion.