How to prepare a construction site photo report: keeping progress photos organised

To prepare the weekly progress report, you open your phone’s gallery: IMG_4821, IMG_4822… two hundred and forty photos. One shows column formwork, one a pile of rebar, one is clearly a wall. Which block? Which floor? Tuesday or Thursday? The person who took the photo knew at the time, but that information was not saved with the photo. The report goes to management tomorrow morning, and there is no option but to open the photos one by one and guess. A construction site photo report is a report that presents progress and status photos in an orderly way by linking them to block, floor, date and task; the value of a photo lies in keeping it together with the record that explains what it shows.

The quality of a photo report is decided by the record, not by the shot. Below we explain step by step which information should be linked to a photo, the outline of a weekly progress report and how a photo gets from WhatsApp into a work record.

How do I link a site photo to a work record with block and floor details?

Every photo should have one sentence next to it, and that sentence should say what the photo is. A photo record should carry at least these six pieces of information:

• Block: A, B, C and so on; on a single-building site, the building name.
• Floor or area: 4th floor, basement, landscaping and so on; grid line details if needed.
• Date: The day the photo was taken; for a photo sent later, the day the message arrived may differ, so note it.
• Task: What was done or what is missing: “slab concrete poured”, “stair guardrail missing”.
• Reported by / which crew: The foreman, the subcontractor lead or the crew name.
• Status: Started, in progress, completed, defect opened or defect closed.

This information is easiest to write down the moment the photo is taken, because that is when you remember it. A week later, gathering the same information means phoning someone else, and the answer is usually “roughly”.

Five rules for taking site photos

1. Shoot from the same spot. The strongest comparison showing progress is two photos taken from the same angle.
2. Take one wide shot and one close-up. The wide shot shows the location; the close-up shows the quality of the work or the defect.
3. Leave a reference for scale. A tape measure, a piece of machinery or a formwork panel makes the size readable in the photo.
4. Keep workers’ faces out of the frame unless necessary. A work photo is not a photo of employees; if a person does not need to be seen, they should not be.
5. One photo, one task. Do not try to show three tasks in a single frame; it stays unclear which task it belongs to.

Weekly construction progress report outline

A weekly progress report is a compilation of the daily records; it does not produce new information but puts the existing records in a readable order. The outline below is a sufficient starting point for most sites.

Construction progress report example: a week of photo records

The rows below are fictional. Each row keeps the photo together with the date, block and floor, and task; by the end of the week the information for the report is already in place.

Looking at the rows, you can see how the 4th floor of Block C progressed in three days, and that the defect on the 2nd floor of Block A was opened on Thursday and closed on Friday. Because the date, task and block of each photo are written in the record, nobody needs to be called to put this summary together.

Choose photos according to who will read the report

Not everyone receives the same two hundred photos from the week. The photos should answer whatever the reader of the report is asking:

• Company management: Overall views and progress comparisons; delays noticed from block to block. A small number of well-chosen photos is enough.
• Building owner or client: Before and after photos of completed work; the status of tasks that affect the handover date.
• Subcontractor: The photo of a defect opened for their crew and the close-out photo; it is the photo itself that takes the argument out of the conversation.
• Office and purchasing: Delivery note photos for materials received, and which task a pending request is linked to.

Thinking of defect photos as a “before and after” pair is the habit that improves a report’s readability the most. An opened defect gets one frame, and the closed defect gets a second frame from the same spot; put the two photos side by side and the question “is it done?” turns into a visible answer instead of a debate.

Gallery, WhatsApp group and folders for site photos: where they work and where they break

On a small site, if the person who takes the photos is the same person who prepares the report, the phone gallery and a weekly folder may be enough. Writing the information into the file name makes the job easier; for example, a name in the format 2026-10-24_Block-C_Floor-4_slab-concrete_01 identifies the photo without opening the folder. The system breaks down at these points:

• The person taking the photo and the person preparing the report are different, and the information stays in the message between them.
• A photo posted in a group gets lost in the conversation; which task it belongs to stays in the head of whoever sent it.
• Not everyone follows the file naming rule; three people name files in three different ways.
• The defect photo and the close-out photo are kept in different places, and there is no proof the defect was closed.
• When the report is being prepared, photos are searched for one by one; the real work becomes searching, not reporting.

How is a photo linked to a record in SahaSesi AI?

In SahaSesi AI, the foreman sends a photo on WhatsApp with a short sentence or a voice message; the site team does not need to install an app. The photo is attached to the record; a note such as “column formwork completed on the 3rd floor of Block B” lines up in the daily report with its block and floor. A defect with a photo is opened for the responsible subcontractor and is closed when the close-out photo arrives. Every record is read back to the foreman as “Logged: …”, and if something was misunderstood, the foreman corrects it; records that cannot be confirmed land in the office’s “awaiting review” list.

The bot cannot read messages in WhatsApp groups; a photo in a group is recorded when it is sent to the bot using “Forward”. SahaSesi AI is being rolled out on its first sites through a pilot programme.

A quick check before sending the photo report

• Does every photo have its block, floor, date and task written down?
• Have comparison photos taken from the same spot gone into the report?
• Does every opened defect have a photo, and every closed one a close-out photo?
• Do the delivery note photos match the delivery records?
• Are photos of incidents or safety non-conformities at the top of the report?

If you would like to see your photos logged from WhatsApp with block and floor details on your own site, you can schedule a pilot meeting on the SahaSesi AI page.