Skip to content

The Precedent handbook

Approve decisions

Each Area sets how many people must approve a decision, and whether its owner's approval counts. The approval that meets every Area's rule decides the draft.

Governance reviews start with three questions: who approved, when, and who asked for changes. Precedent answers them on the decision itself. In AR-131, the Acme Robotics inspection team proposes keeping raw images in a second region. One person approves and another requests changes with a note, so the draft waits; the decision page and the audit export show both.

How approving works

The rule lives on each Area, not on the workspace. A draft tagged with several Areas must meet every Area's rule, each by people with access to that Area. One person's approval counts for every Area they have access to. A draft that supersedes or changes another decision also needs the approvals of that decision's Areas.

Anyone with Member, Maintainer or Area administrator access to an Area can approve there, and so can a workspace administrator. Viewers cannot. The last approval a draft needs decides it: it becomes Decided with no further click, and the people who approved are recorded on it.

An approval is of the draft as the person read it. Editing the draft, changing its Areas or links, or staging a change to another decision dismisses the approvals given so far. They stay on the page, marked as no longer counting, and people approve again.

A change to a decided decision (a revision, a reaffirmation, a reversal, a supersession or archiving) also needs its Areas' approvals. A revision needs the Areas the decision has before and after it, and a supersession needs the Areas of both decisions. The person who makes the change is treated as the person who asked for approval, and their own approval is recorded in each Area where it counts. For a reaffirmation, the owner's approval and that of the person who reaffirms count in every Area they have access to, even where the owner's own approval does not count for other changes. Where that meets every Area's rule, and for an Exception the rule below, the change applies at once. Otherwise it is a proposed change: the decision stays Decided and its text in force does not change until the change is approved.

A decision has at most one proposed change at a time: while it waits, another revision, reaffirmation, reversal, supersession or archiving of it is refused until that one is approved or withdrawn. A draft that supersedes or changes the decision can still be decided, and that closes the proposed change as out of date. The person who proposed it, the decision's owner, an Area administrator of one of the Areas it needs or a workspace administrator can withdraw it with Withdraw proposed change. Anyone but the person who proposed it gives a reason. The person who proposed a revision can change it with Edit proposed revision and Save proposed revision: approvals given before the edit no longer count, and requests for changes stay open. 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 proposed change shows on the decision's page above the tabs, headed by its kind, for example Proposed reversal, with the same approvals table. A proposed revision adds Compare the changes, which shows the text in force and the proposed text of each field it changes. People who can approve it choose Approve or Request changes there. An approval that would reverse, supersede or archive the decision asks you to confirm first.

Ask for approval

Nobody else can approve until the draft is ready. The owner, an Area administrator of one of its Areas or a workspace administrator chooses Ask for approval, and the draft then shows Awaiting approval. Everyone who can approve sees it in their inbox.

Where the owner's own approval counts, the owner chooses Approve instead, which asks and records their approval in one step. The default rule needs one approval and counts the owner's, so under it the owner's Approve decides the draft at once.

  1. Complete the checklist: the title, summary, owner, at least one Area, a review date or condition, and anything its Type requires.
  2. Run the conflict check and acknowledge any unresolved conflicts. The person who asks does this; the people who approve afterwards do not need to.
  3. Choose Approve or Ask for approval. The table above the tabs shows each Area, what it needs and who has approved.

Each Area's rule is copied when approval is asked, so a later change to an Area's settings does not change what a waiting draft needs. Choose Back to draft to close the request; the approvals given so far no longer count.

Who is told

Asking for approval sends nobody an email or a direct message. Where an Area posts new drafts to its Slack channel, the draft's post there says who asked and what each Area still needs, and it changes to Decided, naming everyone whose approval counted, when the draft is decided. A channel that already has the draft's post gets it rewritten, not a second message.

While approval is asked, the person who may ask can choose Nudge someone and tick the people who can still approve. Each gets one message that the draft needs their approval. A person can be nudged about a request once a day; a nudge gives them no extra right and asks nothing more of them.

WhenWho is told
Someone nudges a personThat person.
Someone requests changesThe owner, with the note, unless the owner made the request.
The draft becomes DecidedThe owner, with who approved, unless their own approval decided it.
Someone else changes the draft while a request for changes is openThe person who requested changes, once per request.

