What this covers
The pain: it is 4:30pm on Friday and you cannot remember what you did on Monday. You spend 45 minutes reconstructing the week from Slack, Linear, and your inbox, and the report still reads as a generic “kept making progress” paragraph. This workflow inverts the problem: you capture raw notes daily (90 seconds per day), then on Friday AI turns them into a structured weekly report in under 5 minutes. The output: 3 wins, 2 blockers, 1 ask, 3 next-week priorities, under 300 words, with one human-take sentence your manager actually reads.
Who this is for
ICs and managers who file weekly reports — whether to a manager, to a skip-level, or to a recurring 1:1 doc. Especially useful for engineers, designers, PMs, and analysts who do a lot of small things in a week and find the granularity hard to summarize. Also for managers who file an upward report and a downward report on the same week — the same daily log feeds both.
When to reach for it
Every Friday or end-of-shift before a manager check-in. Also the night before a 1:1 if your team uses an async pre-read. Also for project-level reports that roll up across multiple weekly cycles — the daily-log discipline scales straight up. Skip it the first week you start a new job; you do not have enough signal to summarize yet.
Before you start
- Pick one daily-capture surface and stick to it: a single doc, a Notion page, a Linear “personal” project, a plain text file. Switching surfaces breaks the habit.
- Decide your reporting cadence and structure once: 3-2-1-3 (3 wins, 2 blockers, 1 ask, 3 next-week priorities) is a defensible default; adjust to match your team’s template.
- Set a 90-second daily reminder. Something like 4:50pm or end of last meeting. Make it cheap to capture; the bar is one bullet per item.
- Know your manager’s read pattern. Some skim the TL;DR; some read the asks section first. Order your report by what they actually read.
- Have last week’s report open as a reference. Continuity from week to week is part of the signal.
Step by step
- Throughout the week: capture wins, blockers, discoveries, and questions in a single raw doc. Plain bullets, no formatting. Aim for 2 to 5 bullets per day. Example bullets:
shipped invoice export PR, took 2 days vs 1 estimate, postgres copy slower than expected. - On Friday: paste the raw doc into AI with a prompt. Example:
Convert this week's notes into a weekly report.
Format: 3 wins, 2 blockers, 1 ask, 3 next-week priorities.
Under 300 words total. Plain language, no buzzwords, no "leverage" or "synergy".
Notes:
[paste raw doc]- Review the output. AI will sometimes invent connections that are not in the source (“this win directly enabled X” when X is unrelated). Verify every claim traces back to a specific bullet.
- Edit for your voice and add the one thing AI cannot generate: your take. One sentence with your opinion, your judgment call, or the thing you would say in person. This sentence is where the human signal lives.
- Submit. Save the prompt and the input doc as next week’s template. Optionally archive a copy in a
weekly-reports/folder. - Optional: pre-1:1 read. The night before your 1:1, drop the same notes into AI with a different prompt asking for “the 3 questions my manager will probably ask me about this week”.
First-run exercise
Pick the week that just ended. Reconstruct a daily-log doc from Slack, Linear, and your inbox — yes, the manual way, this one time. Run the prompt and compare AI output to what you would have written yourself. Most people find AI is better at structure and worse at voice. The lesson is to use AI for the bucketing and the word-count discipline, and spend your 2 minutes on the human-take sentence. Start the daily-capture habit Monday so next Friday is the real test.
Quality check
- Every claim in the report traces back to a specific bullet in the raw doc. AI invents connections; you verify.
- Word count is under your target (300 words is a reasonable ceiling). If AI produces 500, ask for a re-trim, not a manual edit.
- The “ask” is named, specific, and time-bound. “I need budget approval by Wednesday from finance” yes; “more support would be nice” no.
- The human-take sentence is yours, not AI’s. Read aloud — if it sounds like a press release, rewrite it.
- Next-week priorities are 3 items, not 10. Lists with 10 priorities have 0 priorities.
- Blockers are actually blockers — something blocking progress — not “could go faster with help”.
How to reuse this workflow
- Save the daily-capture doc with a date-stamped header at the top of each week so future-you can find the source for any week’s report.
- Save your prompt as a snippet. Tweak only the date and section count week to week.
- Every 4 to 6 weeks, look at the trend across weeks: are the same blockers showing up? Are the next-week priorities sliding? The diff is more useful than any single week.
- Build a personal “highlights” doc by copying the wins section into one running file. After 6 months, this is your perf-review preparation kit.
- Share the daily-capture template with one teammate. Comparing what each of you captures surfaces blind spots.
Recommended workflow
Daily 90-second capture into a single doc → Friday paste-and-prompt for the 3-2-1-3 structure → fact-check every claim against the source bullets → edit for voice and add one human-take sentence → submit → save prompt and notes as next week’s template → quarterly trend review across stored reports.
Common mistakes
- Trying to remember the week instead of capturing daily. Friday-only reconstruction misses 30 to 50% of the real signal and feels like a chore.
- Submitting AI’s version verbatim. Managers see a lot of weekly reports; they can tell within 2 sentences when it is AI-only.
- No human-take sentence. Without it, the report is bureaucratic noise; with it, it becomes a 1:1 conversation starter.
- Letting next-week priorities balloon to 6 or 8. Pick the 3 that matter.
- Listing every micro-task in the wins section. Three substantive wins beats ten trivial ones.
- Skipping a week because the week was “slow”. Send the report anyway — cadence is the trust signal.
FAQ
- My manager wants a different format.: Adjust the AI prompt’s section count and order, keep the daily-capture format the same. Your input pipeline is portable.
- What if I work on too many small things to bullet?: Group by project. Each project gets one bullet per day with the day’s most important update. Three projects = three bullets per day.
- What about confidential information?: Keep customer names and revenue numbers out of the AI prompt. Use role tags (“EU enterprise customer”) and round numbers (“around $50K ARR”).
- Should I do this for personal projects too?: Yes. Weekly logs are how you remember what you actually shipped six months later.
- How long should I keep the archive?: One year minimum. After 4 quarters you have a perf-review-ready document.
- Can AI write the human-take sentence?: It can draft, but the value disappears. The human-take sentence is the part of the report that proves you thought about the week.