AMAlbert Mathew

Project controls case study

AI-Enabled Project Controls

An evolving control loop for deciding when AI-assisted work is ready to use.

I use it to establish what is trusted, what has been checked, and whether to approve the result.

See examplesExplore the workflow

01 / Problem

A finished result still needs a decision before use.

AI can accelerate analysis and drafting, but speed does not establish that an output is ready for its intended purpose. When the trusted source, document status, or approval condition is unclear, a polished result can carry forward hidden errors, missing context, or unsupported claims.

I treat that ambiguity as a project-control problem: I establish what is trusted, what has been checked, and whether an output is ready for its intended use.

The goal isn't to establish controls for their own sake.

It's to make clearer decisions before work is reused.

02 / Operating model

Human judgment stays with the owner.

I retain the final decision about whether AI-assisted work is ready to use.

Owner

Frames the work and reviews the result.

  • Defines the purpose and decision.
  • Sets the trusted source and scope.
  • Evaluates the work and its limitations.
  • Decides whether to approve, revise, defer, or hold.

AI

Provides analysis and draft work for review.

  • Analyzes material within the agreed source and scope.
  • Drafts outputs for review.
  • Flags inconsistencies and limitations.
  • Does not decide whether work is ready to use.

04 / Practical use

The controls set the stage for the next decision.

The approach uses a small set of practical controls. Each one answers a question that otherwise might remain implicit.

01

Trusted source

Which information is reliable for this task?

02

Clear status

Is this a draft, an approved working version, a historical reference, or ready for use?

03

Defined AI work

What analysis, drafting, or checking is the AI authorized to perform?

04

Validation gate

Which checks need to pass before the work is reused, presented, or treated as current?

05

Owner decision

Should the work be approved, revised, deferred, or held?

06

Reusable record

What decision context and limitations should remain available for later work?

05 / Examples

Applying controls changes the work.

Two examples show the controls at work: one recovers missing evidence; the other determines whether a revision is ready to use.

Follow the evidence trail.

  1. 01

    Test the claim.

    A question about a specific role reveals that a draft career guide lacks enough supporting detail.

  2. 02

    Find the support.

    Review the source material and later clarifications that may supply it.

  3. 03

    Reconnect the detail to its source.

    Strengthen the draft without treating interpretation as evidence.

  4. 04

    Recover the original intent.

    Restore the distinction between detailed evidence, qualified records, and reusable guidance.

    See the Knowledge System

Finished ready.

  1. 01

    Confirm the change.

    Check the current source and required approval before revising.

  2. 02

    Align the versions.

    Make the owner-approved text change and synchronize the working text with the presentation version.

  3. 03

    Inspect and verify.

    Review the visual snapshots and verify the current status before use.

  4. 04

    Make the decision.

    Promote if the checks and versions align; otherwise, revise or hold. 

06 / Evidence and limits

Evidence and limits belong together.

The evidence supports an internal set of operational controls.

Demonstrated in this work

  • Source, status, validation, review, and approval controls.
  • An owner-approved resume change-control lifecycle.
  • Explicit separation between owner and AI responsibilities 

Not established

  • A fixed operating cadence or universal use of every control.
  • External adoption or regulatory compliance.
  • External validation of the system or its outcomes.