A progress report should help a project owner understand the current situation and decide what happens next. A collection of photographs or a message saying “work is ongoing” may leave important questions unanswered.

The reporting approach should suit the agreed project management scope. A simple, consistent structure often makes updates easier to compare over time, particularly when an owner is following a project remotely.

Identify the project and reporting period

Start with the project name, location, reporting period, and the person preparing the update. This makes it clear which work and dates the report covers.

Use the same basic headings each time. Consistency helps a reader find new information without having to interpret a different report format every week.

Explain completed work in practical terms

List the activities completed during the period and identify the area or stage they relate to. Distinguish finished work from work that has started but still needs follow-up. Avoid using a single percentage to explain several unrelated activities.

If a photograph supports an update, add a date, location, and a short explanation of what it shows. A labelled image is easier to understand than an uncaptioned gallery.

Show what is planned next

Describe the next planned activities and any information, materials, access, or coordination they depend on. Identify which people need to contribute before an activity can move forward.

When a schedule changes, explain the change rather than silently replacing the previous plan. Keep the original reference available so the owner can understand the revised sequence.

Make decisions and open issues visible

Separate routine updates from matters that need the owner’s attention. For each decision request, explain the question, available information, the response needed, and the person expected to respond.

Keep an open-issues list so unresolved matters can be followed from one report to the next. Record the agreed action and responsible person rather than leaving an issue as a general observation.

Keep changes and approvals traceable

Refer to the agreed scope and record approved changes in a way the team can follow. Link supporting information to the relevant activity or request. Use clear filenames and version dates when documents are updated.

Reporting arrangements, review frequency, and approval responsibilities should be discussed at the start of the engagement and adjusted when the project’s needs change.

Connect the update to the next conversation

End the report with a short action list. A project meeting can then focus on outstanding decisions and coordination rather than repeating information already shared.

Discuss KAL project management, or open K Projects to request project coordination, remote supervision, and asset management support. You can also contact KAL about the reporting arrangements you need.