Write a Weekly Req Update for Stakeholders
When to use it
Send an update that gets read and prompts a decision, instead of a wall of numbers nobody opens.
The prompt
Write this week's update on the {{Job Title}} search for {{the hiring manager and whoever else reads it}}. THIS WEEK'S ACTIVITY: {{sourced, replied, screened, submitted, interviewed, offers}} WHERE EACH LIVE CANDIDATE IS: {{initials and stage}} WHAT'S BLOCKING ME: {{feedback outstanding, scheduling, the comp band, an undecided must-have}} WHAT CHANGED SINCE LAST WEEK: {{...}} HOW LONG THE REQ HAS BEEN OPEN: {{weeks}} Give me: 1. Three lines that work if they read nothing else: where we stand, what I need, by when. 2. The numbers, only the ones that moved, with one line on what each means. 3. The asks, each named to a person with a date attached. 4. The honest risk line: what happens to the timeline if the blockers stay blocked. 5. What to cut from what I gave you because it's activity rather than progress. Under 200 words. No filler, and no "great progress this week" if there wasn't any.
Tip
Lead with the ask, not the activity. Hiring managers skim these for what they have to do, and the numbers are there to justify the ask rather than to prove you were busy.
How to use it
Paste the prompt into ChatGPT, Claude or whichever assistant you use, then replace every {{bracketed}} part with your own detail. The more specific and messier your input, the better the output — a model given raw notes has more to work with than one given a tidy summary you wrote first.
More Reporting & Metrics prompts
Open the full tool for all 87 prompts, the glossary, and the JD decoder.