Point of view
Project controls meets AI.
Most AI mandates arrive as a tool to adopt rather than a decision to improve. Project controls exists to find deviations while there is still time to act, and that is where AI is worth having: wider measurement, evidence reconciled sooner, and a prepared position in front of leadership before the meeting.
So the work starts from project controls, not from the tool: assess the conditions AI needs, choose a use that serves a real reporting-period decision, and test it on one period of real work with a named owner and outputs checked against outcomes. Leadership gets faster, verifiable evidence for the decisions it already makes, with the baseline under control.
At a glance
- Readiness
- Four conditions that must hold together.
- Uses
- Four levels, from drafting to governed action.
- Engagement
- Four steps, tested over one reporting period.
Readiness
What must hold before AI can.
AI-assisted controls hold up during a reporting period only when all four conditions hold. Each has a current state, a target, and a first governed bridge; the practice assesses them from approved evidence.
Agent-ready knowledge
- Where teams start
- Procedures, variance thresholds, and decision rights are written for people, in documents AI cannot reliably read, check, or cite.
- Target
- The same procedures, variance thresholds, decision rights, and evidence definitions, versioned and prepared as approved content AI can read and cite.
- First bridge
- One procedure set prepared and approved as agent-readable content
- Accountable owner
- Each discipline lead
Governed access, reconciled evidence
- Where teams start
- Exports move by email and copy-paste; the six control disciplines update on different dates, and the dependencies between them stay implicit.
- Target
- Approved read-only interfaces, with least privilege, consent, and an audit trail, feeding one reconciled view: project, work, and cost breakdown structures, risk breakdown structure, data date, revision, and lineage.
- First bridge
- One approved read-only interface per system of record, granted by that system's owner, with quality rules and deterministic checks
- Accountable owner
- The project controls lead
Bounded specialist AI
- Where teams start
- General chat with prompts that have no owner and outputs that are not tested.
- Target
- Owned instructions, named sources, test cases, stated uncertainty, and sign-off.
- First bridge
- Accepted test cases and failure limits
- Accountable owner
- Each use owner
Governed reporting cadence
- Where teams start
- Updates and analysis happen when someone asks, and decisions arrive mid-discussion without a prepared position.
- Target
- Each reporting period follows the control rhythm against one data date. Reconciled updates and analysis support a decision pack; decisions are recorded, and actions are tracked to closure.
- First bridge
- A published reporting calendar with traceable human approvals
- Accountable owner
- The PMO lead
Readiness output
AI gathers and reconciles. Experts verify. Accountable leaders decide.
For each condition, the output records current evidence, the limiting constraint, the first governed bridge, its owner and date, and acceptance evidence. The assessment starts with the weakest condition.
Uses and engagement
Frame the use, then earn the automation.
The use levels and engagement steps answer different questions. One defines what AI may do and what it needs first; the other defines how a chosen use is introduced, tested, and owned.
Use levels
Where AI fits
Four levels, from bounded assistance to governed agents. A team selects the lowest-complexity level that serves the decision and meets what it needs first; it need not climb all four.
Drafting and explanation
Needs first
An approved tool and a policy that defines which project information it may access or process.Examples
- Variance narratives against the performance measurement baseline, drafted from approved numbers
- A risk-workshop brief drawn from the risk register and current schedule
Analysis assistance
Needs first
An approved performance measurement baseline and agreed definitions against which the analysis can be checked.Examples
- Schedule-quality checks before a baseline update: logic, constraints, float, and progress
- Reconciliation of actuals, commitments, and the estimate at completion, or review of a risk register for duplicates, missing owners, and unquantified risks
Reporting automation
Needs first
Owned data in systems of record, a published reporting calendar, deterministic checks, and a named maintainer.Examples
- A period performance report assembled from systems of record on the published reporting calendar
- Variance thresholds that route exceptions to named owners, with deterministic checks and a reviewable run record
Governed agents in project systems
Needs first
Decision rights, an approver for every change, reconciliation, an audit trail, and a way to stop the process.Examples
- Read-only preparation of updates from project or enterprise systems for a named approver to verify
- Any approved write reconciled to the system of record and submitted through the applicable change control
Grounded in practice
From inside a controls function.
Inside the controls function of a major program, the founder deployed enterprise project portfolio management software linked to enterprise systems and launched a reporting automation initiative that applied AI, aimed at reducing manual effort and improving data accuracy. The discipline that governs a performance measurement baseline is the discipline that makes automation safe to rely on.
Engagement steps
How the engagement runs
The work starts with the decision, the underlying baseline, and the controls that have to survive. AI enters once those are clear.
Shahyn Management Consultancy is not a software vendor, and AI is not a separate service here. The work is project controls, with AI applied where it holds up to scrutiny.
Frame the use
Start from one decision the team makes every reporting period. Name the work, its owner, and the acceptance evidence. Choose the tool last.
Set the guardrails
Define approvals, data location, permitted actions, maintenance ownership, review gates, and the controls that protect the performance measurement baseline.
Pilot on approved tools
Run one reporting period of real work on tools the organization already licenses and approves, with outputs and exceptions recorded for review.
Hand over an owned process
Leave the bounded use as a documented, repeatable process with a named owner, review gates, a reviewable run record, and a way to stop it.
Pilot decision
One reporting period before scale.
The first engagement closes by comparing the pilot with the current process across preparation effort, defects, latency, and action closure. Wider adoption is the executive sponsor's decision, taken on those measures; any write-back to a system of record is authorized by that system's owner.
Contact
One bounded use to start.
Share the mandate, the systems in play, and the decision AI should support. The first conversation names the use, what it needs first, and the control it must keep.