Supervision and sign-off records

Who did the work?

Clients may ask for named individuals, not only a trading name.

Record who attended site for installation, inspection or remedial tasks. Subcontractor arrangements should be transparent where relevant.

Skills, Knowledge, Experience and Behaviours (SKEB) relate to the people doing the task — link names to task-specific competence where possible.

• Named operative(s) on site recorded
• Role or task for each person noted (install, inspect, remedial)
• Subcontractor involvement disclosed where applicable
• Substitutions on site documented if different from planned team
• Contact for technical queries after handover provided

Key takeaway: Named operatives help buyers understand who was responsible on the day — company branding alone is often insufficient.

Who supervised?

Supervision shows oversight beyond the individual operative.

Identify the supervisor — internal senior installer, contract manager, manufacturer representative or inspector — and their relationship to the work.

Supervision frequency may vary by project size, risk and company procedures. Document what applied on this job.

• Supervisor name and job role recorded
• Supervisor competence basis briefly noted (SKEB, not badge alone)
• Whether supervision was remote or on site stated
• Supervisor contact details for follow-up provided
• Different supervisors for installation vs inspection distinguished where both apply

Key takeaway: Supervision records should identify a real person with a defined oversight role — not a generic company signature.

What was checked?

Sign-off should list checks that were actually performed.

Examples may include frame condition, gaps, seal continuity, closer operation, latch engagement, glazing integrity, signage and clearances — depending on scope.

Tick-box templates are useful only if they reflect site-specific verification.

• Pre-work condition check recorded where relevant
• Installation or remedial steps verified
• Functional tests noted (closer, latch, seals)
• Visual checks and measurements recorded where performed
• Items not checked explicitly listed as limitations

Key takeaway: Generic ‘signed off’ statements without check detail answer few buyer questions.

How often were checks carried out?

Document the supervision pattern for the project.

Single-day jobs may have one pre-handover check. Larger projects may need stage inspections — frame fix, seal install, final commissioning.

Record dates and stages so the trail is clear.

• Stage inspection dates recorded for multi-stage work
• Final pre-handover check date recorded
• Interim hold points noted where work paused for review
• Re-inspection after snagging documented
• Remote check-ins logged where used (with limits stated)

Key takeaway: Frequency should match project complexity — a single checkbox rarely fits every job.

What evidence supports sign-off?

Sign-off may be supported by photos, measurements, product records and method notes.

Link sign-off to supporting evidence in the installation or remedial pack — not a standalone signature with no context.

Inspection sign-off may reference report findings; installation sign-off may reference gap checks and functional tests.

• Supporting photos or measurement notes referenced
• Product evidence cross-referenced where relevant
• Inspection report ID linked for inspection sign-off
• Snag list closed or outstanding items listed at sign-off
• Digital or paper file location noted

Key takeaway: Sign-off supported by evidence is easier to explain later than unsupported assertions.

What happens when work is outside competence or scope?

Escalation and refusal behaviours are part of competent practice.

Document when work was stopped, referred to others or declined because it was outside competence, missing product evidence or beyond agreed scope.

Behaviours — honesty about limits, refusing unsafe shortcuts, documenting disagreements — matter as much as certificates.

• Work stopped or escalated — reason recorded
• Alternative competent person or contractor identified where possible
• Client informed in writing of limitation or refusal
• Partial completion and outstanding risks documented
• No sign-off claimed for unchecked or incomplete work

Key takeaway: Good records include what you did not do and why — not only completed tasks.

Why one badge or certificate may not answer all supervision questions

Certification can be useful — but buyers may ask more.

A company-level certificate may not identify who was on site, what they checked today or whether supervision matched the specific door type.

Constructive approach: explain how certification relates to the task, then provide supervision and sign-off detail.

Do not attack certification schemes — use them as supporting evidence alongside SKEB and site records.

• Certification relevance to this task explained where claimed
• Gap between scheme scope and site task acknowledged honestly
• Site-specific supervision records provided alongside scheme credentials
• Client questions about operatives answered with names and roles
• No implication that FireDoorInstallation.com verified the certificate

Key takeaway: Combine certification with named people, checks and records — buyers often need both layers.