Photos, Records and Checks: Can Your Evidence Tell the Full Story?

The installation is finished. The team has moved on. Then someone asks to see a detail that is now hidden behind a finished surface.

You open the job folder.

There are plenty of photos, but the detail you need is missing. The check sheet has a tick in the right box, yet there is no clear result. A change was agreed on site, although nobody can find who approved it or when.

Now the office is calling installers. The supervisor is searching through messages. Someone is trying to explain a decision made several weeks ago.

Meanwhile, the customer is waiting for an answer.

This is how weak evidence can turn a completed installation into more work.

For businesses managing PAS and MCS evidence, the question is whether the information you keep explains what actually happened. A folder can look full and still leave important questions unanswered.

Useful evidence connects the agreed work, the installation, the checks and the handover. It helps the next person understand the job without needing everyone who worked on it in the room.

That takes planning, clear responsibilities and attention while the work is happening.

What does a complete account of the job look like?

Think about someone opening your installation records six months from now.

They may be responding to a customer question, reviewing a repair or assessing the work. They need enough information to understand the decisions and the outcome.

A useful starting point is to ask whether the file explains:

• What was planned and which information the team worked from.
• What the team found before and during installation.
• What was installed, including relevant locations and product details.
• What changed, why it changed and who authorised the decision.
• What was checked, the results and any action that followed.
• What the customer received and whether any work remained outstanding.

These questions help you review the file. The exact evidence needed will depend on the work and the requirements that apply.

You also need to see how the answers connect.

For example, a photograph of an equipment label may identify a product. The installation record should link that product to the correct property. The relevant design, commissioning information and handover documents should then relate to that same installation.

If those connections are missing, the reader has to make assumptions.

Good evidence reduces the need for those assumptions.

Agree the evidence before the work starts

It is much easier to capture a detail while it is visible than to explain its absence after the work is complete.

Build evidence planning into job preparation.

Look at the proposed installation and identify the points where someone needs to record information, take photographs or complete a check. Decide which details could become difficult to access later.

PAS 2030 covers the installation of energy efficiency measures in existing homes, alongside the wider retrofit requirements of PAS 2035. That means the evidence should relate to the particular measure, property and agreed design.

MCS work also needs to follow the requirements relevant to the technology and scheme version. During the phased move to the redeveloped MCS scheme, businesses may be operating under different versions, so check which applies to your work.

Turn the applicable requirements into clear instructions that the team can use.

“Take the usual photos” leaves too much open to interpretation.

A more useful instruction identifies the stage, location, detail and purpose. Explain who captures it and who checks that it is usable before the work moves on.

Make these arrangements clear to subcontractors too.

If a team is joining you for the first time, show them what you expect. Do not wait until their first completed job to discover that their understanding was different.

Give every photograph a purpose

A photo should help answer a question.

Before taking it, ask what someone needs to learn from the image. Is it showing the starting condition, a particular installation detail, a product identifier or the finished arrangement?

A close view may show detail clearly while leaving the location uncertain. A wider view may show the location while hiding the detail.

Where useful, capture both and link them.

For PAS 2030, photographic records are required for installation work that will be covered or become inaccessible. The photographs need sufficient detail to demonstrate the work against the design and method statement, with date and location marked automatically by the camera.

Check that your capture method actually produces the required information. Adding a date to a filename later does not meet that camera-marking requirement.

Beyond those requirements, a practical habit is to look at the image immediately.

Can you see the intended detail? Is the lighting good enough? Is the label readable? Could a colleague understand which part of the job it shows?

If the answer is unclear, correct the image while you still have access.

Also be realistic about what a photograph can establish. A neat finished surface cannot explain the construction behind it. A picture of a working display cannot provide every required test result.

Use the image for the information it can show, and connect it to the appropriate records and checks.

Record decisions while the details are fresh

Installation records need to explain the choices made during the job.

That becomes especially important when circumstances change.

Perhaps the team finds a condition that affects the proposed work. A product is unavailable. The customer asks for a different arrangement. Someone raises a question about the design.

Each situation needs an appropriate response, and the file should make that response understandable.

