How to review a document
Review the linked brief when you need to agree a product choice. Product explanations help you understand the experience; the brief identifies what your feedback needs to resolve.
Read and respond
- Check the document title, revision date and status. A future proposal may be useful to discuss without selecting it for implementation.
- Read the proposed outcome and example. Follow the detail links only for the parts that affect your decision.
- Answer the questions under Decision requested. State which part you accept, want changed or want deferred. Explain a condition or concern where it changes the outcome.
- Send that response through the project's existing discussion channel with the page link and revision date. This site displays documents; it does not submit or authenticate an approval.
For example, a response can say: "Catalogue and publication, revision 5 October 2026: accept independent Offer publication. Before agreeing the minimum fields, include the missing wagering-basis case in the examples." That response accepts one point and leaves another open; it is not blanket approval of the document.
How an agreement is recorded
After an explicit decision, the document maintainer updates the owning project record, adds the outcome to the brief and updates affected product explanations. The outcome names the revision considered, decision date, confirmed decision maker or group, accepted scope and any remaining conditions. No participant is listed as an approver without a real recorded decision.
A changed proposal needs a visible revised date and a description of what changed. An earlier acceptance remains attached to the version and scope that were actually reviewed. Material additions do not inherit that acceptance.
Review states
| State | Meaning |
|---|---|
| For review | A concrete question is ready for feedback; no outcome has been recorded yet. |
| Changes requested | Feedback identifies changes needed before a decision. |
| Decision recorded | An explicit outcome, date and scope have been recorded. |
| Deferred | The decision or its implementation timing has been deliberately postponed; the record says which. |
| Superseded | A later document or decision replaces this one and is linked. |
Publishing a page is not approval. An agreed design is not proof of implementation or availability. Reviewing a project proposal is also different from an editor approving Casino content for publication.
Return to documents for agreement, or use work and progress to inspect what has already been produced.