PMO implementation package

Change, risk, and issue control implementation package

A connected control layer for change requests, risk and issue management, decision logs, and escalation communications.

Tables

Screens

Power Fx snippets

Flow recipes

Downloadable guideChange, risk, and issue build guideDownloadable implementation guide for RAID, change approvals, escalations, and decision control.

Build checklist

Define change, risk, and issue fields.
Build separate but linked portals for each control area.
Automate reminders and escalations.
Create Power BI views for executives and delivery teams.
Review open controls in weekly governance meetings.

Workflow map

Team submits change, risk, issue, or decision

Classify severity and impact

Assign owner and due date

Route approval or escalation if needed

Track mitigation or decision action

Confirm closure evidence

Report open exposure and aging

Data model package

EitherChange Requests

Controls scope, budget, schedule, and risk changes after charter approval.

Column	Type	Required	Notes
Project	Lookup	Yes	Project affected by the change.
Change Type	Choice	Yes	Scope, schedule, budget, resource, quality, compliance.
Reason	Multiple lines text	Yes	Why the change is needed.
Scope Impact	Choice	Yes	None, Low, Medium, High.
Schedule Impact Days	Number	No	Positive or negative variance.
Budget Impact	Currency	No	Estimated cost increase or decrease.
Status	Choice	Yes	Draft, Submitted, Under Review, Approved, Rejected, Closed.

Relationships

Many Change Requests relate to one Project.
Change approvals create Approval History records.

Indexes

Project
Status
Change Type
Approver
Decision Date

EitherRisks and Issues

Operational RAID control for project uncertainty and active blockers.

Column	Type	Required	Notes
Item Type	Choice	Yes	Risk or Issue.
Project	Lookup	Yes	Parent project.
Severity	Choice	Yes	Low, Medium, High, Critical.
Probability	Number	No	Use only for risks.
Impact Score	Number	Yes	1-5 scoring for heat maps.
Owner	Person	Yes	Accountable for mitigation or resolution.
Due Date	Date	Yes	Drives reminders and overdue reporting.
Status	Choice	Yes	Open, Monitoring, Escalated, Closed.

Relationships

Many Risks and Issues relate to one Project.
Actions and Decisions can link to a RAID item.

Indexes

Project
Item Type
Severity
Owner
Due Date
Status

Power Apps screen package

Project manager and PMO analystRAID Register Screen

Manage risks, issues, actions, and decisions from one operating queue.

Layout

Filter tabs for Risk, Issue, Action, Decision
Severity and overdue filters
Register gallery
Selected item edit panel

Controls

tabRaidType
galRaidItems
cmbSeverity
tglEscalatedOnly
frmRaidItem
btnEscalate
btnCloseItem

Formula notes

Heat score = Probability * Impact Score
Close requires closure notes
Escalate creates decision request when decision is needed

Data sources

Risks and Issues
Actions
Decisions
Escalations

Project manager or sponsorChange Request Screen

Capture impact and route change approval before baseline changes.

Layout

Change summary
Impact assessment cards
Recommendation
Approver routing
Decision history

Controls

frmChangeRequest
cmbChangeType
numScheduleImpact
curBudgetImpact
cmbScopeImpact
txtRecommendation
btnSubmitChange

Formula notes

Impact level derives from budget, schedule, scope, and risk impacts
Approval route changes by impact threshold
Approved change prompts baseline update task

Data sources

Change Requests
Projects
Approval History
Actions

Risk, issue, and action ownersOwner Work Queue Screen

Let owners update mitigation, due dates, and closure evidence without seeing the full PMO admin app.

Layout

My open items
Due soon and overdue grouping
Update panel
Closure evidence panel

Controls

galMyActions
frmOwnerUpdate
txtMitigationUpdate
dpNewDueDate
attClosureEvidence
btnSubmitUpdate

Formula notes

Items filter by current user email
Due date extension requires reason
Closure sets Closed Date and notifies PM

