Plain-language definitions for the PMO operating terms that become tables, screens, workflows, and reports in the BuilderVault PMO toolkit.
The controlled path for capturing new project, automation, reporting, enhancement, or process-improvement requests.
Build implication: Create one request record with status, sponsor, category, problem statement, benefit, and decision history.
The PMO review process that validates completeness, scores demand, and decides whether to approve, defer, reject, or request clarification.
Build implication: Use a queue with aging, owner, score, decision reason, and automatic notifications.
The lightweight agreement that defines scope, objectives, value, sponsor, assumptions, dependencies, and ownership before delivery begins.
Build implication: Link the charter to approved intake and require sponsor approval before a project record is opened.
A formal lifecycle checkpoint that verifies required evidence before a project moves to the next stage.
Build implication: Use gate criteria, evidence links, approver decisions, exception reasons, and stage history records.
The artifact, link, approval, plan, or test result used to prove a stage exit criterion has been met.
Build implication: Store evidence as rows or links tied to a gate review instead of free-text status notes.
A combined governance view of risks, actions, issues, and decisions that need ownership and follow-up.
Build implication: Require owner, due date, severity, status, escalation flag, and closure evidence for active items.
A controlled request to change scope, schedule, budget, risk, or expected benefits after baseline approval.
Build implication: Capture impact assessment, decision, approver, baseline update action, and communication history.
The record of decisions needed, options considered, final decision, decision maker, rationale, and date.
Build implication: Keep decisions linked to project, intake, gate, change, or status records so reporting has context.
The post-launch or periodic check that determines whether the approved work created the expected business value.
Build implication: Track benefit metric, baseline, target, current value, measurement date, and accountable owner.
A concise stakeholder update focused on portfolio health, exceptions, decisions needed, and upcoming governance events.
Build implication: Generate from current PMO records and avoid sending raw list exports.