Resources • findings • quote • approval
From findings → quote → approval: a repeatable workflow
A practical workflow for moving from on-site findings to a client-ready quote and approval — keeping evidence and scope joined up door-by-door.
- Inspections
- Quotes
- Approval
- Evidence
- Portal
Approvals become faster when evidence, scope, and door identity
stay linked
A practical workflow for moving from on-site findings to a client-ready quote — keeping everything joined up door-by-door so approval conversations are short and factual.
Goal 01
Record consistently
Stable door identity and a repeatable evidence pack — outcome, note, photo, location — captured the same way by every inspector on every door. The quote is only as good as the record it's built from.
Goal 02
Convert from the record
Build quote scope from findings, not from memory or a retyped spreadsheet. Grouped by area, with mapped line items and explicit assumptions — so scope stays attached to the door-level evidence that justified it.
Goal 03
Close the loop
Handoff to remedials with sign-off evidence attached — before/after photos and approval trail tied to the same door record. The job closes on the same chain of evidence it started on.
Inspection teams
Keep findings consistent so scope can be built repeatably — outcome, note, photo, and location captured the same way every time.
Commercial teams
Turn findings into quote scope without losing door-level traceability — grouped, mapped line items converted directly from the record.
Project leads
Keep approvals, revisions, and handoff tied to the underlying record — a decision trail that answers "who approved what, and when" without email archaeology.
Most scope arguments happen because the inspection record was ambiguous —
start clean
Five things to settle before the site day. Each one prevents a specific class of problem downstream — in the quote, the approval, or the remedials handoff.
Five decisions before the site day
Client & property structure
Create properties, floors, and areas so locations stay consistent across every inspector who visits. Inconsistent location naming breaks filters, reports, and quote grouping downstream.
Door identity
Decide how door IDs are assigned and never reused. A door ID that changes between visits fragments the record — the quote for visit 2 can't reference the findings from visit 1.
Inspection checklist
Confirm that inspection components and quick reasons match your reporting needs. If the checklist items don't map to the line items in your quotes, the conversion step requires manual interpretation on every job.
Inspection status
Remedial quotes generated from inspection failures require the inspection to be marked Completed in Fire Door App. Confirm the right person has permission to mark completion before the site day.
Roles
Ensure the right people can create quotes and exports, not just capture findings. A permissions gap discovered after the inspection — when someone needs to generate the quote urgently — delays the whole workflow.
Evidence and scope split across tools — use this when quotes and approvals are slowing down because inspectors, commercial teams, and project leads are working from different records.
A quote is only as good as
the record it's based on
Four components of a consistent evidence pack — captured the same way by every inspector, for every door. Make audits and approvals predictable.
Four components · same every door · same every inspector
Evidence 01
Outcome
Pass or fail, with consistent severity rules applied the same way every time. If "fail" means different things to different inspectors, the quote scope will reflect that inconsistency and every approval conversation becomes a scope argument.
Evidence 02
Notes
Short, factual, and door-specific. "Gap at bottom of door exceeds 3mm threshold" is a note. "Needs work" is not. Notes that could apply to any door generate scope disputes; specific notes generate line items.
Evidence 03
Photos
Clear "why this failed" evidence — not just a door selfie. The photo should make the finding self-explanatory to someone who wasn't on site. Approval conversations shorten when the client can see what the inspector saw.
Evidence 04
Door location
Enough detail that a different person can find the right opening on a return visit. Building, floor, area, and a stable door ID — not "the third door on the right" or a description that changes depending on which entrance you came in from.
Build quote scope from the record —
not from memory or a separate spreadsheet
Three steps that keep door-level traceability intact through to the quote. Scope that drifts from the record generates revision requests; scope that stays attached to findings gets approved.
Capture → QA → Complete → Quote
Step 01
Group by building and area
Keep scope navigable for clients — grouped by building and area, not a flat list of door IDs. Grouped scope reduces "which door is this?" questions in approval. Clients approve what they can orient to.
Step 02
Use mapped line items where possible
Mapped items standardise wording and pricing so line items read consistently across quotes. Manual edits handle genuine exceptions — but starting from a mapped item means descriptions, units, and pricing stay coherent.
Pricing & CSV mapping guideStep 03
Make assumptions explicit
If something is unknown until opened up, include a separate "investigate / open up" line item and document the assumption. Approval stalls when clients discover assumptions they weren't told about — price the unknown openly.
In-app flow: capture → QA → mark inspection Completed → generate quote from the same record. Generating from a completed inspection ties the scope directly to the finding evidence.
Template · assumptions / exclusions block
Use on every quote so approvals don't stall on ambiguity
01
Access
Access & opening-up
What you assumed was accessible without invasive works — if opening-up is required, price it separately as a line item.
02
Spec
Like-for-like replacement
Whether replacement is assumed like-for-like unless otherwise stated in the quote. Upgrades are a separate scope conversation.
03
Unknowns
Investigate / open-up items
How you handle items that need investigation — these get a separate line item with an "investigate / open up" description, not absorbed into other scope.
04
Hours
Working hours & permits
Whether work is in-hours or out-of-hours, and any permit-to-work constraints that could affect price or scheduling.
Approvals get easier when everyone is looking at
the same evidence and the same scope
Three rules that keep the approval conversation on the record — not in email threads and verbal summaries that diverge from what was actually quoted.
Three rules · one source · one decision trail
Rule 01
One source of truth
Send the quote from the system record, not as a retyped email or a PDF assembled from multiple tools. When clients receive the same document that your team is working from, there's no "which version are we discussing?" overhead.
Rule 02
Evidence references
Point to door IDs and findings that justify each line item. "Replace door bottom seal — FD-027, FD-031" is a quotable line item. "Replace seals (various)" is an invitation to negotiate every item. Specificity shortens approval cycles.
Rule 03
Decision trail
Record who approved, when, and which version. This is workflow support, not legal advice — but an approval trail means you can answer "did you approve quote v2?" without reconstructing an email thread six months later.
Template · approval message
Keep it short — point to the record, request one decision
Message content
What changed
"Quote v2 includes items for doors FD-012 to FD-019 (photos attached per door)."
Decision requested
Accept / reject / request clarification — with a single named owner for the decision.
Assumptions
Include the standard assumptions block or link to it — don't assume it was read in the previous version.
Logistics
Next step
"On approval we schedule remedials for week commencing [W/C DATE] or next available slot."
Access contact
"For site access and permits, please confirm the nominated contact for [SITE]."
One channel only
Don't send one list by email and a different version in the PDF or portal — same document, one channel.
Once scope is agreed, keep the same door-level evidence trail
through close-out
Three handoff rules to preserve traceability from approval to sign-off — then four pitfalls that consistently stall approvals or force the job back to rework.
Handoff to remedials
Three rules to keep evidence intact through close-out
Keep work grouped
Projects organised by building or phase reduce site friction — teams know which doors they're visiting, in what order, without cross-referencing a flat list and a PDF separately.
Close-out evidence
Before/after photos and sign-off notes attached to the door record — not filed in a shared folder or emailed separately. Evidence that's attached is evidence that travels with the record to the next audit.
Remedials prioritisationOutputs from the record
Export from the live record so door lists and totals stay consistent. A PDF manually assembled in Word after the fact is a statement; a PDF generated from the record is traceable evidence.
Common pitfalls · where approvals stall
Evidence
Scope without evidence
If clients can't trace a line item to door IDs or findings, confidence in the quote drops — and they ask for site revisits, more photos, or revised scope before approving. All of which cost more time than capturing the evidence properly on day one.
Fix: minimum evidence per door — outcome, specific note, photo of the failure, and stable door ID — before generating the quote.
Scope control
Changing scope after sign-off
Adding or removing doors after a quote is approved without re-issuing creates a mismatch between what was approved and what gets invoiced. The approval record says one thing; the invoice says another. Disputes follow.
Fix: if scope changes after sign-off, re-issue as v2 with a clear revision marker — note what changed and get sign-off on the revised version.
Assumptions
Unclear "open up / investigate" items
If investigation items are folded into other line items without being explicit, approvals stall when the open-up cost arrives as a surprise. Clients who felt they approved "replace seal" don't expect an additional charge to investigate what's behind it.
Fix: price "investigate / open up" as a separate, explicit line item every time. If the cost is unknown, say so — name it and give a range.
Consistency
Multiple channels, multiple versions
Sending one scope list by email and a different one in the PDF or portal is the fastest way to create a disputed approval. One version is approved verbally, a different version goes to site. The client can point to the email; you can point to the PDF. Neither is wrong.
Fix: one document, one channel. Send the quote from the system and have the client respond to that same document — not a summary email alongside it.
Quick answers on quoting order, scope drift, evidence,
and platform boundaries
Four questions that come up when teams are formalising the inspection-to-approval workflow for the first time or moving off spreadsheets and email threads.
Workflow sequence
Most teams quote from inspection findings first, then schedule remedials once scope is agreed. This keeps the approval loop clean — the client sees findings, approves scope, then work is scheduled. There's no risk of arriving on site before the quote is approved.
For unknowns — items that need opening up to scope properly — include an explicit "investigate / open up" line item in the quote. Capture the assumption, price it separately, and get approval on that line item before sending the remedials team in.
Three things together: keep door IDs stable so the record doesn't fragment, attach photo evidence to each door at the time of capture, and convert findings into quote scope from the same record — not from a retyped summary in a separate spreadsheet.
Scope drift usually starts at the transition point — the moment someone re-enters findings from the inspection into a quoting tool. Every manual re-entry is a chance for scope to diverge from the original record. Generating the quote from the finding keeps them joined.
Evidence & platform boundaries
Minimum pack: stable door identity and location (building, floor, area, and door ID), clear pass/fail outcome with consistent severity, and photos that show the failure — not the whole door, but the specific finding being quoted.
This keeps approval conversations short and factual. When a client can open the quote, see "FD-027 · Block A · Level 02 · gap exceeds threshold" with a photo of the gap, there's nothing left to dispute. The evidence makes the line item self-explanatory.
No. Fire Door App supports workflows and evidence retention — the platform helps you capture findings consistently, convert them to quote scope without retyping, and keep approvals attached to the record. It does not determine what remedial work is required.
Competent-person decisions — what the finding means, what the correct remediation is, and the final scope — remain entirely your responsibility. The platform makes those decisions easier to document and trace, not easier to skip.
Quick facts
Inspection → quote → approval at a glance
Sequence
Inspect → quote → approve → remedials. Open-up items as explicit line items
Evidence minimum
Door ID + location, pass/fail + severity, photo of the failure — per door, before quoting
No drift
Convert findings to scope from the same record — no retyping into a separate tool
Assumptions
Open-up and unknowns as separate explicit line items — never absorbed into other scope
One channel
One document, one version in circulation — don't send an email summary alongside the PDF
Platform boundary
FDA handles workflow + evidence. Competent-person scope decisions remain yours
Get started
Run one joined-up workflow end-to-end
Capture findings on site, generate the quote from the same record, and keep approval and handover evidence attached to each door.
Run one joined-up workflow end-to-end.
Then compare to email-and-spreadsheet handoffs.
Capture findings on site, generate quote scope from the same door records, and keep approval evidence attached so close-out stays traceable.