Review
Decide what to keep, change or leave for later.
On this page
Choose what to do with the case
Read the requests, answers and evidence gaps first. Then choose a decision and write a short reason.
| Decision | What it does |
|---|---|
| Accept | Keep the finding as advisory: something to review, not an automatic failure rule. |
| Edit | Write your own expectation or choose checks the system can evaluate. |
| Reject | Do not include it in new tests. Keep the decision in history. |
| Defer | Leave the decision for later. This is not approval. |
Write a check you can explain
- Objective check: only recommend allowed restaurants, avoid excluded ones, or return the expected answer format.
- Approved policy: a rule you choose for one diner, such as including an option from a set, avoiding an option, or ordering two options when both appear.
- Advisory: keep an interesting finding for human judgement.
Choose from the supported checks. Writing a reason alone does not create an automatic rule, and accepting a finding is not a passed test.
If your save needs attention
If a newer decision was saved while you were reviewing, load it before submitting again. Your draft stays in the tab, including when you need to sign back in. After an uncertain save, use the same-request retry rather than starting a new decision.
Know when it is saved
After a confirmed save, TasteCase shows the decision, reason and receipt. A checksum is a fingerprint of the saved content; it helps identify the exact record you are reopening.