What does project evidence actually prove?

What project evidence is for

Construction produces important facts that disappear quickly. Pipes are covered. Reinforcement is encased in concrete. Product labels are discarded. A site instruction is remembered differently. Certificates remain in somebody’s inbox.

A shared project record preserves selected information while it is available and links it to the work, requirement, event or decision it concerns.

That can help a customer understand progress, review a milestone, ask a precise question, maintain the finished work and show a later professional what happened.

It does not turn Assurr into an inspector.

Different evidence answers different questions

A photograph may show a visible condition at a particular time. It may not show what is hidden behind the work, whether a measurement is accurate or whether an installation complies technically.

A product label may identify a material. It does not prove correct installation.

A delivery note may show that goods arrived. It does not prove they were used on the project.

A certificate records the statement, test or outcome within its scope. It does not certify unrelated work.

A marked-up drawing may show an intended or as-built arrangement. It does not prove that the arrangement was accepted unless the approval is recorded separately.

The useful question is:

What does this evidence support, and what further decision or expertise is still required?

Evidence should not make the customer the surveyor

Customers often worry that a platform showing photographs will expect them to judge specialist work. That should not be the role.

If the project requires a test, certificate, inspection or professional decision, that requirement should be explicit. The customer can check whether the expected record exists and ask for clarification. They should not be forced to make a technical judgement outside their knowledge merely because a payment is waiting.

Evidence is not surveillance

More files do not automatically create more protection.

A stream of two hundred unlabelled photographs can make the project harder to understand. It burdens the contractor, overwhelms the customer and makes important facts difficult to find.

Assurr’s governing principle is evidence by significance and exception.

Capture information when it helps answer a foreseeable future question, particularly when:

• work is about to be concealed;
• a milestone criterion depends on it;
• a specified product matters;
• a test, inspection or delivery occurred;
• a customer selection or instruction affects responsibility;
• the project changed;
• an issue was corrected;
• a payment request relies on it.

The project should establish proportionate expectations before work. A small decorating job and a major structural alteration should not carry the same evidence burden.

What makes evidence useful?

Useful evidence is:

• linked to the exact work, requirement or event;
• dated and attributed;
• labelled with location and context;
• captured while the relevant detail is visible;
• clear enough to understand later;
• preserved with its history;
• visible to the appropriate participants.

A photograph called `IMG_4837` is much less useful than “Utility wall, waterproof membrane before boarding, 14 September”. Context makes the image part of the project record rather than merely a file.

What should you do if evidence is missing?

Absence of a photograph is not automatic proof that the work is wrong. Ask what evidence was agreed, whether another record exists and whether the work can still be inspected.

Raise the question before concealment if possible. If the work is already covered, the response depends on the importance of the requirement, the contract and professional advice. Assurr cannot decide whether opening work is justified.

Building Control, professional evidence and approval

Keep these events distinct:

• Building Control attended or recorded an outcome;
• a professional gave an opinion or certificate;
• the contractor submitted a milestone;
• the customer recorded a review decision;
• a payment instruction was created;
• work later proved to have a defect.

One can inform another without becoming the same fact.

The shared record

Assurr connects evidence with accepted scope, changes, milestones, queries and decisions. Each item stays in context and the chronology shows what was known at the time.

Assurr does not determine whether an image is technically sufficient. It does not determine whether an image is genuine unless a specific verified mechanism explicitly says so. It does not certify compliance or decide a dispute by counting files.

The aim is simpler: make important project facts easier for both sides to see, understand and use.