Project Status Board
Every Monday I rebuild the same status report from scratch.
One row per project and one square per week, marked on track, at risk or blocked. Owners update their own row and the report builds itself.
- No.
- 008
- Department
- Ops
- Build time
- 1 hr
- Difficulty
- Beginner
- Team size
- 5–50 people
- Replaces
- Monday.com
Parts
- 1
Projects
Name, owner, due date, and one line on where things stand.
- 2
Weekly health
A green / amber / red dot for each week, so trends are obvious at a glance.
- 3
Owner update
Each owner gets a Friday nudge to set their status and add a sentence.
- 4
Leadership view
A clean read-only page you can share instead of a slide.
Data model
- Project { name, owner, due_on, archived }
- Update { project_id, week_of, health, note, by }
Build prompt
Build an internal tool for my team: "Project Status Board".
The problem: Every Monday I rebuild the same status report from scratch.
Who uses it: a team of 5–50 people.
What it should do:
- Projects: Name, owner, due date, and one line on where things stand.
- Weekly health: A green / amber / red dot for each week, so trends are obvious at a glance.
- Owner update: Each owner gets a Friday nudge to set their status and add a sentence.
- Leadership view: A clean read-only page you can share instead of a slide.
Data:
- Project { name, owner, due_on, archived }
- Update { project_id, week_of, health, note, by }
Constraints:
- Built for one team inside one company. Simple sign-in (or none), no billing, no multi-tenant setup.
- Fast, calm and obvious enough that teammates need zero training.
- Data must persist and be shared across the team.
- Ship the simplest version that works, then tell me what you'd add next.Works with Claude, ChatGPT, Cursor, Lovable, Replit or Type.
Variations
- Post the summary to a Slack channel on Monday morning
- Group projects by team or quarter goal
- Flag anything red two weeks in a row
A new blueprint every week
Sent on Sundays. One tool per email.
More blueprints
Client Onboarding Tracker
Client onboarding lives in one person's head, and things fall through the cracks.
- No.
- 006
- Dept.
- Ops
- Build
- 1–2 hrs
- Replaces
- Rocketlane
Approval Workflow
Purchase requests get lost in Slack, and nobody knows who approved what.
- No.
- 007
- Dept.
- Ops
- Build
- 1–2 hrs
- Replaces
- Kissflow
Simple CRM
We pay for a giant CRM and use about ten percent of it.
- No.
- 001
- Dept.
- Sales
- Build
- 2 hrs
- Replaces
- HubSpot