The report you write from memory is already in your ATS
Most desks review the week the same way. Somebody asks how the jobs are going, and you answer from memory: the three roles you worked hardest, the offer that is close, the client who went silent. The jobs you did not think about do not come up. Those are the ones that needed the question.
Your ATS holds the whole picture. It knows every live job, who is at which stage, and which records changed. What it does not do is read across all of it and tell you, on one page, where the week went and what has stalled. That is a reading job, and reading your own system costs nothing.
The report is short on purpose. Totals first, then the exceptions: what moved, what did not, who is waiting on you. A page you read beats a dashboard you scroll past.
What you get back
One page. At the top, the counts: live jobs, candidates in process by stage, jobs opened and closed this week. Then three lists. What moved, with the candidate, the job and the stage they moved to. The quiet jobs, oldest first, with the date of the last recorded change. The chase list, with the candidate, the client and the date their record last changed.
At the foot, a plain note of what the report could not see in your system, so an empty section is never mistaken for a clean one.
Variations worth knowing
One report per consultant. Filter by job owner and each person gets their own page.
Client by client. Group by client before an account review. It shows whose roles are ageing without movement.
Turn a quiet job into action. A live role with a thin pipeline is a prompt to look again at who you already hold: find the candidates already sitting in your own ATS.
Fix what it exposes. If the report is wrong because the records are, that is the finding. Make an old recruitment database searchable again is the follow-up.
Where this goes wrong
Stages nobody updates. The report is as true as the pipeline. If candidates are moved on in conversation and not in the system, the chase list fills with people who were dealt with last week.
Reading quiet as idle. A job worked entirely by phone shows no recorded change, which is why the report uses those words.
A snapshot read as a trend. On systems that cannot answer what changed since a date, the report shows today. It does not show movement, and it does not pretend to.
Live statuses set wrong. Leave out a status your team uses and those jobs vanish from the report. Check the first run against jobs you know.
A report nobody opens. A scheduled report waits in your workspace. If opening it is not part of your Monday, it changes nothing.
