DataStackMRANTI DATA TEAM Explore mapping ↓

PMO · MASTER-DATA-DRIVEN N8N DESIGN

Map every scope.
Route every owner correctly.

The PMO master is not simply Initiative → Owner. It is Initiative → Scope ID → Scope Owner → Team → Weight → Status. The proposed n8n workflow must respect that row-level mapping before any submission or approval routing happens.

Explore all scope mappings See the proposed flow
38Initiatives
178Scope records
26Unique mapped owners
3Multi-owner initiatives

01 / CORRECT OPERATING LOGIC

The scope row drives
the routing decision.

n8n should never assume one owner per initiative. It first resolves the initiative, then the exact scope ID, then reads the owner and team attached to that scope record.

01

User identity

MRANTI staff member enters the PMO reporting flow.

Email / SSO
→
02

Initiative lookup

Load only initiatives relevant to the user or reporting role.

e.g. TPE/01
→
03

Exact scope lookup

Resolve the selected scope row — this is where owner, team, weight and lifecycle status are stored.

e.g. TPE/01/02
→
04

Scope owner route

Submission is attributed to the owner mapped on that exact PMO INFO row.

Owner varies by scope

IMPORTANT MASTER-DATA BEHAVIOUR

Three initiatives currently contain more than one mapped owner across their scopes.

↓
05

Monthly scope update

Status, progress, remarks, supporting evidence, risks and finance values are captured for the selected scope.

→
06

n8n validation

Check active/changed/removed status, scope ownership, milestone weight, reporting month and mandatory evidence.

→
07 · PROPOSED

Approval matrix

Approver is looked up separately by pillar / initiative / scope. The workbook currently defines owners, not named approvers.

→
08

Official outputs

Approved records update PMO Tracker, review queue, dashboards and management exception reporting.

02 / ACTUAL PMO INFO MASTER

Every initiative.
Every scope. Every owner.

This browser is generated from all scope rows in the attached PMO INFO tab. Owner is shown at the scope-row level rather than being flattened to one initiative owner.

VISIBLE INITIATIVES38
VISIBLE SCOPES178
VISIBLE OWNERS26
STATUS MIX153 active

03 / N8N ROUTING PREVIEW

Click any scope above.
See exactly who it routes to.

The selection below demonstrates the lookup chain n8n should execute from the PMO master. Approval remains a proposed separate matrix.

04 / MASTER DATA GOVERNANCE

Lifecycle changes remain
visible and auditable.

The PMO INFO tab already records Active, Completed, Changed and Removed rows. n8n should use these flags when deciding what may be submitted for a reporting month.

153Active scope rows
7Completed scope rows
4Changed scope rows
14Removed scope rows
ACTIVE

Available for reporting

Normal scope routing can proceed subject to reporting-period rules.

COMPLETED

Closed milestone history

Keep history visible but prevent unnecessary new reporting after the effective completion month.

CHANGED

Respect remapped code / name

Use the effective month plus changed scope code or changed scope name when resolving the canonical master record.

REMOVED

Do not offer after removal

Keep prior submissions for audit, but remove the scope from future form choices from the effective month onward.

THE DESIGN PRINCIPLE

One form does not mean
one owner per initiative.

PMO INFO MASTER Initiative Code ↓ Scope ID ↓ Scope Owner + Team + Weight + Status ↓ Monthly Submission ↓ Validation → Approval → PMO Outputs