What Did the Approver Actually See?

  1. WHAT AN APPROVAL RECORD HOLDS A name A timestamp What they saw Who approved it, and what did they see? The second half is new. Taskeen taskeen.leapora.tech 1 / 4 (c) Leapora AI, Inc. All rights reserved. Siva Kowsika.
  2. WHAT THE CLICK RECORDED, AND DID NOT What the record can tell you IT HOLDS who clicked the minute the item IT DOES NOT which version what was shown whether it was read Taskeen taskeen.leapora.tech 2 / 4 (c) Leapora AI, Inc. All rights reserved. Siva Kowsika.
  3. DRAFTING AND AGREEING, ONE RECORD A model drafts the rationale. A person agrees with it. Two different acts. One record. It cannot tell them apart. Taskeen taskeen.leapora.tech 3 / 4 (c) Leapora AI, Inc. All rights reserved. Siva Kowsika.
  4. WHAT THE RECORD HAS TO HOLD The approval and what it rested on, recorded together: the version shown, and a named person on a date. Otherwise it is a signature on a blank page. Taskeen taskeen.leapora.tech 4 / 4 (c) Leapora AI, Inc. All rights reserved. Siva Kowsika.

An auditor asks one question. Who approved this deviation, and when.

That question grew a second half in the last two years, and almost nobody has a system for it. What did the approver actually see at the moment they said yes.

The substitution that held for a century

Leaving the basis of an approval unrecorded was, until recently, a perfectly reasonable thing to do.

A quality lead approving a deviation had read the deviation. Reading it was the only way to know what it said. There was no path from ignorance to a signature that did not pass through the document, so the name and the timestamp stood in for the judgement, and the substitution held.

Every approval workflow in every regulated industry is built on that substitution. It is why an approval record looks the way it does: an actor, an object, a moment. Three fields, and the fourth one was implied by physics.

The month it stopped holding

It stopped holding the month a model started drafting the rationale.

An approval can now mean a person read two paragraphs of generated summary and agreed with them. That may be entirely sound. A good summary of a sound analysis, read by someone competent, is a reasonable basis for a decision.

It is a different act from the one the record claims. And the record cannot tell the two apart, because it was never designed to: it has a field for who and a field for when, and the thing that used to make those two fields sufficient has quietly been removed.

Nobody removed it deliberately. No approval policy was changed. The drafting tool was adopted by a team that found it useful, and the meaning of every approval record downstream of that team changed on the same day, without a single line of the approval process being edited.

Audit week, and the finding that moved

The old audit finding was that three systems give three answers. They still do, and that is still worth fixing.

The new one is harder. The system everybody agrees on records a name against a decision whose basis was never captured and now cannot be reconstructed. Everyone involved acted properly. The record is internally consistent. It simply does not contain the thing the auditor came for.

An approval that does not carry what was in front of the approver is a signature on a blank page. The organisation was getting away with it for as long as a human had to read the thing in order to approve it.

The follow-up question nobody can answer

An auditor who finds a clean approval will usually ask one more thing, and it is the question that decides how the rest of the week goes. Show me what they were looking at.

In a paper process the answer was trivial, because the approval was physically attached to the document. In a workflow system the answer is usually a link to the current version of the object, which is a different thing from the version that existed on the day. If the deviation was amended twice after approval, the link resolves to a document the approver never saw, and nothing in the record says so.

Teams discover this during the audit rather than before it, because the link works perfectly every other day of the year. It only misleads on the one day somebody asks it to prove something about the past.

What has to be recorded now

Three things together, as one record, or the gap stays open.

The version. Not the document, the version of it. A deviation approved on Tuesday and amended on Wednesday is two different objects, and an approval that points at a title rather than a revision points at whichever one is current when somebody asks.

What was shown. Whether the approver saw the full analysis, a generated summary of it, or a summary of a summary. This is the field that did not need to exist before and does now, and it is the one most approval systems still have nowhere to put.

A named person, on a date, confirming. Not a role, not a service account, not a queue. A person, because an auditor asking who approved this is asking about a human being who can be asked what they were thinking.

That layer is what Task Accountability Infrastructure records. It does not make the approval a better one. A person who skims will still skim. What it does is make the approval checkable years later by somebody with no reason to trust you, which is the only test an approval record ever has to pass.

Questions

What should an approval record contain?

The approver, the moment, the exact version of what was approved, and what the approver was shown of it. The first two have always been recorded. The second two used to be implied, because reading the document was the only route to approving it, and that is no longer true.

Is a name and a timestamp enough for an audit?

It was, for as long as approving something required reading it. Where a model drafts the rationale, a name and a timestamp cannot distinguish between someone who read the full analysis and someone who read a generated summary of it. Both produce an identical record.

How does AI-drafted content change approval records?

It breaks the assumption the record rests on. The approval workflow is unchanged, the fields are unchanged, and the meaning of the entry changes the day a team starts drafting with a model. Nothing in the audit trail marks the moment that happened.

What is approval basis?

The evidence actually in front of a person when they approved something: which version, and what of it they were shown. It is distinct from the approval itself, and it is the half that most systems do not capture.

Taskeen records who was told, who acknowledged, what they did, and what proves it. See how it works.