Weekly Notion project status roll-up
Every Monday, a roll-up of your Notion projects grouped by status, with stalled, overdue, and blocked items called out and linked back to Notion.
Mondays at 8:00 AMProductivity Emailed to you
Use this routine →Opens prefilled — review and save.
Works with
The instructions
Every Monday at 8am, read my Notion projects database, group the projects by status, and flag what needs attention. 1. Locate the projects database first. Search Notion for the projects database by the name I give you (I'll tell you the database, plus which property is the Status and which is the Due date — Notion has no universal field names, so use the ones in my schema). If you can't find a database matching that name, say so plainly and stop instead of guessing at a different one. 2. Read the project rows. Query that data source, paginating through every page so nothing is missed on large databases. For each project, capture its name (the title property), its Status value, its Due date if set, the owner/assignee if present, and the page link so items can be clickable. 3. Group by Status. Roll the projects up under each Status value (e.g. Not started / In progress / Blocked / Done), with a count per group. 4. Flag at-risk items using only these three signals: stalled — the page hasn't been edited in roughly 14 days (use the page's last-edited timestamp; note this means "not edited recently," not necessarily "no work done"); overdue — the Due date is before today; and blocked — only if my schema models it (a Blocked status value or a flag I point you at). Don't infer risk beyond these. Deliver the result as an email roll-up: a one-line summary up top (open vs. at-risk counts), then a section per status group, then an "At-risk" section listing each flagged item with its reason, owner, and a link back to Notion. Stay read-only — only read and summarize; do not edit, move, or create anything unless I've explicitly turned the write-back on. If the database returns no rows, or a property I named isn't present, say so plainly instead of guessing.
What a run emails you
Notion projects — week of 29 Jun 2026 31 active projects · 6 need attention (2 overdue · 3 stalled · 1 blocked). By status • In progress — 14 • Not started — 9 • Blocked — 1 • In review — 7 Needs attention • Q3 pricing rework — overdue (due 26 Jun) · Priya N. · open in Notion • Mobile onboarding v2 — overdue (due 24 Jun) · Devin R. · open in Notion • Billing migration — stalled, not edited in 18 days · Sam O. · open in Notion • Help-center refresh — stalled, not edited in 21 days · unassigned · open in Notion • SSO rollout — stalled, not edited in 15 days · Priya N. · open in Notion • Data-export API — blocked (waiting on vendor) · Lee K. · open in Notion Read-only run — nothing in Notion was changed.
How it works
- Attach your Notion connection and tell the routine which database holds your projects, plus which property is the Status and which is the Due date — Notion has no universal field names, so it keys off the ones in your own schema. It only sees pages and databases you've explicitly shared with the integration, and reads them, nothing else.
- It groups every project by status, then flags at-risk items using three concrete signals: stalled (not edited in roughly 14 days, via the page's last-edited timestamp), overdue (due date is in the past), and blocked (only when your database models that — a Blocked status value or a flag you point it at).
- Keep "Email me the result" on to get the status roll-up with each at-risk item linked straight back to Notion every Monday morning.
Make it yours
- Tune the at-risk rules — change the ~14-day "not edited" window, adjust how overdue is measured, or scope the roll-up to one team, owner, or sub-database.
- Point it at a different projects database or rename which properties count as Status and Due date if your schema changes.
- Turn on the optional write-back to have the roll-up saved to a Notion page each week — off by default, so the routine stays read-only unless you opt in.
Your workspace stays yours: connection tokens are encrypted at rest, the integration only touches the pages you share with it, and the routine is read-only unless you explicitly enable the write-back.
Run “Weekly Notion project status roll-up” on autopilot
Copy it to your account, tweak the details, and it runs mondays at 8:00 am.
Use this routine →More Productivity templates
Weekly Airtable rollupProductivity
Every Friday, roll up the week's Airtable changes and email a clean summary to your team.
Fridays at 5:00 PM
Weekly overdue Asana tasks roundupProductivity
A Monday email of every overdue and due-this-week Asana task, grouped by owner.
Mondays at 9:00 AM
Daily standup doc in CraftProductivity
Every weekday at 7am, create a fresh, dated standup note in Craft — pre-structured with Yesterday / Today / Blockers, and primed with your calendar for the day.
Weekdays at 7:00 AM
Day-ahead calendar briefProductivity
Each evening, a prep brief for tomorrow's meetings — context and last email thread per attendee.
Sun–Thu at 6:00 PM