A short, useful change record can explain what was found, why the original arrangement needed reviewing, who considered the issue and what was agreed.

It should also show how the revised information reached the people doing the work.

Consider a simple example.

A team records: “Position changed.”

The person reading that later still needs to know which item moved, where it moved to, why the move was needed and whether the relevant people agreed.

A clearer account links the issue to the revised drawing or instruction, records the decision and points to evidence of the completed arrangement.

Keep the technical decision and the customer discussion clear. Customer agreement alone does not establish that a technical change is suitable.

You do not need a long account of every conversation. You need enough relevant detail to explain decisions that affect the installation.

Capture that information while the people involved can check it accurately.

Make checks show a result and a response

A tick tells the reader that someone marked a box. Its meaning depends on the question, the check and the information recorded.

Some checks may be suitably recorded with a clear pass or fail. Others need readings, settings, observations or supporting documents.

Review your forms with that distinction in mind.

“Installation checked” is difficult to assess if nobody can tell what the check covered. Where a reading is required, “all good” leaves the result unclear.

A useful check record identifies the job, the item checked, the relevant requirement or procedure, the result and the person responsible.

It should also show what happened when the result needed attention.

For heat pumps, MCS installation standard MIS 3005-I requires commissioning against a documented procedure covering safety, installation requirements, manufacturer requirements and operation against the system design.

Your forms and results should make the relevant commissioning work understandable. Use the applicable technology requirements rather than assuming one general sheet covers everything.

When a check finds a problem, follow the record through.

What needed correcting? Who took responsibility? What action was completed? How was the outcome checked?

A correction recorded without its follow-up can leave the reader uncertain about the final condition.

Also distinguish office checks from technical checks. Confirming that a document has been uploaded is useful administration. Judging whether a technical result is acceptable needs someone with the appropriate competence and authority.

Both tasks matter, and each needs a clear owner.

Check that the records agree with each other

Individual records can appear reasonable while the job file as a whole contains contradictions.

The quotation names one model. The equipment photograph shows another. A drawing has been revised, but the completion form still refers to the earlier version.

These differences deserve attention.

Start with the information that links the file together: the job reference, property, relevant equipment, installation dates and document versions.

Then follow the sequence.

If the design changed, can you see which version the team used? If a problem was recorded, can you find the action and follow-up? If the customer was promised a further visit, does the file show its outcome or current status?

An apparent contradiction may have a simple explanation. The problem arises when that explanation remains only in someone’s memory.

Record it clearly and correct errors in a way that preserves the history.

For instance, if a product identifier was entered incorrectly, make the correction traceable. Show what changed, when and why, following your record-control arrangements.

Avoid silently replacing information where that would leave others working from conflicting copies.

A consistent job file helps the office answer questions confidently. It also makes it easier for someone returning to site to understand the actual installation.

Give each person a clear part in the evidence

Evidence can slip between teams when everyone believes someone else is handling it.

The installer takes the photos but assumes the supervisor will upload them. The supervisor expects the office to check the folder. The office assumes that a completed folder means the technical checks have been accepted.

Make the responsibilities visible.

Installers need practical instructions about what to capture and when. Supervisors need to know which details require review before the next stage. Office staff need a clear way to identify missing documents and pass technical questions to the right person.

Managers need to provide enough time, suitable tools and cover for absences.

A named owner for the file can help coordinate these tasks. That person does not have to carry out every check, but they should know who is responsible and how outstanding matters are followed up.

Include the handover between site and office in your planning.

How does the office know the site evidence is ready? What happens if an upload fails? Who checks that a promised record has arrived?

Try the process with the people who use it.

Instructions that seem clear at a desk may be awkward on a phone, in poor lighting or with an unreliable connection. Their feedback can help you make evidence capture easier to complete properly.

Keep the file easy to find and use

Evidence has limited value if the people who need it cannot find it.

A photo on one person’s phone, a revised drawing in an email and a commissioning sheet in a separate folder create extra searching.

Under the redeveloped MCS Installer Operating Requirements, installation records must be retained for at least six years. The requirements also call for a simple, accessible and secure filing system that brings an installation’s documentation together.