Data sources

Risks and Issues
Actions
Communication Log

Power Fx package

lblHeatScore.TextCalculate RAID heat score

Formula / code

With(
    {
        heatScore: Coalesce(Value(cmbProbability.Selected.Value), 1) * Coalesce(Value(cmbImpact.Selected.Value), 1)
    },
    Text(heatScore, "0")
)

Notes

Use probability only for risks; issues can default probability to 1.
Use the score to drive escalation and Power BI heat maps.

btnCloseItem.OnSelectClose RAID item with evidence

Formula / code

If(
    IsBlank(Trim(txtClosureNotes.Text)),
    Notify("Add closure notes before closing this item.", NotificationType.Warning),
    IfError(
        Patch(
            'Risks and Issues',
            varSelectedRaidItem,
            {
                Status: { Value: "Closed" },
                'Closed Date': Today(),
                'Closure Notes': txtClosureNotes.Text
            }
        ),
        Notify("Item could not be closed.", NotificationType.Error),
        Notify("Item closed.", NotificationType.Success)
    )
);

Notes

Closure evidence is what makes RAID history useful later.
Notify the project manager when an owner closes an escalated item.

Power Automate package

FlowControl - Escalate Critical Risk

Trigger: When a risk or issue is created or severity changes.

Check severity and heat score.

If critical or escalated, post Teams alert to sponsor and PMO lead.

Create escalation record.

Create owner action with due date.

Write communication log.

Expressions

@or(equals(triggerOutputs()?['body/Severity/Value'], 'Critical'), greaterOrEquals(triggerOutputs()?['body/HeatScore'], 12))
addDays(utcNow(), 3)

FlowControl - Route Change Approval

Trigger: When Change Request status changes to Submitted.

Calculate impact level from schedule, budget, scope, and risk.

Route low impact to PMO lead and high impact to sponsor/change board.

Update decision fields.

Create baseline update action after approval.

Expressions

@equals(triggerOutputs()?['body/Status/Value'], 'Submitted')
if(greater(triggerOutputs()?['body/BudgetImpact'], 25000), 'Sponsor', 'PMO Lead')

Dataverse solution package

Create solution BV PMO Controls with publisher prefix bvpmocntl.

Tables

bv_changerequest
bv_raiditem
bv_action
bv_decision
bv_escalation
bv_impactassessment

Choices

bv_changetype
bv_controlstatus
bv_severity
bv_raidtype
bv_decisionstatus

Apps

RAID Register
Change Request Portal
Owner Work Queue

Cloud flows

Control - Route Change Approval
Control - Escalate Critical Risk
Control - Overdue Owner Reminder
Control - Close Item Notification

Security roles

Control Project Manager
Control Item Owner
Change Approver
Executive Escalation Viewer

Environment variables

Critical Risk Channel URL
Change Board Email
Overdue Reminder Days
Baseline Update Owner

Dashboards

Risk Heat Map
Issue Aging
Change Impact
Open Decisions

Deployment checklist

Create development, test, and production environments or sites before build-out.
Create publisher prefix, solution shell, environment variables, and connection references first.
Build tables and choices before apps and flows.
Import sample template rows, then test with non-admin users.
Run approval, rejection, revision, escalation, and overdue scenarios before release.
Publish Power BI pages after validating relationships, date fields, status definitions, and security trimming.
Document owners, support mailbox, release notes, and rollback steps.

Starter files

Intake requests CSVStarter columns for demand intake, scoring, ownership, and triage decisions.Project charters CSVStarter charter fields for scope, sponsors, success measures, approvals, and assumptions.Stage gates CSVStarter criteria and review fields for stage movement and gate decisions.RAID and change control CSVStarter fields for risks, issues, actions, decisions, and change requests.Status reporting CSVStarter fields for weekly project health, milestones, benefits, and decision requests.PMO build roadmapA plain-language build order for rolling out the PMO system one tool at a time.