Task

Write a weekly report with AI

Sort your week into four clear sections. Work awaiting approval should stay awaiting approval.

  1. 1Understand the method
  2. 2Do it
  3. 3Check the result
1

How to do this task

Follow the method below, do the task, then check the result. Tool links show options, not extra steps you must complete.

Traditional approach
Sort one reporting period into completed work, in progress, next week, and decisions or help needed. Keep pending approvals, blockers and conflicting updates visible. Link each claim to the notes, and confirm unresolved points with the relevant person before sending.
Use AI

Open the weekly-report App below and paste non-sensitive notes for one reporting period. It produces a four-section draft: completed work, in progress, next week, and decisions or help needed. Compare every status, owner, date and blocker with your notes before copying the report. If the notes include public source links, also check that each link supports the exact claim. You can use the same prompt in an assistant you are allowed to use instead.

View ChatGPT instructions →
Prompt to use with your assistant

Turn only the notes below into four sections: completed work, in progress, next week, and decisions or help needed. Preserve the stated owner, date and outcome. Tested does not mean deployed; submitted does not mean approved. Put one activity in its current state, without counting it twice as completed. Mark missing owners or dates as not stated. Keep conflicting updates as questions to resolve. Do not invent business impact. Notes:
What can go wrong
  • The draft says “shipped”, but the notes say only that the export fix passed the test and has not been deployed. Change it to “Passed the test; not deployed” and keep it under in progress. Report a release only when the notes confirm deployment.
  • An item appears as both approved and awaiting approval. If the notes clearly identify its current status, list it once in that state. If the updates still conflict, keep both as a question to resolve; a newer date alone does not prove approval.
  • The draft invents a device owner or delivery date. Remove the guess and write “No owner or delivery date has been agreed.” Keep that missing device beside the test it blocks, then ask who can arrange it and when; asking is not assigning.
2

Run this task now

This one runs a real AI model in AhaDo. Open the app, paste your own input, and check the result before you use it.

Open the Task App →
3

Human check before use

  • Compare every completed item with the notes: tested, submitted and discussed do not mean deployed, approved or decided.
  • Check that pending approvals and missing resources remain visible as progress or blockers.
  • Check every owner and date against the source; keep missing or conflicting details explicitly unresolved.
  • Remove duplicate achievements and private details, then adapt the wording to the actual reader before sending.
Keep the final decision with a person

AI does not verify facts, arithmetic, identity or policy. Treat every generated line as a draft until you have checked it.

→

Continue with a concrete task

Choose the task that matches the material and decision you have now.

Where this comes from

No real usage, success rate, elapsed time or edit rate has been measured for this task yet.

Source type
AhaDo task instructions
Collected on
2026-08-30
Verification status
Real-user results not yet measured
Sample size
No user samples yet

Report a correction

Point out a missing step or an unsafe claim. Your note is saved in your workspace for review.

Page you are correcting: Write a weekly report with AI

When you submit, we send your correction, any source link or screenshot you choose to add, and this page’s public content. We do not automatically include your Task inputs or results.

An AI model service reviews your contribution. Do not include passwords, identity documents, personal details or confidential work.

The screenshot stays private and is visible only to you and the reviewer.