SOP read receipts and compliance reports

An SOP read receipt is a dated acknowledgement that a named person confirmed a named procedure — not a vibe that “everyone saw the PDF.” Compliance reports then show who is outstanding. Proof of required reading is an HR operations object with an owner (usually HR or the process owner), an artefact (the receipt plus the report), and a done definition (this person, this SOP version, this date). Product surface is Dayzen SOP management: My SOPs read receipts and compliance reports, plus authoring, categories, assignment rules, and revision control. Procedure structure stays on the SOP template. New-joiner assignment of a welcome SOP is a special case of the join path on Dayzen onboarding (welcome SOP on activation). This page is operational proof of reading. It does not satisfy POSH or other statutory training by itself, is not legal advice, and does not reprint how to write or version a procedure.

Why “we circulated it” is not a receipt

Emailing a file, pinning a handbook chapter, or mentioning a process in stand-up creates a story, not an acknowledgement. Six months later you cannot answer who confirmed which version. Audits, customer questionnaires, and internal reviews ask for a list, not a recollection. The cost of a missing list is rework: you re-send, you guess, you argue whether a Slack emoji counted.

A receipt is a row you can defend: person, SOP (and version if you version), date and time of acknowledgement, and whether they are still outstanding. That is operations. It is not a government filing and not a training certificate for a facilitated session.

What a read receipt is

In this usage, the employee (or other assigned reader) opens the current procedure in My SOPs and confirms they have read it. The system stores a dated acknowledgement against that person and that SOP. The owner of chasing outstanding receipts is whoever you named — often HR operations for company-wide procedures, a function lead for a local job. The done definition is acknowledged against the assigned version, not “they work here so they must know.”

Dayzen SOP management includes My SOPs read receipts. Readers acknowledge in the product; you do not need a paper sign-off sheet as the system of record for these procedures. A paper sheet can still exist for a site that wants one; do not run two ledgers and then pick the friendlier one after an incident.

A receipt is not attendance at induction. A receipt is not a quiz score unless you separately run a quiz. A receipt is not proof that the person performed the job well. It is proof they confirmed the text you assigned.

What a compliance report is

A compliance report answers who was assigned, who has acknowledged, and who is outstanding — for a procedure, a category, or a population you care about. The artefact is the report (export or screen), with a date you ran it. The owner is the same chase owner as the receipts, or an auditor who only reads. The done definition is that you can name the gaps and the next action, not that the report is green because you filtered out the leavers by hand in a spreadsheet and lost the filter.

Dayzen SOP management includes compliance reports on top of receipts. Use them as the operational list. Do not rebuild the list from mailbox search. When a person has left, the report should reflect assignment rules and employment status you actually maintain — not a forever-red row you ignore until someone asks.

Reports do not create legal compliance by existing. They create an operational picture. What you must keep, for how long, and for which topics may depend on applicable law, contract, policy, or company practice. Verify with your HR, legal, or SME team. This article does not invent retention years.

What receipts are not (especially training)

Do not treat an SOP read receipt as POSH training, a statutory briefing, an IC procedure, or a completion certificate for a classroom or LMS module. Reading a procedure can be part of how you communicate a topic. It is not, by itself, those other objects. If your policy says a facilitated session is required, log that session elsewhere; do not point an inspector at My SOPs and call it the session.

The same warning applies to other statutory or customer-mandated training you may run: site safety, data handling, customer codes. An acknowledgement that someone opened an SOP is operational proof of reading that SOP. Stretching it into “we trained everyone as required” is how you fail the next question after “show the attendance list.”

This page is operational guidance, not legal advice. Pending questions about what a particular law expects should go to your reviewer, not into a receipt configuration.

Assignment, then receipt — not the reverse

A receipt only makes sense against an assignment. If nobody was assigned, a blank report is not “100% compliant”; it is an empty audience. Assignment and distribution rules, categories, and role-based audiences are SOP management work; the strategy article for audiences is the sibling on role-based assignment. Welcome SOP on activation is the joiner special case: Dayzen onboarding can assign welcome SOP material when the employee is activated, and then My SOPs is where they acknowledge.

Do not assign every procedure to every employee to make the report look busy. Flooded inboxes produce click-through acknowledgements that mean less. Assign the job’s procedures to the people who do the job, then chase receipts for that set.

When a procedure is revised, whether readers must re-acknowledge is a decision you make with versioning — owned by the versioning sibling. This page only needs you to know that a receipt is tied to what they confirmed. Mixing “they signed last year” with “we changed the steps last week” without a re-read rule is how old acknowledgements pretend to cover new text.

A comparison you can paste into a RACI

	Read receipt	Compliance report	Statutory / facilitated training
Object	Dated acknowledgement of a named SOP	List of assigned vs outstanding	Session or module with its own attendance
Typical owner	Assigned reader completes; HR chases	HR or process owner	L&D, IC, or named trainer — not this page
Artefact	My SOPs acknowledgement row	Report as of a run date	Attendance, agenda, certificate if you issue one
Done when	This person confirmed this version	Gaps named and chased	Your training rule’s done definition — separate
Dayzen role	My SOPs receipts (verified)	Compliance reports (verified)	Not an LMS; do not equate receipts with POSH training

Day-to-day chase

Run the report on a cadence you can keep — weekly in a rollout, monthly in steady state, or before a customer audit you actually have. Name who pings outstanding readers. Name what happens after a second miss: manager copy, access restriction if your written policy says so, or only a reminder. Do not invent a nationwide penalty. If you block work systems for unread SOPs, that is a company choice you write down; Dayzen receipts record reading, they do not by themselves lock doors.

Joiners should see assigned procedures in My SOPs after activation and welcome assignment, not after a scavenger hunt through a shared drive. Leavers should drop off the chase list when their assignment should end. Transfers should pick up the new role’s procedures and stop being chased for the old shop’s packing SOP if they no longer pack.

Keep the SOP text in the system of record. A receipt against a file that only exists in someone’s inbox is a receipt against a ghost.

What this page will not become

It will not become the SOP template. You still need purpose, scope, owner, and steps in the procedure; receipts do not replace structure.

It will not become a writing-craft guide or a versioning guide. Craft and effective dates have siblings. Receipts consume versions; they do not design them.

It will not become the hire-to-activate pipeline. Onboarding is linked because welcome SOP assignment on activation feeds My SOPs. Pipeline stages stay on the onboarding owners.

It will not claim AI generation, AI search, helpdesk ticketing, or that a green report is POSH, DPDP, or any other statutory completion by itself.

Language to use in status updates

Prefer sentences like these:

• “Receipts: attendance regularisation SOP v2 — 40 assigned, 36 acknowledged, 4 outstanding (named).”
• “Report run 12 June; leavers excluded by current assignment, not by deleting rows.”
• “POSH session is a separate attendance list; My SOPs is not that list.”

Named person, named procedure, dated confirmation, then a report of gaps. If you only have a forwarded PDF, you have circulation, not a receipt.

Keep Dayzen SOP management as the place receipts and compliance reports live. Keep the SOP template as the procedure skeleton. Keep onboarding as the path that can assign a welcome SOP at activation so joiners have something to acknowledge. Keep statutory training on its own artefacts. This page only makes required reading provable as operations — and refuses to dress that proof up as a training certificate.