Skip to content

The Precedent handbook

Inbox and reviews

The inbox collects drafts and decisions that need attention. A review asks you to check a choice; it does not change the choice for you.

Read your inbox

Open Inbox in the sidebar. Your items are grouped by why they need attention. Workspace administrators can switch between Mine and Everyone to see the workspace's open items.

The sidebar badge counts your open items, including when a workspace administrator views Everyone. Completing an item in the app updates the badge without a browser refresh. Navigating between pages refreshes the count to include changes made in another tab or by an assistant. When none remain, the badge disappears.

ReasonWhat to do
Awaiting your approvalApproval was asked on a draft, or someone proposed a change to a decided decision, such as a revision or a reversal, in an Area where your approval counts. The item says who asked or proposed, and when. Open Review and approve, read the record, and choose Approve, or Request changes with a note. If the draft or the proposed revision is edited after you approve, your approval no longer counts and the item returns.
Changes requestedSomeone asked for changes, with a note, on a draft you own or on a change you proposed to a decided decision. Open Review changes requested, edit the draft or the proposed revision, and ask them to approve or withdraw their request.
Drafts to finishA draft you own has not been approved. Open Finish draft, check the reasoning, complete missing details, then approve it or ask for approval.
Change requestSomeone's decision conflicts with one you own, and they asked you to change, reverse or supersede it. The item quotes both conflicting passages and the proposed change. Open Review change request and choose Accept, Adjust and accept, or Decline with a note. If the decision was revised after the request, Accept and Adjust and accept are replaced by Review and accept. For a proposed text change, compare the Now and Proposed rows on the decision first; for a reversal or supersession, check the request against the decision as it reads now. If the owner accepts, the change is proposed on their decision and applies once its Areas' approvals are in. It applies at once where the owner's approval is enough.
Review date reachedRead the decision and check whether the assumptions still hold. Choose the appropriate review action and set a new review date or condition when you reaffirm it. For an exception the item reads Expires today or Expired, and reaffirming it needs a new date.
Dependency changedRead the named change and follow Trace impact or the linked record. Decide whether your decision still holds.
Condition metRead the observation and supporting evidence. Decide whether the condition calls for reaffirming or changing the decision.
A review becoming due does not reverse a decision. The existing choice stands until someone changes it. The one derived state is Expired: a decided exception past its date shows the badge and no longer waives its target, while its status stays Decided. Exceptions reaching their date within 30 days are listed under expiring soon.

Choose the right action

When the decision page's warning banner says a review is due, its exact date appears beside the owner near the top of the page. The review field does not repeat that overdue message. If a condition notice takes priority, the overdue date warning remains visible separately. These notices describe the current decision, including when you read an earlier revision.

On a current decision, the side panel shows each review action you may take as a button: Reaffirm, Revise and Supersede, with Reverse set apart below them. On narrow screens this panel appears before the record. Each choice names the lifecycle action it performs.

ActionUse it whenResult
ReaffirmThe choice still holds.Set a new review date or condition and say why it still holds. One sentence is enough; the note is required. The open review is resolved as Reaffirmed when the reaffirmation applies, and stays open until then. When an Area posts reviews to its Slack channel, each review carries a Reaffirm button, which asks for the next review and a note, as Precedent does. Where the reaffirmation needs more approvals, the form that button opens says which ones, its button reads Propose reaffirmation, and the reaffirmation waits for them. While a change to the decision is proposed, its review in Slack names who proposed it and has no Reaffirm button.
ReviseThe same choice needs updated wording, reasoning, or assumptions.Save a revision under the same reference with a change note. Until it applies, the revision in force does not change. Earlier revisions remain available.
SupersedeA new choice replaces this one.Create a separate successor. The original stays current until the successor is decided, then becomes Superseded.
ReverseThe choice no longer holds and there is no replacement decision.Record a reason. Once the reversal applies, the record remains available with Reversed status.

Reaffirming, revising, reversing or archiving a decided decision, or superseding it with another decided decision, needs its Areas' approvals. It applies at once where your own approval is enough. Otherwise it is a proposed change: it waits for its Areas' approvals, and the decision stays Decided, with its text in force unchanged, until the change is approved. Where a change would wait, its button says so before you press it: it reads Propose revision, Propose reaffirmation, Propose reversal, Propose archiving or Propose supersession in place of Save revision, Reaffirm decision, Reverse decision, Archive or Supersede decision. The dialog, or the line beside the revision's button, says which approvals it still needs. A decision has at most one proposed change at a time. See Approve decisions.

Available actions depend on your role, ownership, area access, and workspace state. Owners, Area administrators and workspace administrators can Revise; a non-owner Maintainer can Reaffirm or Reverse but cannot Revise. Members can start a successor, and it still needs the approvals its Areas require. Drafts retain Edit draft and approving; closed records offer their successor or a follow-up where appropriate.

Outcome history

Every review records its outcome when it is resolved: Reaffirmed, Revised, Superseded, Reversed or Archived. The review keeps the reason given with the action: the reaffirmation note, the revision's change note, or the written reason for superseding, reversing or archiving. It also keeps who resolved it and when.