Choose an arrangement your team can use consistently.

You might organise each job around preparation, site work, checks, changes and handover. Use clear names, dates and references so someone can follow the sequence.

Keep original photographs and ensure they remain linked to the relevant job. If you create an annotated copy to explain a detail, retain the original too.

Make sure the right people can retrieve records when someone is absent. Check that your arrangements protect the information and allow recovery if a device fails.

PAS 2030 requires installation process records to be kept for six years or the term of the relevant guarantees, whichever is longer. Make sure your storage arrangements support the applicable retention period.

The aim is to make the file useful during the installation and when questions arise later.

Include what happened at handover

A finished installation still needs a clear handover.

The customer may need help using controls, understanding maintenance or finding the right contact when they have a question.

For installers operating under the redeveloped MCS scheme, the Customer Commitment includes demonstrating the system, explaining its use and providing relevant manuals, maintenance information, guarantees and support details.

Your record should help explain what the customer actually received.

Was the demonstration completed? Which documents were provided? Were questions answered? Was any further work agreed?

A signature alone may leave those details unclear.

For example, if the customer asks for another explanation of a control, record the follow-up arrangement. Give it an owner and show when it was completed.

Keep any outstanding work visible too.

A note saying “return visit needed” is more useful when it explains the task, the person responsible and the agreed next step.

This helps the office support the customer after the installation team has left. It also reduces the chance of a promise being lost between departments.

The evidence should reflect the handover that took place, including anything still awaiting attention.

Deal openly with gaps

Sometimes a record is missing.

The photograph was not taken. A form was incomplete. An important discussion happened, but the decision was not properly recorded.

When you find a gap, establish what you know and what still needs checking.

Look for genuine supporting information. Ask the people involved for an accurate account, and clearly identify any explanation recorded later.

Keep the timing clear. A photograph taken during a return visit should be identified as evidence from that visit.

A statement based on someone’s recollection should be described that way. It should not appear to be a record completed at the time.

Never fill a gap by inventing a result, backdating a form or using a photograph from another installation.

Where missing evidence affects confidence in the work, ask an appropriately competent person to decide what further inspection, testing or action is needed.

Then record the response and its outcome.

The missing information is also a chance to improve the process.

Was the instruction unclear? Did the team lack access to the system? Was there no review before the work became hidden?

Find the reason and address it. Otherwise, the same gap may appear in the next folder, leaving another person to search for answers.

Review a job with someone who was not there

A useful way to test your PAS and MCS evidence is to give a recent file to someone who did not work on the installation.

Choose someone suitable for the questions you are asking. A colleague can test whether the file is understandable; technical conclusions still need the right competence.

Ask them to follow the job from preparation to handover.

Let them identify where they need an explanation. Those questions show where the records may be relying on shared knowledge.

Could they identify the final agreed design? Could they connect photographs to locations? Could they see the results of checks and what happened after a problem?

Did they know which work was complete and which actions remained open?

Review an ordinary job as well as more complex work.

A routine installation can reveal habits that are easy to overlook when everyone is familiar with the task. Different teams and subcontractors may also expose different gaps.

Use the findings to improve instructions, forms or handovers between people.

Then look at a later job to see whether the change helped. A revised form only adds value when the team can use it to create clearer, more reliable records.

Start with one question your evidence should answer

You can make a useful improvement without redesigning every form at once.

Pick one recent installation and one important question.

It could be: “Which design did the team follow?” Or: “What happened after this check identified a problem?”

Follow the evidence needed to answer it.

Look at the photograph, the relevant instruction, the result and the action. Notice where the reader has to guess or call someone for missing context.

Agree one improvement before the next suitable job starts.

Perhaps it is a clearer photograph instruction. Perhaps a check needs a result field. Perhaps a change needs an owner who makes sure everyone receives the revision.

Explain the improvement to the people using it, then review the next file together.

Photos, records and checks are most useful when they connect. They should help your team understand the work, answer customer questions and make sound decisions about what happens next.

Open one ordinary job folder this week.

Can you follow the whole installation through the evidence, or are important parts of the account still held in someone’s memory?