Wisaven
πŸ—“οΈ

Weekly Report Template: Structure, Example and How to Write One

A weekly report tells your manager what moved this week, what is stuck and what you plan next, in the two minutes they have for it. The good ones lead with results and numbers, name problems together with what was done about them, and end with the one or two things you need from someone else.

Get these right before you write

  1. 1Lead with outcomes, not activity: 'closed 12 tickets, response time down to 5 min', not 'worked on tickets'.
  2. 2Every problem comes with what you did or decided; a bare problem reads as a complaint.
  3. 3Next week's plan should be checkable the following week: three items, each with a deliverable.
  4. 4Asks go last and say who, what, by when.

Structure

The document opens with these headings and blanks.

Weekly report β€” [week of …]
##Done this week
[result, with a number where there is one]
##Problems and how they were handled
[problem β†’ what was done]
##Next week
[plan]
##Need from others
[who, what, by when]

A complete example

Written by the AI from this brief, exactly as the workbench would write yours:

The weekly report of a customer-support team lead for the week of 29 September to 3 October 2026: 1,180 tickets handled, median first response 6 minutes, two payment-failure incidents escalated to the payments team, one new agent started training; next week: launch the login self-help page, hire one more agent; need from IT: the ticket export fixed by Wednesday.

Weekly Report β€” Customer Support, 29 September to 3 October 2026

This week's results

Metric Result
Tickets handled 1,180
Median first response time 6 minutes
Incidents escalated 2 (payment failures, to Payments team)
New agents in training 1
  • Volume and response time held steady through the week; the 6-minute median first response is within our target of [figure needed].
  • The new agent started training on [date needed] and is following the standard two-week onboarding plan.

Problems and how they were handled

Payment-failure incidents

  • Two separate payment-failure incidents surfaced through customer tickets this week.
  • Both were escalated to the Payments team with affected ticket IDs and reproduction details.
  • Current status: [status needed β€” e.g. root cause identified / fix pending].
  • Affected customers were told we are investigating and will follow up once Payments confirms a fix.

Ticket export

  • The ticket export tool is currently broken, which blocks our weekly reporting pull and quality review sampling. A fix request is with IT (see below).

Next week's plan

  1. Launch the login self-help page β€” publish the page and link it from the login error flow and the help centre; monitor whether login-related ticket volume drops.
  2. Hire one more agent β€” finalise the shortlist and hold interviews; target an offer by end of week.
  3. Continue onboarding the new agent and keep first response time at or below this week's level.

What I need from others

  • IT: the ticket export fixed by Wednesday 7 October, so reporting and quality review are not delayed a second week.
  • Payments team: confirmation of root cause and expected fix date for the two escalated incidents, so I can close the loop with affected customers.

Names, figures and dates in the example are made up for illustration.

How it works

  1. 1Open the template: a document with the skeleton and the brief appears.
  2. 2Add one line about your case to the brief, or attach your notes as sources, and press First draft.
  3. 3Edit directly, or ask the AI to tighten, expand or translate any passage; every AI change is reviewed before it lands.
✨ Write one from this template

Questions

Can I use the example as it is?
The example shows the shape and tone; its names and figures are made up. Open the template and give the AI your own facts, and it writes yours in the same shape.
Does it work in English and Chinese?
Yes. The document is written in the language of your brief, and any passage can be translated afterwards.
Is it free?
Writing is billed by the tokens used, usually a few credits per draft; the template, the skeleton and the editor cost nothing.

Other documents in this group

All everyday documents (27) β†’
πŸ“‹Work summaryA period's work in results, lessons and plans.🎯Self-reviewYour own case for the review: role, results, growth.πŸ—ΊοΈProject planGoal, scope, milestones, people, risks.πŸ“Meeting minutesDecisions, actions, owners, deadlines.πŸ–οΈLeave requestDates, reason, handover, in a few lines.πŸšͺResignation letterClear, courteous, with the last day and handover.🧾RΓ©sumΓ©One page that gets the interview.βœ‰οΈCover letterWhy this role, why you, in one page.