The Compliance Horror Stories That Usually Start With “We’ll Sort That Later”

The Compliance Horror Stories That Usually Start With “We’ll Sort That Later”
At the time, it looked like a five-minute job.
The installer was heading to the next property. The office had a queue of files to review. Someone spotted a missing record and said the words everyone was relieved to hear.
“We’ll sort that later.”
Now it is month end. The person who remembers the detail is away, the work has been covered and the customer is asking for an update.
What looked like a small loose end has become hours of chasing.
Halloween may be the season for spooky stories, but a job file full of unanswered questions can cause enough concern on its own.
For PAS and MCS businesses, the cost can reach beyond a few late documents. Repeated gaps can delay reviews, lead to return visits and leave staff explaining decisions they can no longer clearly recall.
The useful question is what happens after someone says “later”.
Is the task recorded? Does it have an owner? Has anyone decided whether work can continue?
The following fictional examples show how everyday gaps can grow and how a clearer routine can help prevent them.
“We’ll find the photos later.” An installation team finishes a stage of work and moves on.
The required images have either not been taken or have been saved somewhere the office cannot find.
When the file is reviewed, the relevant detail is no longer visible.
The installer remembers doing the work. The office still needs to understand what can be shown and how the installation was checked.
A return visit may help establish some facts. A photograph taken now cannot show an earlier stage that has since been covered.
The next step needs an honest review by the right person.
Record the gap, establish what reliable evidence is available and agree any further inspection or action needed. Make clear when later evidence was created and what it shows.
Then look at why the problem happened.
Were the relevant pre, mid and post photos clearly identified? Could the installer access the guide? Was there a check before the work moved to the next stage?
Give the team a practical way to link images to the correct job and check their quality while missing detail can still be addressed.
Keep photographs alongside the other checks and records required for the installation.
The aim is to create useful evidence as the work progresses, so the file can be understood later.
“We’ll record the change later.” The product specified for a job is unavailable.
An alternative is suggested, and the team is keen to keep the installation moving.
A quick conversation takes place. The work changes, but the job instructions, design records and customer information remain as they were.
A few weeks later, the photographs show one product and the file describes another.
Nobody can easily establish who reviewed the change or what was agreed.
For PAS 2030 work, proposed variations to the retrofit design or location-specific method statement need to be documented and submitted to the Retrofit Coordinator for approval before installation work proceeds.
Build the relevant approval steps into the working process.
Staff should understand who can make the technical decision, what information is needed and when work must pause.
Keep the approved change with the job. Make sure the people carrying out and checking the installation receive the current information.
Review any effect on related work and the documents supplied to the customer.
For MCS installations, apply the relevant technology and scheme requirements when reviewing a proposed change. Keep technical decisions with people qualified and authorised to make them.
A message that says “fine to go ahead” needs enough context to show what was reviewed and approved.
Bring that information into the shared job record while the people involved can still confirm it.
“We’ll check that result later.” A test record arrives with a note that needs technical review.
The person handling the file sees that the document has been uploaded and moves the job to the next stage.
The note remains unanswered.
Later, someone asks how the concern was resolved. The record is present, but the decision is missing.
This is why it helps to distinguish between receiving a document and reviewing its content.
Agree who checks the technical results and how their decision is recorded. Give office staff a clear way to identify records awaiting that review.
If a result or observation raises a concern, the appropriate technical person needs to decide what happens next.
Record any further work, testing or inspection and its outcome.
Where there is a safety concern, respond promptly through the people and arrangements suitable for that risk. It should never sit unnoticed in a general list of unfinished paperwork.
Check what happens when the usual reviewer is unavailable.
The business needs a workable route for reaching an appropriate decision. Staff should know how to raise the issue and which tasks must wait.
A file can look busy and still leave the most important question unanswered.
Make the outcome of checks easy to find.
“We’ll do the handover later.” The system is operating, the team is packing up and the next appointment is already waiting.
The resident receives some documents and is told someone will explain the controls another day.
No appointment is recorded. The job is marked complete.
A week later, the customer is unsure how to use the system and has no clear contact for help.
Under the redeveloped MCS scheme, the Installer Operating Requirements call for an effective customer handover supported by the relevant technology checklist.
Plan the applicable handover steps as part of the job.
Allow time for the explanation, questions and the information the customer needs. Agree who is responsible for providing each part.
A useful handover should help the resident understand the improvements, how to use relevant controls and where to obtain support.
Where further contact is needed, record the arrangement and give it an owner.
Keep promises realistic. If someone is expecting a call on Tuesday, the person making that call needs to know.
Also consider whether information needs to reach another person who will use the system.
Check what has actually been explained and supplied before recording the handover as complete.
A clear record should reflect the customer’s experience of the service.
“We’ll deal with that action next month.” A review identifies the same missing information in several files.
Everyone agrees that the instructions need updating.
The action is added to a list, then carried forward at the next meeting. A new month begins and more jobs arrive with the same gap.
Eventually, the team has two problems: the affected jobs and an improvement that was never completed.
PAS 2030 includes requirements to investigate issues from internal reviews, address the occurrences, act to prevent them returning and check whether the corrective action has been effective.
Turn a finding into a clear task.
Describe what needs changing, who will do it and when it is due. Agree how the result will be checked.
If the instruction is updated, make sure staff receive the new version and understand how to use it. Remove outdated versions from the places people use.
Then review later work for the original gap.
An amended form shows that a document changed. Further checks help establish whether the new routine is working.
If the same problem continues, investigate why. The action may have missed the cause, or the people doing the work may need more support.
Keep the result of that review with the action record.
Month-end pressure can make “later” sound reasonable. Managers want an accurate view of completed work. Teams want to finish the current jobs and move on.
The pressure becomes harder to manage when different people use “complete” to mean different things.
One person may mean that site work has finished. Another may mean that technical checks, handover and required records have all been reviewed.
Define the stages used by your business.
Make it clear which tasks and approvals are needed at each stage and who confirms them.
Record outstanding items honestly. If the file is awaiting a technical decision, the people managing work need to see that status.
Keep the deadlines that apply to the installation and its certification visible. A company’s month-end routine needs to work alongside those requirements.
Check whether the way you report progress encourages staff to raise unfinished tasks.
An accurate list of open actions gives managers something they can address. A list that appears clear while concerns remain elsewhere can hide the work still needed.
Use month end to improve visibility of the position across the team.
Some tasks have an agreed place later in the programme. Record when they are due and confirm that preceding work can proceed under the relevant requirements. Problems grow when an essential check is missed or an action has no planned route to completion.
Look at why tasks keep being pushed back. People often delay something because another job appears more urgent.
Sometimes they lack the information, access or authority needed to finish it.
Ask what is stopping the task from being completed.
An installer may be unable to upload photos from site. An administrator may be waiting for a technical decision. A supervisor may have more work than can be checked properly in the time available.
Those situations need different responses.
Walk through the task with the people involved. Find where the work stops and what is needed to move it forward.
Check that instructions are clear and suitable for the people using them.
Review whether the schedule allows time for the required checks, records and customer explanations.
If several staff struggle with the same step, look closely at the way it has been organised.
Keep the discussion fair. Describe the gap and its effect, then agree a practical change.
People are more likely to provide useful detail when they can explain what happened without being dismissed.
Give an open task enough detail to be managed. A note that says “sort paperwork” tells the next person very little.
A useful entry identifies the job, the specific issue, its possible effect and the next action.
Name the person responsible and record the date agreed for that action.
Show who needs to make any technical decision and what information they need.
If an action depends on another task, make the link visible. The office should be able to see that a visit is awaiting approval or that a record needs review before the next step.
Review priorities against the actual risks and requirements.
A concern affecting safety or installation quality needs a different response from a filing query that does not affect the work.
Give both a clear route to resolution while responding appropriately to their urgency.
When an item is closed, record the outcome and the evidence used to confirm it.
That helps another colleague understand the position without starting the whole conversation again.
Use one shared record of the job. Important decisions can become difficult to trace when they remain in personal inboxes, phones or separate notebooks.
Agree where the current job information belongs and who needs access.
Bring relevant messages, approved changes and follow-up actions into that record.
Keep the latest instructions easy to identify while retaining the history needed to understand earlier decisions.
The redeveloped MCS Installer Operating Requirements include accessible, secure filing arrangements that keep an installation’s documents together and protect against their loss.
Choose a method your team can use reliably.
Check that staff understand how to name records, select the correct job and raise a missing item.
Make arrangements for absence and staff changes. Work should remain understandable when the person who usually deals with it is unavailable.
Use a sample of files to test how easily another suitable colleague can follow the recorded decisions.
The review can reveal gaps that familiar staff have stopped noticing.
Keep the people affected informed. A delayed task can leave a customer, installer or office colleague waiting without knowing what will happen next.
Agree who will provide updates and what they need to explain.
Tell the customer about changes that affect appointments, access, the agreed work or promised support.
Where more investigation is needed, give a realistic update and explain when they should expect further contact.
Keep those communications with the job.
Internally, make sure the people booking work understand what is ready and what remains subject to a decision.
A clear update can prevent another team arriving without the information needed to proceed.
It also helps managers see where support is required before the diary becomes harder to manage.
You can give your month-end review a useful focus with five steps.
- Find the open items.Bring together outstanding records, technical decisions, customer promises and actions from previous reviews. Check job files and the places where staff currently track unfinished work.
- Decide what needs attention first.Have suitable people review the effect of each issue. Act promptly on safety and quality concerns, and keep applicable deadlines in view when arranging the work.
- Give each action an owner.Describe the next step clearly and name the person responsible. Confirm that they have the time, information and authority needed, or a route to the person who does.
- Confirm the result before closing the item.Check that the required action has happened and record the outcome. Where a technical review is needed, make sure the right person has completed it.
- Use repeat gaps to improve the routine.Look for issues appearing across several jobs. Review their cause, make a suitable change and check later work to see whether the improvement has helped.
Keep the review proportionate to the work and use it often enough to act on concerns in time.
A useful meeting leaves people clear about what happens next.
The benefits of PAS and MCS consultant support can become clearer when the same loose ends keep returning. An outside review can help connect what happens in the office with what happens on site.
A consultant can help review relevant requirements, examine sample records and identify where instructions or staff responsibilities need attention.
That support may include improving job checklists, helping managers track actions or clarifying how information moves between teams.
It can also help identify where further technical training, specialist advice or assessment needs arranging.
Keep technical decisions with people suitable for those tasks.
The value of support comes from making the working process clearer and easier to maintain. Test proposed changes with the people expected to use them.
Ask whether the new routine helps them complete the task at the right time and makes outstanding work easier to see.
Then review actual jobs for evidence that the change has helped.
This Halloween, take a look at the tasks your team has been carrying from one week to the next.
Choose one that regularly creates chasing or uncertainty.
Find out why it remains open, agree the next action and give it an owner. If the same issue appears on other jobs, review the cause and improve the process behind it.
PAS and MCS compliance becomes easier to manage when unfinished work is visible and decisions are followed through.
There will always be tasks to complete. The important part is knowing what they are, who is dealing with them and how the result will be checked.
Speak to Compliant about your certification plans and how PAS and MCS consultant support could help you improve installation evidence, clarify responsibilities and prevent repeated gaps from following your team into another month.



