Thoropass audit readiness error policy version approved but evidence still points to draft

TL;DR

Fix this in Thoropass by acting on the exact problem first: publish the approved policy version in Thoropass, repoint the evidence link from the draft version identifier to the published version, and open the auditor view to confirm the approved text is what an auditor would see. Do not rerun the whole job or collection unchanged, because the same inputs produce the same failure. Prove the fix on one control, account or batch first, then rerun the full scope and reconcile the counts.

policy version approved but evidence still points to draft

Use this when

• The operation in Thoropass fails with this exact message or symptom: policy version approved but evidence still points to draft.
• The same failure repeats on retry with unchanged inputs.
• An audit, evidence package or compliance review is blocked until this item completes.

Not for this skill when

• The message is an outage notice from the platform. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an auditor judgment or a control design choice. That is a review discussion, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Thoropass, and copy the full message plus the control, account or item involved into the run notes. Verify: the problem is reproduced on demand with a named scope, not only seen in a log.
2. Apply the specific fix for this problem: publish the approved policy version in Thoropass, repoint the evidence link from the draft version identifier to the published version, and open the auditor view to confirm the approved text is what an auditor would see. Verify: the smallest failing scope now completes, or the named control, account or item behaves as the fix predicts.
3. Check the neighbouring controls, accounts or items that share the same connection, mapping or owner, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in Thoropass on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
5. Compare the result counts or status against the source in Thoropass so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Why it happens

Approval and publishing are separate states, so evidence linked at draft time keeps pointing at the draft until someone publishes and relinks it after approval.

Variant phrasings

policy version approved but evidence still points to draft

The verbatim form searchers paste from the console, ticket or audit request. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - Thoropass audit readiness error policy version approved but evidence still points to draft

The how to phrasing for the same failure in Thoropass. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Thoropass troubleshooting for this failure

The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Edge cases

• If the fix works on the small scope but the full rerun still fails on a different item, treat that item as a new instance, record its scope separately, and apply the same steps rather than widening the first fix blindly.
• If evidence was already sent to an auditor in the wrong state, correct the record with a dated note explaining what changed, rather than silently replacing files in the package.
• If two settings or mappings could both produce this symptom, change one at a time and retest the small scope after each change, so the working fix is known rather than guessed.

Compatibility: Thoropass at current versions, plus the admin console or API the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_aNn4R40qzrZa52DUvudMfw