Weekly Status Update Collector

The problem this kills

Every Monday the same scramble starts. You email a dozen project owners asking for their weekly update. A few reply in a tidy paragraph, a few reply in a wall of text, a few reply "same as last week," and a few don't reply at all. You spend Tuesday chasing the silent ones, Wednesday copy-pasting answers into a master deck, and by the time the roll-up reaches leadership it's half-stale and you're not even sure every project is represented.

The information itself isn't hard. The collection is. There's no single place that knows who owes an update this period, who has submitted, who is late, and what last week said. So you become that place - the human inbox-and-spreadsheet that nags, formats, and consolidates by hand, week after week.

This tool takes that job off your plate. It knows the cadence, knows who owes what, asks each owner with a short structured form, chases the people who haven't answered, and hands you a clean, deduplicated, ready-to-review set every period - so you review and approve instead of assemble.

What you'll build

A small internal web app, tailored to your projects and your status fields, that:

• Sends update requests to each project owner on your cadence, with a private link to a short structured form (progress %, RAG status, risks, blockers, next steps - whatever you actually use).
• Pre-fills last period's answers so an owner with no change can confirm in ten seconds instead of starting from a blank page.
• Tracks who has and hasn't responded in a live dashboard: submitted, in-progress, missing, late.
• Chases the laggards automatically with polite reminder emails on a schedule you set, and flags anyone still missing.
• Deduplicates on project + reporting period, so the same status can't be submitted or counted twice.
• Gives the PMO an approval gate: you review every submitted update, edit or send-back if needed, and approve the consolidated set before it becomes the official roll-up.
• Exports a clean CSV of the approved, consolidated updates in exactly the columns your reporting deck or system expects.

What's inside the Implementation Plan

The plan is a single markdown file you paste into Claude Code. It builds the whole tool with you, step by step, each step ending in a ready-to-paste prompt.

Before it writes a single line, the plan interviews you about your business - your projects, your owners, the exact status fields and RAG wording you use, your cadence, your reminder rules, and your messy edge cases (owners who run several projects, projects on pause, mid-week handovers). It reflects a short tailored spec back to you and waits for your thumbs-up. That's the difference between a generic form builder and a tool that fits how your PMO actually runs - it's built around your answers, not a template.

From there it walks through the data model, the secure login, the request-and-collect flow, the auto-chase reminders, the PMO review-and-approve screen, and the CSV export - and ends with a checklist so you can prove it works.

The governance it includes (this is the point)

This isn't a survey toy. It's built with the controls a PMO needs to trust the output:

• Login so only your team and your project owners can touch it.
• Row-level security so each owner sees only their own projects, and the PMO sees the whole portfolio - never another organization's data.
• A complete audit trail: who submitted what, who edited it, who approved it, and exactly when.
• A hard human-in-the-loop approval gate: submitted updates are drafts until the PMO reviews and approves the consolidated set - nothing becomes the official roll-up automatically.
• Duplicate guards keyed on project + reporting period, so a double-submit or a re-run can't create a second status for the same week.

Who it's for

PMO leads, program managers, and delivery directors who own the weekly or biweekly portfolio roll-up and are tired of being the human collection-and-chase engine. If you herd status updates from a list of project owners and assemble them into a report, this is for you - and you don't need to write code.

You've got this. Open the plan, paste the first prompt, and let it interview you.