eltyoKeep two dated snapshots of the same tracker so deadline changes stay visible and records missing from the view can be checked.
Review time changes the equation.
Adjust the assumptions. Checking the result takes time too.
Assumption: 2 minutes of AI-assisted preparation per task. Calculation: tasks × (current time − 2 min − review) ÷ 60. Excludes setup, maintenance and other costs.
To prepare a weekly report from Notion, save the tracker’s state at an agreed time and compare it with the following week’s snapshot. Claude can draft an update that links each finding to the relevant record references. The operations lead checks the differences before sharing the report.
This helps an SME see blockers, completed work and deadlines that have moved. It adds a record of change to the current tracker. The workflow below follows the vendors’ documentation. The example and expected results are fictional.
1. Prepare a stable tracking view
In your Notion database, create a view called Weekly review — operations for one team or project. Include every status so completed work remains available for comparison. Keep the scope consistent between weeks. Set up these properties.
| Property | What it contains |
|---|---|
| Item | A title the team understands. |
| Reference | A stable identifier, such as R01, retained when the title changes. |
| Status | In progress, Blocked, Done or Cancelled. |
| Owner | The person who can explain the change and confirm what happens next. |
| Due | The date of the commitment being tracked. Leave unagreed dates blank. |
In the view settings, use Copy link to view. This identifies the tracker you want to read. View filters organise the information, while the connected account’s permissions determine what it can access. Notion views · MCP connection permissions
2. Save a snapshot before each review
Add the Notion connector, published by Notion, from Claude’s connector settings on the web. Sign in with an account authorised to read the tracker, then enable Notion in the conversation. Ask it to read the selected view and check the returned references. Claude’s tool permission settings can restrict writes where your organisation makes these controls available. Notion connector for Claude · Claude connector permissions
The notion-query-data-sources tool can run a saved view. Notion documents this mode on every plan, without a quota specific to that operation. AI client usage limits, request rate limits and permissions still apply. Direct row reads and SQL have separate conditions. Ask specifically to read the saved view. Read views through Notion MCP
For the first pilot, pick a small tracker whose complete record list you can check. Verify missing or repeated references, statuses and dates. Save the five properties with the record links and reading time. If the response is incomplete, finish collecting the data before calculating changes.
You can also open the database in Notion, choose Export → Markdown & CSV, and select the current view where that option is offered. Check the exported file and keep it in the team’s approved working folder. This also provides a fallback when MCP access is unavailable. For each snapshot, record the date, time zone, view link, filters and number of distinct references. Export a Notion database
3. Check the differences on five fictional references
The example compares a snapshot from 6 November 2026 at 9 am with one from 13 November at 9 am, Paris time. The first contains R01, R02, R03 and R04. The second contains R01, R02, R03 and R05.
| Reference | What the two snapshots show |
|---|---|
| R01 — Catalogue, Maya | In progress at both readings. The deadline moves from 12 to 16 November. |
| R02 — Kits, Noah | In progress, then Blocked. The deadline stays at 20 November. |
| R03 — Instructions, Iris | In progress, then Done. The deadline stays at 10 November. |
| R04 — Pricing, Lina | Present on 6 November and absent from the 13 November snapshot. |
| R05 — Workshop, Sam | Present only on 13 November, In progress, due on 20 November. |
The expected report shows four distinct references at each reading, with three in common. It records one entry into the scope, one exit to check, one move to Done, one changed deadline and one new Blocked status.
Maya confirms R01’s new deadline and the reason for it. Noah clarifies R02’s blocker. Lina looks for R04 to check whether its filter, access permissions or classification changed. The snapshot establishes that R04 is missing. To confirm completion, the team needs to find its status. Likewise, R05’s appearance in the view calls for a check of its creation date if the report needs that information.
4. Ask for a draft with this prompt
Prepare the [date and time, time zone] operations report from the two supplied snapshots. Identify their scope, filters and reading times. Check distinct references and flag duplicates. If collection or scope is uncertain, start with the items that need checking.
Match rows by Reference. List references in both snapshots, those present only in the first or second, status changes and deadline changes. Keep the old and new date for every changed deadline. Use the owner as recorded in the source and mark missing details “To complete”.
Draft the report using the template below. Give each finding its reference and the record link where supplied. Separate observed changes from suggested explanations. Finish with decisions the owner needs to make. Prepare the draft in chat.
Copy this template after the prompt.
Report for [date] — [team]
Coverage · Snapshots compared, scope, reference counts and whether collection is complete or has gaps.
Observed changes · Reference, previous value, current value and source.
Blockers and missing details · Reference, owner and information to confirm.
Meeting decisions · Decision needed, person to ask and date to agree.
5. Establish the weekly routine
In the first week, save the starting state. From the second week onwards, keep both snapshots and the approved report. Reading the current tracker describes its state at the time of access. To count every event during the week, including a change reversed between readings, keep a change log.
You start this pilot on demand. To produce the draft at a set time, choose scheduling that can retain the snapshots and pass the result to the review owner. First test a complete batch, records without an owner and an interrupted connection. Compare preparation and checking time with your usual review over two or three runs. Eltyo’s method for measuring an automation
Explore the original sources.
The references behind this approach. Examples and exercises in this article are illustrative.