Weekly Report AI workflow template: A weekly report every number traces back.

The ConvOps Weekly Report template makes your AI produce a status report in four steps: gather the week's inputs, draft a report a stakeholder can read in under a minute, review it so every claim traces to an input, then publish. You approve before it goes out. Reject it and it returns to Draft.

4 steps · 1 approval · 1 loop back

Weekly Report · example runyour AI client
  1. 01Gather
  2. 02Draft
  3. 03Reviewwaits for approval
  4. 04Publishclosing note
task created · workflow attached

example · the steps are this template's real steps

in short

What does the Weekly Report template do?

For managers and operators who write the same status update every week from scattered notes and task updates.

Weekly Report is stored in ConvOps as four steps, and your AI client receives them one at a time. A Weekly Report run holds at Review until an explicit approval is given.

  • Write a weekly team status report from scattered updates
  • Turn the week's notes into a clear progress update for stakeholders
  • Draft a recurring project report with wins, blockers, and next steps
step by step

How does the Weekly Report workflow run?

The 4 Weekly Report steps in order, each with the instruction your AI receives there as Weekly Report stores it.

Gather
Draft
Reviewapproval
Publishclosing note

A status report a stakeholder reads in under a minute, where every number traces to a gathered input, published after your approval.

  1. 01

    Gather

    the agent works

    Collect the inputs for this report before drafting.

    Record:

    • The reporting period and the audience for the report
    • What got done this week: completed work, shipped items, results
    • In-progress work and where it stands
    • Blockers and risks
    • Any metrics or numbers to include
    • What is planned for next week

    Pull from notes, task updates, or the operator's recollection. If a key area is empty, ask before assuming nothing happened.

    Save the gathered inputs as a task note with task_notes_add. The next step (Draft) reads this note.

  2. 02

    Draft

    the agent works

    Read the task notes with task_notes_list: the note from the Gather step contains the week's inputs. Work from it.

    Write the report. What good looks like:

    • A one- or two-line headline summary of the week
    • Wins and completed work
    • In-progress work with status
    • Blockers and risks, with what is needed to clear them
    • Metrics, if any, with plain context
    • Next week's plan

    Keep it scannable: a stakeholder should grasp the state in under a minute. State numbers plainly; do not inflate.

    Save the full report draft as a task note with task_notes_add. The Review step reads this note.

  3. 03

    Review

    waits for your approval

    Read the task notes with task_notes_list: the Draft note holds the report and the Gather note holds the source inputs. Work from them.

    Review the report:

    • Every claim and number traces back to a gathered input
    • Blockers are stated honestly, not buried
    • The summary matches the body
    • Nothing important from the inputs was dropped

    Ask the operator to approve the report for publishing. This is a checkpoint: once published it informs decisions, so the AI cannot advance until you approve. If you reject, the workflow returns to Draft.

    rejected → back to Draft

  4. 04

    Publish

    closes with a note

    Read the task notes with task_notes_list: the Review note holds the approved report. Work from it.

    Publish the report to its audience: the channel, doc, or email the team uses. Save the published report as a task note with task_notes_add so the record of what was sent stays on file, then close out the task.

reach for it when

  • The same readers expect the same update on the same day every week.
  • The inputs are scattered across notes, tasks and messages.
  • A wrong figure in the report would mislead a decision.

something else fits when

  • It is a one-off summary, which a Task handles.
  • The readers need the numbers as they change, not a weekly snapshot.
  • There is nothing to say beyond what the tracker already shows.
example · regional retailenterprise

The Friday store-operations update

A regional manager has the agent gather sales notes, staffing gaps and open tickets for twelve stores. Review flags one figure with no source, and the manager approves the corrected draft.

Review approval, run on a weekly schedule

where approval is required

Where do you approve in Weekly Report?

Weekly Report holds at Review until an explicit approval is given, recorded with the account that gave it.

step 3

Review

Once published, the report informs decisions. Your AI checks every number against the gathered inputs and that blockers are stated honestly, then you approve or send it back to Draft.

what you review

  • Every claim and number traces back to a gathered input
  • Blockers are stated honestly, not buried
  • The summary matches the body
  • Nothing important from the inputs was dropped

reject → back to Draft

gates the engine checks without you

  • Publish closes Weekly Report only when your AI leaves a closing note, saved on the task.
what you need

What do you need to run Weekly Report?

make it yours

How do you customize Weekly Report?

Once installed, Weekly Report is a workflow in your workspace. Ask your AI to change Weekly Report in plain words; the edit lands on the one step that needs it.

ChatGPTexample

new chat

In Gather, always pull the tasks completed in our workspace this week.
workflow_step_update · Weekly Report
Done. Weekly Report in your workspace now has the change, and every new run follows it.

more example prompts

  • "In Gather, always pull the tasks completed in our workspace this week."
  • "Add a section to Draft: decisions needed from leadership."
  • "Schedule this workflow every Friday at 3 pm."
the difference

Weekly Report: without a workflow vs with it

  • The weekly report becomes a last-minute scramble that leaves out the blocker that mattered
  • The update ships with a number that was never checked and a claim nobody verified
  • Each week the report looks different and readers cannot find what they need
  • Last month's reports are scattered across chats and nobody can trace what was claimed when
  • The Weekly Report process lives in a prompt, and each run follows it a little differently
  • The AI drives a Gather step first, so the report is built on the week's real inputs, not memory
  • The AI pauses at a review checkpoint so you confirm the report before it is published
  • The AI drives the same structure every week, so wins, blockers, and next steps land in the same place
  • Every step (Gather, Draft, Review, Publish) is logged, so every report's history is already there
  • Your AI receives the 4 stored steps one at a time, and the run holds at Review until an explicit approval is given
questions

Weekly Report template FAQ

What is the ConvOps Weekly Report template?

The ConvOps Weekly Report template makes your AI produce a status report in four steps: gather the week's inputs, draft a report a stakeholder can read in under a minute, review it so every claim traces to an input, then publish. You approve before it goes out. Reject it and it returns to Draft.

Where does the report get its numbers?

From the ConvOps Gather step: the reporting period and audience, completed work, in-progress work, blockers and risks, metrics and next week's plan, pulled from notes, task updates or your own account. If a key area is empty, your AI asks before assuming nothing happened, and saves the inputs as a task note that Draft and Review read.

What does the review check?

The ConvOps Review step reads the draft and the gathered inputs side by side and checks that every claim and number traces back to a gathered input, blockers are stated honestly rather than buried, the summary matches the body and nothing important was dropped. The run holds there until an explicit approval is given. Reject it and the run returns to Draft.

Can the report run every week on its own?

ConvOps can schedule recurring work with a repeat rule, so a weekly report task can start every Friday. The Review approval still holds the run until an explicit approval is given before anything is published, and the Publish step saves the sent report as a task note, so every week's version stays on file next to its inputs.

What does a good weekly report look like here?

The ConvOps Draft step asks for a one- or two-line headline summary of the week, wins and completed work, in-progress work with its status, blockers and risks with what is needed to clear them, metrics with plain context, and next week's plan. A stakeholder should grasp the state in under a minute, with numbers stated plainly and never inflated.