How we review an AI decision
See what your team sends, what we check and what you decide.
Three views of the decision
As planned is what your contracts, policies and diagrams say.
As built is what your systems and vendors actually do.
As is is what has changed since, because it keeps changing.
The document review records the evidence available for each view. System behavior needs separate authorized testing.
We read documents under a nondisclosure agreement. We do not connect to your systems.
Three review steps.
You send
List the uses and send the records we agree to review.
We prepare
We inspect those sources, explain evidence gaps and prepare assigned actions.
You decide
Your team decides what the records support. You record the decision and any conditions.
Five distinct record states.
- Answer received: Someone listed a use or answered a question.
- Reference received: An answer points to a record.
- Record checked: a reviewer inspected that version within the agreed scope.
- Evidence supports a finding: a reviewer recorded why the evidence answers a stated question.
- Decision recorded: the authorized reviewer recorded the outcome, conditions and review trigger.
An ID, a check mark or a named owner does not show that review took place. Track ownership and review separately.
Retain the record when a source changes.
Keep each version, open question, failed case, decision and condition. When you send an update, flag the questions it may reopen. Keep the prior record.
A file fingerprint can show that two copies match. It cannot prove who made them, who approved them or what their contents establish.
Inspect the retained baseline and reopened questionReview boundary.
A review prepares a file. It does not certify compliance, give a legal opinion or connect to a core.
See how we handle your records