Skip to content

Resource · workflow map

Map the work from brief to close-out.

Write down what each stage needs, who owns it and what the next person should receive. Start with the blank workflow map or inspect a fictional completed example.

Spectra guide · Source review: 3 November 2026

Use the working documents

Start blank, or inspect the clearly labelled fictional example.

Download editable CSVOpen printable A4 sheetOpen fictional completed exampleDownload fictional example CSV

At a glance

A reliable workflow carries context, state and responsibility together. Start with the hand-off that repeatedly causes reconstruction, then make its owner, release condition and exception route visible.

01 / Map

Give every hand-off an owner and an output.

Use the stages that reflect your operation—not an idealised diagram. For each stage, identify the input someone can rely on, the controlled output they create, and the condition that allows the job to move.

On the blank workflow map, use one row per stage the business actually runs. The fictional completed example shows how the columns read; copy that structure and replace every label with the person who can answer for the work. Do not treat the example names as a recommended organisation chart.

  • Enquiry and qualification
  • Survey and evidence
  • Estimate, quote and commercial review
  • Artwork, proof and approval
  • Production and quality control
  • Installation, collection or delivery
  • Invoice, actuals and close-out
Column on the blank mapWrite thisHold the stage when
accountable_ownerA person who can answer for the outputOnly a shared inbox is named
required_inputThe fact the next stage is allowed to trustThe fact is still an assumption
controlled_outputThe record the next person should receiveThe output is only a verbal note
release_conditionThe check that lets the job moveNobody can point to the check
exception_routeWho decides, and which record they updateA missing fact is copied forward

02 / Exceptions

Design the stop as carefully as the flow.

A useful map shows what happens when a dimension is missing, a proof changes, access disappears or a material is unavailable. Record who decides, what is updated and how the next person knows the hold has been resolved.

03 / Improve

Change one hand-off and measure it.

Choose a visible failure, agree the new rule and review a small run of jobs. Useful measures include time waiting for clarification, revisions caused by stale information and jobs released with open dependencies.

Bring the job. Explore the next step.

Discuss your workflow