SpectraResource · workflow map
Seven hand-offs. One accountable job trail.
Map who owns the next action, what they need, and what happens when a job cannot move.
Published by Spectra · no named expert reviewer is claimed · last reviewed 17 September 2026 · operational guidance, not technical, legal or safety certification.
The practical answer
A reliable workflow carries context, state and responsibility together. It is a working aid, not a promise that software, a checklist or a single person can resolve every exception.
Map
Give every hand-off an owner and an output.
Start with enquiry, survey, estimate, proof, production, installation and close-out. At each stage, name the record the next person receives and the condition that permits release.
| Stage | Owner | Required output | Exception path |
|---|---|---|---|
| Survey | Survey lead | Referenced measurements and open questions | Hold estimate; request missing access or qualified review |
| Proof | Artwork lead | Issued version and decision | Revise, then reissue against the same job |
| Installation | Install lead | Completion record and exceptions | Return visit or commercial review owner |
Worked sample
Follow a fictional fascia job through the breaks.
Synthetic sample: North Quay Café requests an illuminated fascia. The survey record says the fascia width is supplied, not independently verified; access timing is still open. Estimating therefore releases a provisional scope, not a production instruction.
Use with care
A workflow map does not authorise technical decisions.
Keep safety, structural, electrical, planning, contractual and brand-authority decisions with competent people and the records your business uses for them. The sheet deliberately records unknowns instead of interpreting them.
A sample, not a promise