Chapter 02
Coverage by workflow, not by area
Why coverage planned by area produces gaps the workflows hit, and how planning by workflow first inverts the failure mode without abandoning the safety and security overlays that area-led plans get right.
01
The area-led trap
The most common capture plan is a site map with cameras dropped at the corners of zones. Each zone gets one fixed view, plus a 360 route or two, and the planner ticks the box. The trap is that the workflows do not run by zone. Progress verification follows the package — the steel frame moves, the cladding chases it, the fitout follows the cladding. Claims evidence follows the activity — a stand-down claim wants the gate, the access road, and the affected front, not the whole site. Safety monitoring follows the high-risk operation — a lift over a live road, a confined-space entry, a hot-works permit. An area-led plan inevitably has gaps where the workflows actually need evidence and surplus where they do not. The map looks comprehensive and the workflows still miss.
02
Workflow-led coverage, in practice
Workflow-led coverage starts from each workflow and asks what evidence it needs. The evidence shapes the capture sources, the cadence, and the retention. The plan then maps these onto the site. Some areas attract heavy coverage because they sit at workflow intersections — a gate that serves logistics, attendance, and incident readiness will have multiple sources. Other areas attract lighter coverage because no workflow needs them — a finished basement after the structural sign-off does not need the same density as a live floor. The plan looks uneven on a map and even on the workflows. That is the right shape. A plan that looks even on the map is almost always uneven on the workflows the project actually runs.
03
Tower crane, fixed views, and the structural frame
A worked example. On a high-rise structural job, the workflows in scope are progress verification, claims, monthly stakeholder reporting, and incident readiness. The capture set that closes them is a tower crane camera as the primary wide shot, two fixed views at the principal elevations to track the frame as it climbs, and a gate camera for deliveries. The crane camera serves progress, reporting, and incident readiness as a single source. The elevation cameras serve claims and as-built. The gate camera serves logistics and attendance. Five sources cover four workflows. An area-led plan for the same site might place eight cameras to cover the perimeter and still miss the crane shot, because the perimeter view is what feels comprehensive on the map.
04
Where area overlays still earn their place
Workflow-led coverage does not replace area thinking entirely. Some areas need coverage for safety regardless of which workflows touch them — a permit-controlled high-risk zone, a lay-down area with public road exposure. Some areas need coverage for security — a compound holding plant, a perimeter at a project with theft history. The discipline is to start workflow-led, list the residual risks the workflow plan does not cover, and add area-led overlays as named exceptions. The exceptions sit on the plan with their justification written next to them. A capture source without a workflow or a named overlay should come off the plan at the next revision.
05
Failure modes from mixed methods
The most common failure is a hybrid plan that calls itself workflow-led but is area-led under the surface. Symptoms: every floor of a tower has the same density of capture even though the workflows shift floor by floor; a 360 route is identical across packages even though MEP needs a different cadence than fitout; gate coverage is treated as one source when the project actually has three gates with different traffic profiles. The fix is not to redraft the plan from scratch but to walk it workflow by workflow, asking which sources each workflow uses and removing the ones with no taker. The plan that emerges is leaner, defensible at audit, and easier to revise.
Practice
01. Pick a workflow from your current programme. Sketch the minimum capture set that would close it. Identify the first capture point you would cut if budget halved, and explain why that point is the least load-bearing for the workflow.
Look for: A practitioner answer names a workflow such as progress verification on the structural frame, lists the tower crane camera, two elevation views, and a gate camera as the minimum set, and identifies the second elevation view as the first cut because the crane camera plus one elevation gives adequate angle redundancy for monthly progress, while losing the crane view or the gate would break two workflows each.
02. Take an area-led plan you have written or inherited. Re-tabulate it by workflow rather than by zone. Mark each source with the workflows it serves. Highlight any source that serves zero workflows and any workflow that has zero sources.
Look for: A useful re-tabulation typically reveals two or three sources placed for visual completeness that serve no named workflow, and one workflow — often gate logistics or fitout 360 — that has no dedicated source. The exercise is the precondition to a defensible revision.
Checkpoint
Walk through your current capture plan source by source. Which sources serve at least one named workflow, and which serve none?
Recommended reading