Skip to content

Weekly delivery status report

Pulls your team's work items once a week and builds a status report grouped by initiative. It puts at risk items first and flags anything with no update in two weeks.

OperationsWorks with Claude Code · Zapier Agents+1Community example
Build your promptSee requirements

What it does

  • Pulls work items and their status from the tracker
  • Groups them by initiative and product area
  • Compares to last week and marks new, changed and unchanged items
  • Flags at risk items with no change and items not updated in 14 days

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Emailing the report
  • Publishing the report site

You decide what happens next.

More about this workflow

This setup is for operators and managers who keep the busywork moving. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it pulls work items and their status from the tracker. Next, it groups them by initiative and product area. Then it compares to last week and marks new, changed and unchanged items. Finally, it flags at risk items with no change and items not updated in 14 days. It works with your issue tracker, email and git host, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before emailing the report and publishing the report site, and says plainly if a step cannot be undone.

“Unchanged items last, greyed out”
robert-onuma-cko robert-onuma-cko on GitHub · Sep 8, 2026
Before you startIssue tracker · Email accessScoped permissionsClaude Code or Zapier Agents
Explore required tools and model recommendations

Tools and access

  • Linear

    Handles the issue tracker part of this job. Grant read plus create in one triage team.

    API required: Yes. Needs a personal API key or an OAuth app.

    Sign up: Linear

  • Gmail

    Handles the email part of this job. Grant read-only plus compose (drafts) scopes.

    API required: Yes. Needs a Google Cloud project with an OAuth app and the Gmail API turned on. The agent signs in through OAuth with only the scopes you pick.

    Sign up: Google Workspace

  • GitHub

    Handles the git host part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

    Sign up: Create a GitHub account

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Cheap cached input suits jobs that rerun the same instructions each week.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for simple data pulls and matching.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

which items to include

e.g. initiative, team

day and time

2Your prompt

4 of 4 still empty
Fill these in before you run it: [YOUR TRACKER QUERY: which items to include] [HOW TO GROUP: e.g. initiative, team] [WHO GETS IT] [WHEN TO RUN: day and time] You are the Weekly delivery status report agent. Pulls your team's work items once a week and builds a status report grouped by initiative. It puts at risk items first and flags anything with no update in two weeks. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Pulls work items and their status from the tracker - Groups them by initiative and product area - Compares to last week and marks new, changed and unchanged items - Flags at risk items with no change and items not updated in 14 days What you must never do without a yes from a person: - Emailing the report - Publishing the report site Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Zapier Agents, n8n

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Linear with its own login, not yours. Grant read plus create in one triage team.
  2. 2Connect Gmail with its own login, not yours. Grant read-only plus compose (drafts) scopes.
  3. 3Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: emailing the report, publishing the report site.

Undo and logs17 / 20

Leaves drafts you can throw away, with a record of what it made.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 81.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Weekly delivery status report](https://trustcase.dev/badge/weekly-delivery-status-report.svg)](https://trustcase.dev/use-cases/weekly-delivery-status-report)
HTML
<a href="https://trustcase.dev/use-cases/weekly-delivery-status-report"><img src="https://trustcase.dev/badge/weekly-delivery-status-report.svg" alt="Trustcase trust score for Weekly delivery status report" height="20"></a>

More operations workflows

  • Spoken site update to daily report

    Turns a short spoken end of day update from a crew lead into a structured daily report. Plain rules, not the AI, decide who hears about each issue.

  • Business expense report builder

    Reads your credit card statements and pulls out the charges that look like business expenses. Sure items and unsure items go on separate tabs so you only review the doubtful ones.

  • Monthly contractor invoice builder

    Builds your monthly invoice and timesheet PDF from weekly timesheet screenshots. It checks the hours before filling your template.

  • Daily delivery app sales log

    Reads yesterday's sales from each delivery app and your point of sale every morning. Writes the totals into one sales sheet.