Skip to main content
ControlFrameby LockedIn Labs

Choose your role

For audit and advisory firms

Less reconstruction. More expert review.

Your expertise belongs in the review. Connect each requirement to its source evidence and reviewer decision, so the next person can understand what is recorded, what is missing, and what needs their judgment.

Follow the evidenceExplore independent review

Operating remit

Require
Make the expected proof explicit
Review
Keep source context beside the workpaper
Decide
Preserve the reviewer’s reason and next action

One connected record

Follow the question.
Keep the context.

A workpaper has arrived. Does it establish the identity-proofing result the requirement calls for?

Follow the record from expected proof to the reviewer’s next question.

Explore the CMS EDE framework

Illustrative CMS EDE record · synthetic example

Identity proofing

CMS EDE · Year 9RIDP TC01/TH10001 ACC

The expected proof

Establish the outcome of the same attempt.

Remote identity proofing (RIDP) case TC01 specifies an ACC outcome. The case definition tells the reviewer what to look for; it does not establish an observed result.

H139 · RIDP Test Harness DataInitialRequest-Q · row 3
Source baseline
Year 9 requirement catalog
Proof needed
Authorized outcome capture and matching proofing record or request/response

Requirement remains open · source proof needed

Your operating lane

Give the next reviewer a clear starting point.

A useful handoff connects the workpaper to the requirement and the question still to resolve. In a configured engagement, the client prepares the record and the authorized assessor retains independent judgment.

  1. 01

    Agree

    Define the evidence needed

    Set the requirement, scope, source, and review responsibility before the handoff. Keep the method version visible when the engagement uses one.

    Record carried forward: requirement, scope, and method reference

  2. 02

    Receive

    Keep the source with the workpaper

    Retain the submitted artifact and its source context. Make missing capture time, environment, or supporting proof visible instead of leaving the reviewer to infer them.

    Record carried forward: artifact version and source context

  3. 03

    Review

    Ask for the proof that is missing

    A named reviewer records a decision and its reason against the exact artifact. A revision request explains what the next submission must address.

    Record carried forward: reviewer decision and revision request

  4. 04

    Carry forward

    Preserve the decision trail

    Keep the requirement, artifact, and review history connected. Evidence acceptance and package release remain separate, authorized decisions.

    Record carried forward: decision history and release requirements

Agent contribution

Automate preparation, never accountability.

  • Use recorded project status to suggest a next step and identify work waiting on a person.
  • Ground recommendations in the available project records and make the source of the answer visible.
  • The example demonstrates intake, review, and traceability; full-content AI assessment and source collection are not demonstrated here.

Named human authority

Keep the consequential decisions attributable.

  • Agree scope, method, sampling, and the proof required for the engagement.
  • Accept, conditionally accept, or reject evidence through a named, reason-coded decision.
  • Own sufficiency judgments, findings, supervisory review, and the assessor opinion.
  • Authorize release through the permitted engagement role and required gates.

Platform guides for your role

Understand how each capability supports your work.

Explore the platform capabilities and operating boundaries relevant to your role. A configured walkthrough can connect this model to your sources, evidence requirements, and review responsibilities.

  1. 01 · Preparation

    Understand the agent’s role

    See how preparation and recommendations fit around human decisions and configured access.

    Explore agent preparation
  2. 02 · Review

    Keep the conclusion independent

    Connect the source, the reviewer’s question, and the recorded decision without transferring assessor authority.

  3. 03 · Delivery

    Understand release requirements

    See how evidence eligibility, review gates, and package contents shape a controlled release.

    Explore evidence delivery
  4. 04 · Verification

    Inspect portable proof

    Check covered hashes and the signature boundary using the public offline verifier.

    Check a proof package

Start with one evidence handoff.

Bring one journey and agree the evidence requirements together. A focused pilot can test the handoff from intake to reviewer decision, with success measured in review time and rework.

Request a role-based walkthrough
Connected evidence for audit and advisory firms | ControlFrame