Each goes by Slack direct message when the person linked Slack, and by email otherwise, and only to someone who can still see the draft. Turn them off with Drafts, approvals and reviews in Settings → Your preferences. Nobody is told about each approval along the way; the inbox and the weekly digest show what is waiting.

People are told about a proposed change to a decided decision in the same way, with the same setting. Where an Area posts new drafts to its Slack channel, the decision's post there says which change is proposed, by whom and what each Area still needs. When the change is approved, withdrawn or out of date, the post shows the decision as it then stands. Whoever may withdraw it can also choose Nudge someone.

WhenWho is told
Someone other than the owner proposes a changeThe owner.
Someone requests changes to itThe person who proposed it, with the note, unless they made the request.
The person who proposed a revision edits it while a request for changes is openThe person who requested changes, once per request.
It is approvedThe person who proposed it and the owner, except whoever gave the approval that applied it.
It goes out of dateThe person who proposed it, with what caused it, unless their own change did.
Someone else withdraws itThe person who proposed it, with the reason.

Request changes

Anyone who can approve, other than the owner, can choose Request changes and write a note saying what needs to change. The note is required, and it is quoted on the decision page above the approvals table.

A request for changes blocks the draft, across edits, until its author approves or chooses Withdraw request. It also stops blocking if its author loses access to the draft's Areas. An Area administrator of one of the draft's Areas, or a workspace administrator, can choose Dismiss request and give a reason, which is recorded in the event log.

Set an Area's rule

SettingEffect
Approvals neededHow many people must approve, from 1 to 10. The default is 1.
The owner's own approval countsOn by default. Turn it off to require approval from someone other than the decision's owner; the person who asked for approval does not count either.

An Area administrator of that Area or a workspace administrator changes the rule on the Area's form. Settings → Approvals lists every Area's rule and how many people have access to it, with a link to each Area's form.

When fewer people have access to an Area than its rule needs, the Area form warns you and Settings shows Cannot be met. The rule can still be saved, but asking for approval on a draft in that Area is refused until more people have access, the number is lowered, or the owner's approval counts.

Exceptions

An Exception always needs at least one approval from someone other than its owner, the person who asked for approval and the person who last changed the draft, whatever its Areas' rules say. An Area's rule can ask for more. A proposed change to a decided Exception needs one from someone other than its owner and the person who proposed it. A draft that supersedes a decided Exception, or stages a change to one, needs one too, from someone other than the draft's owner, the Exception's owner, the person who asked for approval and the person who last changed the draft. A one-person workspace cannot decide an Exception until a second person has access. See Record an exception.

See The seven Types for what each Type needs before it can be approved.

From an assistant or Slack

With the Decide permission and Assistants can decide turned on, an assistant can approve a draft with approve_decision, ask for approval with ask_for_approval, and request changes with request_changes. Each waits for you to accept a prompt in the assistant's app, which names each Area and what it still needs. get_decision returns the approval state in its approvals field, and confirmBlockers lists what the checklist still needs.

Where People can approve and reaffirm from Slack is on, a draft's post in an Area's channel carries an Approve button. Only people who could approve in Precedent can, and each approval is accepted in Slack before it is recorded. Withdrawing an approval or a request, dismissing a request and choosing Back to draft happen on the decision page.

EventRecorded when
Approval askedSomeone asks for approval, with each Area and its rule.
ApprovedA person approves the draft as they read it.
DecidedThe last approval the draft needs is given. The draft becomes Decided, with whose approvals counted.
Changes requestedA person requests changes, with their note.
Approval withdrawnA person withdraws their approval or their request for changes.
Request dismissedAn administrator dismisses a request for changes, with their reason.
Moved back to draftSomeone chooses Back to draft. The approvals given so far no longer count.
Request closedThe owner changed, which closes the request for approval.

The Decided entry records whose approvals counted. Decisions from before approvals moved to Areas keep their earlier entries in the event log: each earlier request, approval, objection and withdrawn request ends “(before approvals moved to Areas)”, and their Decided entry keeps the wording it was recorded with. The audit export keeps every stored event type.

Discard unsaved changes?

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