The Outcome history section on a decision lists its reviews, newest first. Anyone who can see the decision can read it, and it is included in the JSON export with each review item and in get_decision for assistants, where a reaffirmed review has the stored outcome value held. Reviews resolved before outcomes were recorded show Not recorded. When one action resolves several open reviews, such as a passed review date and a dependency change, they are listed and counted as one review with both reasons.

Reaffirming, superseding or reversing a decided decision is a judgement on whether it still stands, so it is recorded when it applies, even when no review is open. It appears as an Unscheduled review in the outcome history and counts in Insights, but it was never an inbox item. Revising or archiving a decision with no review open is an edit or a cleanup and records no outcome. Client portals keep their own History card and do not show the outcome history.

Insights rates these outcomes per area. If AR-041 (Postgres full-text for search) is reaffirmed at two reviews and revised at a third, each of its areas shows three recorded reviews, two of them reaffirmed.

Administrative controls

Archive and Legal hold appear separately under Administrative controls. This includes authorised draft archiving. An Area administrator or a workspace administrator can also change the owner of a current decision.

Archive removes a record from working lists. Area administrators and workspace administrators can archive current or closed records; a draft's creator or owner can also archive their draft when their area role permits writing. Archiving a decided decision applies at once where your own approval is enough, and otherwise waits for its Areas' approvals as a proposed archiving; a draft or a closed record is archived at once. A configured retention policy can later permanently delete an archived record, its revisions, events, evidence and files. There is no unarchive action.

Workspace administrators can place or clear a decision's legal hold. It protects the record and its evidence from retention deletion, including after archive. It does not freeze editing or change whether the decision stands. Clearing it allows an eligible archived record to be purged on the next retention run, unless a workspace hold still protects it.

Supersede a decision with a successor

  1. Open the decided record and choose Supersede.
  2. Describe the new choice and explain why it replaces the old one. Complete its owner, areas, and review date or condition.
  3. Save a draft successor if the replacement needs review. The original decision continues to stand.
  4. When the successor is decided, it becomes the active decision and the original points to it.

If Acme Robotics later needs search capabilities that justify Elasticsearch, a successor to AR-041 would explain those new requirements. The earlier Postgres reasoning remains part of the history.

Reviews when linked decisions change

When a supersession, reversal or archiving applies, it opens a dependency review for the owner of each decided decision with a direct link to it. The inbox names the change, for example “AR-014 was superseded by AR-051”. Drafts and closed decisions do not receive these reviews.

Inbound depends on, affects and departs from links open reviews, following the impact map. An affects review is marked lower urgency; if several link types exist, the dependency or exception takes priority. Only one level is reviewed. Further reviews open when a person changes a dependent decision.

Each decision has at most one open dependency review. Further changes leave its original explanation in place. Reaffirming, revising or closing the decision resolves it once that change applies; a later linked change can open a new review.

Reminders before a review date

The daily review job tells a decision's owner directly 30 days and 7 days before its review date, on the date itself, and once on the day after it passes. Each notice names the decision by reference and title, its Type, the date, and the two choices: reaffirm it with a new date, or let it lapse. An Exception's notice also names the decision it departs from.

Owners who linked their Slack account get a Slack direct message. Everyone else gets email. Each reminder goes out once for each date: running the job again the same day sends nothing, and a reaffirmation with a new date starts the schedule again for that date once it applies. Each reminder has a window, counted from the day the daily job runs: the 30-day reminder goes out when the date is 28 to 30 days away, the 7-day reminder at 5 to 7 days, the reminder on the date only on that day, and the after-date reminder 1 to 3 days after it. The first run inside a window sends that reminder, so a missed run is caught up. A date the job first sees outside every window, for example one set 20 days ahead, waits for the next window. A reminder that reaches nobody, for example because Slack and email both failed, is tried again on the next run inside its window. A reminder is never sent twice: if a run stops before it can record the result, or Slack does not answer in time, that reminder is not retried. The next one in the schedule still goes out; after the last, the inbox item and the weekly digest still list the decision.

While a reaffirmation of the decision is proposed and waits for approval, the reminders pause and the inbox item stays, with a line saying who proposed it. They start again if the reaffirmation is withdrawn, and once its proposed review date has passed, since it can no longer be applied.

Turn these reminders off under Review dates and exception expiry in Settings → Your preferences. The inbox item and the weekly digest still list due reviews.

Check what changed and stay informed

Open Revisions on a decision to inspect earlier versions and compare changes. Open Event log for the sequence of recorded actions and who performed them.

In Settings → Your preferences, configure your digest and delivery preferences. Newly opened dependency reviews email the owner when Drafts, approvals and reviews is enabled. Linked Slack channels can receive notices and digests; restricted records appear there as a reference and link. Check the notification log for delivery attempts. Dates and times there and in the event log are in UTC, and every clock time says so.

Discard unsaved changes?

Your changes have not been saved. Stay to keep editing, or discard them and leave.