Build a weekly update that supports the next decision

Set the reporting window and purpose

State the project, reporting period, preparation date, author, and information cutoff. A Friday update assembled Thursday afternoon should not imply it includes Friday's events. A useful update helps readers see what changed and what needs attention next.

A weekly rhythm is the example used here, not a universal requirement. Follow your project's communication arrangements. NYSDOT's meeting guidance illustrates that meeting frequency and participants vary with the work.

Separate completed work from reported progress

Build the recent-work section from identifiable records: daily reports, delivery logs, reviewed documents, or named updates. Include locations and dates where they clarify the summary. Distinguish work you can support with records from progress reported by another party. A delivery entry, for example, does not establish installation.

Use consistent measures when discussing progress. If a percentage has no agreed basis, explain the actual recorded activity instead. FHWA's reporting guidance emphasizes specific, factual records.

Make dependencies understandable

For each important upcoming activity, state what information or preceding action it depends on. 'Drainage activity planned Tuesday; drawing clarification RFI-024 remains pending' reveals more than a green status symbol. Identify the dependency's owner, the next review date, and the source of the planned timing.

Keep a forecast separate from a commitment or authorized schedule change. If an unresolved dependency may affect the plan, record the uncertainty and the question for the responsible scheduler or manager. Do not calculate an unsupported project delay from one missing document. A coordination update can reveal the issue without deciding its contractual effect.

Turn discussion into assignable actions

Write actions with a verb, a deliverable, an owner, and a target or review date. 'Alex to locate the delivery ticket for DT-116 before Tuesday's materials review' is easier to follow than 'materials to be sorted.' Where responsibility has not been accepted, show owner confirmation as pending rather than inventing agreement.

Record a decision only when the authorized participant has actually made it. Link the decision's source and preserve any conditions. Meeting discussion, a proposed option, and an issued instruction are different records. NYSDOT's progress-meeting guidance provides an agency-specific example of connecting action items with responsible people and deadlines.

Publish a snapshot and carry changes forward

Keep one identifiable issued version for the reporting period, with the location of supporting records. Check that the intended recipients can open the references. If a correction is needed, date it and identify what changed. Avoid quietly replacing a disputed statement so nobody can understand the earlier communication.

At the next update, revisit open actions before adding new ones. Show completed actions with evidence, retain overdue work visibly, and explain changed dates or owners. Close the communication loop by making the current status and next responsibility explicit.

Fictional training example

Worked example: Harbor Road weekly coordination

Fictional training scenario. Update WU-07 for project HR-15 covers 19–23 October, with information collected through Thursday at 3 p.m. The recent-work section links delivery log DL-29 and states that two inlet units were received. It does not call them installed. Friday's activity is listed as planned, based on the contractor's Thursday update.

The next-week section identifies RFI-024 as an unresolved dependency for a planned drainage activity. The document coordinator owns follow-up with the designated responder; the scheduler owns review of any effect on sequencing. At the meeting, a new review date is agreed and recorded with the minutes reference. WU-08 carries the same identifier forward until a supported resolution is recorded.

Try it yourself · Fictional scenario

Practice: replace an optimistic update with a useful one

Fictional scenario. A draft says: 'All drainage materials are done. Work starts Monday. Design is handling the questions.' The delivery log records one shipment received, RFI-032 remains open, and Monday is a proposed start in the contractor's look-ahead. Nobody has confirmed who will follow up on the RFI.

Your task

Rewrite the progress statement using only supported information.
Describe Monday's activity and its unresolved dependency.
Write a specific action to confirm responsibility and the next review date.

Use your own notes or a sheet of paper. Compare your response with the example below when you are ready.

Reveal a sample response

A clearer update says: 'One drainage-material shipment received, according to the delivery log. Installation is not established by that record. Monday's start is proposed in the contractor's look-ahead; RFI-032 remains an unresolved drawing question.' Add the actual source identifiers and dates before issuing the update.

Ask the project coordinator to confirm the assigned RFI follow-up owner and review date through the established communication process. Record that assignment as pending until confirmed. The scheduler or manager assesses the relationship to the planned activity; the summary does not create a schedule decision.

Keep in mind: A useful update shows the evidence, the uncertainty, and who owns the next step.

Build a weekly update that supports the next decision

What you will practice