A weekly report template, minus the Friday scramble

Why the Friday report is so annoying

Writing the thing takes ten minutes. Figuring out what to write is the slow part, because by Friday, Tuesday is gone. So the report ends up being whatever you can remember plus whatever’s sitting in Jira. That’s usually the boring ticket stuff. The things that actually mattered, like the incident you quietly fixed or the PM you got unblocked, don’t have a ticket, so they don’t make it in.

And then six months later it’s review season, and you’re doing the same archaeology again, except now it’s a whole half-year.

The weekly report format managers actually read

Most managers skim. What they’re scanning for:

• What moved this week (shipped, merged, decided, fixed)
• What’s stuck, and what would unstick it
• What you’re doing next, so next Friday holds no surprises

Nobody needs a day-by-day diary.

One more thing worth knowing: these reports travel. Your manager pastes bits into their own update, and your skip-level reads that. So write each line so it still makes sense when it’s copied out of context.

The fastest way to do that is to lead with the outcome, not the activity:

It’s the same work in both columns. The right one just says why it mattered.

Weekly report template (copy and paste)

Paste this into Slack, an email, Confluence, wherever your team does updates:

**Week of Oct 6**

**Done**
- [Outcome first], [proof: a number, who it helped, or a link]
- …

**In progress**
- [Thing]: [where it's at], [rough ETA if you have one]

**Blocked / need help**
- [What's stuck]: [who or what would unstick it]
  (Nothing blocked? Say so. That's useful too.)

**Next week**
- [Your top one to three priorities]

And here’s a sample weekly report to a manager, filled in by a backend engineer:

**Week of Oct 6**

**Done**
- Cut p95 latency on /search from 820ms to 310ms by adding a covering index
- Fixed the double-charge bug in checkout (~1.2% of orders since Mon); hotfix shipped Wed
- Onboarded Sam: first PR merged Thursday

**In progress**
- Webhook retry backoff: in review, should land Tue

**Blocked / need help**
- Need a decision from product on refund window (7 vs 14 days) before I can finish the API

**Next week**
- Ship webhook backoff
- Start the Postgres 16 upgrade plan

Two habits help a lot. First, reach for a number before an adjective: “310ms” says more than “significantly faster” ever will. Second, keep it under ten bullets. If it’s running longer than that, you’ve slipped back into diary mode, and the one line your manager needed is buried somewhere in the middle.

The real fix: write one line a day, not one report a week

A template fixes the format. It doesn’t fix the memory problem. You still have to remember what happened.

The fix is boring: write things down while they’re fresh. Thirty seconds at the end of the day, a couple of rough lines. By Friday the remembering is already done and you’re mostly editing.

That’s what Perfly is built around.

How Perfly turns that into a weekly report

1. At the end of the day you jot down a few rough lines, in whatever language you think in. Perfly splits them into separate work items and you confirm which ones to keep. If you connect Google Calendar, GitHub, Jira, or Notion, it drafts items from your activity too (metadata only, so it never sees your code or what’s inside your docs). And if you work with Claude Code, Codex, or Cursor, your agent can send the summary for you.
2. When an item would hit harder with a metric, Perfly asks for the one number that matters. How many users? How much faster? You answer once, and the number sticks to that item everywhere it gets used later.
3. On report day the draft is already waiting. Confirmed items are grouped by project into bullets, and each bullet links back to the items it was built from, so you can always trace a claim to where it came from. If your team likes paragraphs better, there’s a narrative version too.
4. You edit whatever needs editing. You can rewrite a bullet yourself, or ask the AI to make it punchier, work in a number, shorten it, or come at it from another angle, and you see the suggestion before anything changes. Then copy it, or download it as Markdown, and paste it wherever your team posts updates.

Perfly never sends anything to your manager. It writes the draft and you decide what goes out.

And it doesn’t stop at the weekly report

Those same confirmed items are what Perfly uses later for your performance self-review, and for résumé bullets when you start looking around. So the thirty seconds you spend tonight also save you a miserable weekend in review season.

FAQ

Do I have to log every single day?

No. Skip a day and nothing breaks, and connected tools still fill in what they can. The more days you capture, the better the draft gets, but it’s not a streak game.

Can I write my notes in Chinese and get the report in English?

Yes. Write notes in whatever language is fastest for you. The output language is a separate setting, so the report can come out in a different language than your notes.

Does Perfly send the report to my manager?

No. You copy it out yourself. Nothing gets sent on your behalf.

Is this a team tool?

No, it’s a personal one. There’s no team dashboard or admin view, so your log is just yours.

How much does it cost?

30 days free with everything unlocked. After that it’s $6.99 a month, or $69.99 a year.