The bottom line
Roughly 85% of the work in Review plans is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: With no child occupations seeded, the score is derived from the process name 'Review plans' and its city-government industry context. Evaluating plans and documents against municipal codes or regulations is fundamentally analytical knowledge work. Because the value step involves reading, analyzing, and verifying information rather than physical execution, it falls solidly into the digital band.
grounded in the economy graph · digital scalar 0.85 · digital
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Review plans sits inside a larger value-flow — 1 parent structure it composes into. The hierarchy is grounding, not the story: it tells you which aggregate exposure Review plans inherits.
Where Review plans sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
How the work flows
Trigger: An applicant submits architectural or engineering plans to the municipality for zoning, building, or development approval.
- Receive and log the submitted plan documents and application fees
- Route plan sets to concurrent reviewing departments such as building, zoning, and fire
- Review plans against municipal codes, safety standards, and zoning ordinances
- Consolidate department comments and identify required modifications
- Issue a plan approval or a formal request for revision
Outcome: The municipality approves the plans for permit issuance or returns a consolidated list of required code-compliance revisions to the applicant.