Hiring guide
Management report delivery: reconcile sent, received and acknowledged
By CFO Index · Published
The correct report was approved and a message was sent, but one decision maker never received it and another cannot open the link. A version register cannot by itself prove that the intended audience received a usable report. Add a small delivery reconciliation for decision-critical releases. It should expose failed hand-offs without claiming that an email open proves understanding or approval.
Freeze the approved recipient roster
For each release record the report ID, exact version, purpose, approved audience, dispatch owner and decision deadline with timezone. Resolve distribution-list membership at the time of sending instead of treating the group name as evidence of its members. Confirm each person's role and permitted content with the report owner. Keep a restricted report away from recipients who are merely convenient to contact. This worksheet follows the delivery outcome; the existing version and access controls still determine what may be sent and to whom.
Use separate evidence states
A message in Sent is dispatch evidence, not receipt evidence. Microsoft's Outlook guidance says a delivery receipt concerns the recipient's mailbox, while a read receipt indicates opening; recipients or email software may prevent read receipts. Neither proves that the linked report opened successfully or that its recommendations were accepted. Record only the evidence available and use unknown rather than converting missing acknowledgements into either refusal or successful review.
| State | Evidence | What it does not establish |
|---|---|---|
| Approved recipient | Current release roster | Message actually dispatched |
| Sent | Message reference and timestamp | Mailbox delivery or report access |
| Delivered or failed | Supported receipt or failure notice | That a person read the report |
| Access confirmed | Recipient confirms correct version opens | Agreement with analysis |
| Acknowledged | Dated response tied to release ID | Approval unless explicitly stated |
| Decision recorded | Authorised decision and conditions | That every recipient reviewed it |
Work one missed-recipient example
Hypothetical example: six approved recipients need release R3 before a Tuesday decision. Six dispatch records exist. One address bounces, one recipient says the link is blocked and the other four explicitly confirm access to R3. The reconciliation is four access-confirmed, one failed delivery and one unresolved access issue, not six completed hand-offs. After an approved address correction, the bounced recipient confirms access: five confirmed and one still blocked. The arithmetic counts recipient outcomes, not email opens or management approvals.
Repair the specific failed hand-off
Assign an owner and next action to each exception. Correct an address only after checking the intended recipient, and have the responsible system owner resolve access through normal controls. Do not send the whole confidential workbook to a personal address or broaden a link to anyone merely to clear a blocked status. Microsoft describes recipient-specific sharing links as limited to the invited audience; actual product and organisation settings still require verification. If the deadline arrives first, tell the meeting owner which participant lacks the report and let that owner decide how to proceed.
Treat a replacement report as a new delivery event
If R4 supersedes R3, link the replacement and explain which decision-relevant information changed. Reconcile R4 against the authorised audience again; an acknowledgement of R3 is not evidence that R4 arrived. Include anyone who received the affected version through an approved route and record any known uncontrolled copy as an exception for the responsible owner. A successful permission removal or message recall should not be assumed to erase a downloaded attachment. Do not silently overwrite the delivery history.
Close on usable evidence, not a perfect receipt rate
Define which reports actually require explicit access confirmation or acknowledgement. A routine low-risk update may not justify chasing every recipient, while a decision-critical pack may. Record the policy, overdue exceptions and accepted limitations, and retain only necessary communication evidence under company rules. Test the workflow with a failed address, a blocked link and a superseded release using synthetic or approved non-sensitive material. The goal is an accountable hand-off before the decision, not covert tracking or an unsupported claim that all recipients understood the report.