Quick answer: A useful snag record states where the issue is, what was observed, why it matters and what evidence is needed for closure. Blackstone supports structured construction inspections with checklists and photo evidence; the responsible project team still verifies the corrective work.
A photograph in a messaging group is easy to send and difficult to close. The location may be unclear, the responsible trade may change and the final image may show a different area. A structured snagging workflow gives each finding a stable reference and keeps the evidence connected from the first site walk to the follow-up inspection.
Prepare the site walk around the work scope
Choose a checklist that matches the inspection purpose: daily safety, quality control, snagging or handover. Define the site, building, level and area before recording findings. Use the current drawing or specification as the reference where relevant. A checklist helps organise observation; it does not replace the judgement of a competent inspector.
Write a finding another person can locate
Describe the observed condition in plain language. Add the exact location, affected element and reference requirement. Include a context photograph and a closer image when detail matters. Severity should reflect the project risk rather than how dramatic the photo looks. Blackstone's published workflow includes checklists, severity tagging and GPS-stamped photo evidence.
Make the corrective action clear
Identify the responsible trade or project contact and agree the next action through the project's normal process. State what an acceptable correction would look like and which checks will be repeated. Avoid the vague instruction 'please fix'. A useful finding separates the observed fact from the proposed remedy, especially where a designer or specialist must decide the solution.
Reinspect rather than closing on a message
A contractor's statement that work is complete should trigger verification. Revisit the recorded location, compare the corrected work with the requirement and capture follow-up evidence. Where testing is necessary, record the method and result. Keep unresolved or partially corrected findings visible. This is a recommended project workflow, not a claim that every step is automated by software.
Make the handover record understandable
Before sharing the report, check location names, photo references, statuses and any inspection limitations. Keep the initial observation and subsequent verification linked through a consistent reference. Blackstone provides an offline inspection and reporting workflow; connectivity and device permissions should be checked before a field visit. Software improves organisation, while the project team remains responsible for technical acceptance.
Buyer checklist
- Each finding has a location and stable reference.
- Photographs show context and relevant detail.
- The responsible party and acceptance requirement are clear.
- Closure follows verification and recorded evidence.
Frequently asked questions
Does GPS identify the exact room?
Not by itself. Record building, level and room or area as well as available location evidence.
Can software decide whether remedial work is safe?
No. Technical acceptance belongs to the competent person responsible for the work.
Is this the same as home inspection?
No. This article covers construction snagging and site workflows; Blackslate addresses a separate home-inspection use case.
Useful next steps
Explore the service · Discuss your requirements