Run Policy Attestation Sign-Offs

Track every license, certificate, permit, and calibration you are responsible for in one live register that flags a renewal before it lapses. These compliance prompts build the operational layer around the credentials your business runs on: what you hold, when it expires, who owns the renewal, and what gets blocked if it slips. Built for operators who would rather find an expiry in a dashboard than in an audit.
Run Policy Attestation Sign-Offs

Copy

Build me a policy attestation tracker. Keep one record per policy with its title, version number, effective date, owner, and the document. Define the audience for each policy by role or team rather than sending everything to everyone. Create one attestation record per person per policy version capturing the date signed and the version they signed. Show me a completion view that lists the outstanding names rather than just a percentage. Add an AI agent that chases outstanding attestations weekly, escalates to the manager after two weeks, and starts a fresh cycle automatically when I publish a new version.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Run Policy Attestation Sign-Offs

Track which policy version each person signed, who still owes an attestation, and re-run the cycle automatically when the policy changes.

// the spark catches · intelligence awakens · the answer unfolds

"Everyone was sent the policy" is not the same as everyone having read it, and only one of those survives a question. This prompt builds the sign-off tracker: which policy, which version, who it applies to, and who has actually attested.

What's Included

  • Policy versions so an attestation points at the text that was signed.
  • Audience rules: who each policy applies to, by role or team.
  • Completion view showing the outstanding names, not just a percentage.
  • An AI agent that chases the stragglers and summarizes the gap for a manager.

How To Use

  1. Load each policy with its version and effective date.
  2. Define who it applies to rather than sending it to everyone.
  3. Collect attestations and watch the outstanding list shrink.
  4. Re-run the cycle automatically when a policy version changes.

Pair it with the staff certification register so training and policy sit together, and with team collaboration prompts for the communication around a change.

Related from the blog