Provide portfolio ownership, strategy goals, scoring weights, gate criteria and quorum, approval delegation, approved budgets, currencies, initiative identifiers and authorized delivery/finance mappings.
Implementation
Configure strategy, approval policy and connected evidence before rollout.
Implementation phases
- Agree governancePortfolio Manager
- Prepare source dataTeam and ERP.ai
- Verify decisionsTeam and ERP.ai
- Invite the teamPortfolio Manager
Phase 1 · Portfolio Manager
Agree governance
The Portfolio Manager confirms portfolio ownership, goals, scorecards, gate criteria and distinct funding approvers.
Phase 2 · Team and ERP.ai
Prepare source data
Reconcile the proposal backlog, initiatives, budgets and KPI history with retained identifiers.
Phase 3 · Team and ERP.ai
Verify decisions
Run independent proposal, gate and funding cases, including conflicts, duplicate commands and unavailable headroom.
Phase 4 · Portfolio Manager
Invite the team
The Portfolio Manager reviews executive and operational views with scoped accounts, then enables the approved connections.
Version scoring and gate policy between review cycles. Material changes invalidate affected decisions. Preserve previous review evidence and budget history; corrections use linked records and independent approval. Repeat affected permission, concurrency and reporting cases before rollout.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.