Weekly completion reports the ops director actually reads

If your weekly training report is a 12-page PDF with charts, the ops director is not reading it. They are deleting it. A useful weekly completion report is one screen long, opens with a single headline number, names the three locations that need intervention this week, and ends with one line per district manager. Anything longer competes with their inbox and loses. ## The ops director's reality A franchise ops director runs four to twelve direct reports, sees fifty to two hundred Slack messages an hour during peak, and gets pulled into operational fires (a closed location, a supplier issue, a regional manager resignation) on a daily basis. Training is one of fifteen things they care about. Your weekly report has about ten seconds of attention before it gets archived or deleted. Design the report for that ten seconds. ## The structure that works **Subject line: the headline number.** Not "Weekly Training Report Week 23." Use "Network completion 87% (-2pt) — 3 locations behind." The subject is the report. If the ops director never opens the email, they still got the signal. **Top of email: one paragraph, three sentences.** Network completion this week, change vs last week, the three locations bottom-of-table. That is the report. Everything below is appendix. **Mid-email: the bottom-three table.** Three rows. Location name, district manager, completion %, overdue count, a one-line note ("new manager, ramping" / "seasonal hires not yet enrolled" / "system issue, see ticket"). The note is the diagnostic; without it, the table is a list of percentages. **Bottom of email: district roll-up.** One line per district manager: name, district average, change vs last week. This is the accountability layer. The ops director scans, sees which districts are slipping, messages those district managers directly. That is the entire report. No charts, no trend lines, no engagement scores. The ops director can drill in via the dashboard if they want more. ## What to leave out Resist these temptations: - **Charts.** They look professional and they communicate nothing in an email skim. The dashboard has charts; the report does not need them. - **Engagement metrics.** "Average time on platform" tells the ops director nothing actionable. Cut it. - **Module-level breakdown.** That is for the L&D team's view, not the ops director's. Cut it. - **Year-over-year context.** This is a weekly report, not a quarterly review. Cut it. - **The training team's commentary.** The data speaks. Commentary slows down the read. Every line you cut makes the lines you keep weigh more. ## Automation, not a manual write-up If the report is hand-written every Monday by an L&D coordinator, it will eventually be late, inconsistent, or skipped during vacations. The report should be automated — generated by the platform, sent on a schedule, with the same shape every week. Aristotl's HQ dashboard exports a weekly report in this exact format by default — subject line auto-generated from the network completion number, bottom-three table auto-populated, district rollup auto-populated. The L&D coordinator does not write it; they review it and add the diagnostic notes (the "new manager, ramping" line) before it sends. Twenty minutes of work per week, not three hours. ## What changes when this is in place Three weeks after switching to this format, the ops director will start replying to the email. Usually with a forward to the relevant district manager: "Site 22 — what's going on?" That is the goal. The report is not a status update for filing; it is a trigger for intervention. The district managers learn quickly that being in the bottom-three table is uncomfortable. They preempt by intervening before the Monday report. Network completion drifts up. The bottom-three becomes a different three locations every week, then becomes harder to find. That is the report doing its job. ## When to break the rules Three exceptions where the report should be longer: 1. **Quarter-end.** A monthly or quarterly summary can carry a chart and a YoY comparison. Different cadence, different scope. 2. **Audit prep window.** When an audit is six weeks out, add a "compliance window" section showing refresher coverage. The ops director cares about this then. 3. **Major rollout week.** If a network-wide SOP rollout launched on Monday, the ops director wants to see early adoption — "24 hours in: 38% started, 12% complete" — at the top of the report. Replace the regular structure for that week only. Outside those windows, hold the line on the one-screen format.

Ready to put this into practice?