Audit-Ready Attestation with Separations, Leave, and New Hires
Crestline University must submit an annual rules-education attestation covering 342 staff members. The live platform dashboard shows 314 complete, 28 outstanding, and 346 assigned learners. The 28 include 7 who separated before the assignment date, 5 on approved leave, 3 hired after the deadline, 9 active staff with no completion, and 4 whose records show a completion at a prior institution. The compliance director wants the dashboard brought to 100% before signing and asks an administrator to mark the 28 complete. HR's roster is the authoritative list of active employees. Institutional policy requires five years of retention for completion records and a documented exception process. The platform report can be filtered by assignment date, completion date, role, and sport, but it cannot show leave status. The board meeting is in three days.
1. How would you build an audit-ready report from these numbers, and why is the dashboard not the population?
Read the worked answer
Do not treat the dashboard as the population. Reconcile the 346 platform assignments to HR's 342-person roster by employee ID. The four-person gap is probably duplicate accounts or assignments to separated staff; resolve those before calculating a rate. Define the required population as of the assignment date, with clear categories: active and required, separated before assignment, approved leave, new hire after deadline, and completion at a prior institution. A prior-institution completion is not automatically equivalent; route those four to the compliance director for an equivalency decision and document the basis. Report both a raw platform rate and a reconciled compliance rate. The reconciled report should show name, role, sport or unit, hire date, separation or leave date, assignment date, completion date, module version, and exception code. That is what an auditor can follow; a 100% dashboard with unexplained rows is not.
2. How should the 28 outstanding records be handled? Address the director's request to mark them complete.
Read the worked answer
Handle the 28 by category, not by marking them complete. Seven separated before assignment: remove from the required population with HR documentation; do not mark complete. Five on leave: extend the deadline under the institution's exception policy, set a return date, and document approval. Three new hires: assign within the policy window, with a due date after the board meeting. Nine active non-completers: send a supervisor escalation with a five-day cure, offer a completion lab, and record outreach. Four prior-institution records: evaluate equivalency, then either accept with documentation or assign the module. The director's request to bring the dashboard to 100% should be reframed as certifying the reconciled population with documented exceptions. Marking completions without evidence would create a false record and a worse audit finding than an explained exception.
3. Who owns which part of the attestation, and what documentation should be retained?
Read the worked answer
Name the roles: HR owns the roster, the platform administrator owns the extract and assignment data, the compliance director owns the exception decisions, and the FAR or designated approver signs the attestation. Use a versioned report with an as-of timestamp and a methodology note. Attach the HR roster snapshot, the platform extract, the exception memos, and the support tickets. Store it read-only for the retention period. In the board briefing, lead with the reconciled rate and the categories, not the raw dashboard. State what is still open, who owns it, and the date of the next snapshot. If the platform changes after the snapshot, do not rewrite the signed report; issue a supplement. That preserves the audit trail and keeps the institutional roles clear.