Metadata that makes an image usable
Capture the date and time using the project’s agreed convention; retain the original file metadata where appropriate. Add a stable project identifier, building or area, floor or zone, viewpoint code, direction, photographer or capture source, and a short subject description. Where an image is related to a drawing, include the drawing identifier and revision only after checking that it is the applicable controlled version. If an automated system derives a location or classification, keep the source and confidence information visible to reviewers rather than silently replacing the original facts.
File names can be predictable without becoming overloaded. One workable pattern is project-area-viewpoint-date-sequence, provided the team documents the pattern and handles corrections consistently. Do not put sensitive personal information in file names. Keep the original capture, any edited derivative and any annotation distinguishable. Cropping, stitching, enhancement or redaction can change what a reviewer can infer; record material edits and avoid implying that an altered image is an untouched source.
Set a useful rhythm
Capture frequency should follow the decision cycle and pace of work. A daily picture is not automatically better than a weekly one if it cannot be located or reviewed. Agree a schedule around planned work, handovers, hold points and reporting dates. If an event changes the expected work sequence, record the reason for an extra capture or a missed one. A gap in the archive is information: it should trigger a question about coverage, not an assumed state of the site.
Consider whether the same viewpoint remains safe and representative as the project changes. Temporary works, stored materials, weather, lighting and access restrictions can obscure the subject. Record those factors in a short note. If a drone or other specialized capture method is used, follow applicable permissions, site policies and safety controls; aerial imagery is not a shortcut to inspecting hidden or inaccessible work.
Review quality before comparison
Before using an image as evidence, check that it opens, is legible at the required scale, has a reliable timestamp and can be tied to a location. Confirm the original has not been confused with a duplicate or an image from another area. Identify obstructions, glare, poor light, blur and changes in framing. These are not cosmetic details if they hide the work being assessed.
Comparison is strongest when the earlier and later views cover the same boundaries. If they do not, state the difference and narrow the conclusion. An image can support “visible steel members are present in this area” without proving that every connection is complete, inspected or accepted. Write the observation before the conclusion. Then link any remaining checks—inspection reports, test results, delivery records or an authorized sign-off—to the exact claim.
Make the routine workable for the site team
Use brief instructions and a field checklist. A capture record can ask: Is the viewpoint safe? Is the right zone visible? Is the view comparable? Is the date and source recorded? Are there people or sensitive details that need handling under the project’s rules? A supervisor should be able to explain how to submit a missed or changed view without inventing a substitute. Make capture part of existing site routines where possible rather than an extra process that competes with safe work.
Finally, keep responsibilities explicit. The person taking a photograph records an observation. The person matching it to a drawing or work package confirms the mapping. A qualified or authorized reviewer decides whether the combined evidence supports the milestone statement. This separation makes the trail more useful to project managers, site engineers and clients: each can see what is observed, what is inferred, and what remains open for human judgment.
Illustrative records on this page are schematic examples, not site photographs or proof of a real milestone.