Review schedules

Review schedules

A review schedule is a promise that somebody looks at a page on a cadence.

Setting one

Two fields in frontmatter:

---
title: Rotating an API token
owner: ada@example.com
review_every: 90
last_reviewed: 2026-08-01
---

review_every is days. Common values are 30, 90, 180 and 365. You can also set schedules in bulk from the writer.

Choosing a cadence

Cadence	For
30 days	Pricing, limits, anything a release changes.
90 days	Most product documentation.
180 days	Conceptual pages and architecture.
365 days	Policies and stable references.

A cadence you will not keep is worse than none, because an overdue review is a suspicion signal on a page that was fine.

Owners

owner is the email address of the person answerable for the page. They are notified when a review is due.

An owner who is not a member of the workspace raises unknown-owner, a warning. A page with no owner at all is a health issue: a review nobody is assigned is a review nobody does.

When a review is due

The owner is notified and can do four things:

Confirm it is accurate. This updates last_reviewed without changing a word of the page. This is the action that makes schedules work: confirming costs seconds, so people do it.

Edit it. The ordinary flow. A publish updates the date.

Reassign it. To whoever now owns the feature.

Snooze it. When you know a change is coming and reviewing now would waste the visit.

Generated pages

A page written by staleless document carries no last_reviewed. A machine that wrote a page has not reviewed it, and Pulse stays suspicious of it until a person says otherwise.

What a review is not

It is not a publish. Confirming accuracy creates no new content and no reader sees a change. It records that somebody with their name on the page looked at it on a date.