PMO · ONE N8N WORKFLOW · ACTUAL PMO INFO MAPPING
One workflow.
Every scope routed correctly.
The workflow starts from PMO INFO, resolves the exact initiative and scope row, routes to that scope's actual owner, captures the monthly update, validates it, moves through approval and governance, then publishes the official PMO outputs.
01 / MASTER N8N FLOW
Follow one scope from
entry to official reporting.
Choose any actual PMO scope. The flowchart updates to show the real pillar, initiative, scope owner, team, weight and lifecycle status before moving into the proposed approval layer.
02 / ALL INITIATIVES + ALL SCOPES
The entire PMO hierarchy
inside the same workflow.
All scope rows are loaded below. Expand initiatives individually, or reveal all scope nodes at once. Selecting a scope updates the master route above so the workflow never loses the exact owner-to-scope mapping.
WHY SCOPE-LEVEL ROUTING MATTERS
Some initiatives deliberately route different scopes to different owners.
03 / APPROVAL + GOVERNANCE
Approval sits inside
the same end-to-end flow.
The PMO workbook gives us owners and the existing Review Queue / Overrides logic. It does not currently define named approval roles, so the approval matrix below is intentionally marked proposed.
The submission keeps the same initiative + scope context. Owner corrects the record and resubmits; n8n preserves the audit trail.
Progress was 100% while status was “On Track”; the current workbook flags this for confirmation to Completed. That same rule can become an n8n validation / governance check.
THE MODEL TO BUILD
One reusable engine.
178 scope-specific routes.
The form stays standard. The routing changes dynamically because PMO INFO tells n8n which initiative, scope, owner, team, weight and lifecycle rule applies.