These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Ghost Kitchen Aggregator
- Features
- Review and evidence
Review and evidence
Give an independent reviewer the exact order revision and supporting documents.
OverviewPending Review Decisions×
Ghost Kitchen Aggregator · Review and evidence
New
Pending Review Decisions
Action waits for the independent reviewer
| Source | Source revision | Decision | Reviewer | Evidence reference | |
|---|---|---|---|---|---|
| KO-80322 | 70 | Pending | ER-645 | ||
| KO-37191 | 690 | Pending | ER-667 | ||
| KO-81092 | 830 | Pending | ER-543 | ||
| KO-22558 | 470 | Pending | ER-754 | ||
| KO-48261 | 730 | Pending | ER-888 |
6 of 6 records
ER-645Review decisions · RD-70718
PendingSourceKO-80322
Source revision70
What you can do
Give an independent reviewer the exact order revision and supporting documents
An order is changed after its first evidence document was attached. The reviewer opens the selected revision, checks the document reference and verification, and decides whether that revision can proceed. A returned decision carries a reason to the owner. The work starts with selected order revision and reviewer. Those details let the next person open the same order or partner context instead of relying on a message thread. The team then checks document attachment, verification and decision reason. The important decision is whether the decision belongs to the same revision that will be routed.
The records here separate an operating fact from its review. An order can have a status, an observation can have an outcome, and a run can have an execution result. Each answers a different question. When the team sees a returned decision or unverified document, it keeps the decision reason and linked evidence beside the source order so a later reviewer can reconstruct what happened.
How the work is organized
- Identify the source. Start from selected order revision and reviewer and keep the related organization, partner and order visible.
- Check the decision. Review document attachment, verification and decision reason before the order moves to the next status or a result is used.
- Keep the trail. Record the decision reason and linked evidence with the same source identity when a question needs investigation.
What to agree during setup
Agree which documents support a revision and who verifies them. Independent Reviewer must use the current revision, evidence reference and decision reason. Keep the order owner separate from the person deciding the review. Returned work needs a reason that Order Operator can act on.
Give the Independent Reviewer an order revision and evidence reference. Walk through an accepted case and a returned decision or unverified document. Check that the people who prepare the record can see the returned work, while the independent reviewer can record the reason for a decision. Keep the rule tied to the selected order revision so an older decision is not mistaken for approval of a later change.
Check the handoff on an actual case
An order is changed after its first evidence document was attached. The reviewer opens the selected revision, checks the document reference and verification, and decides whether that revision can proceed. A returned decision carries a reason to the owner. Ask Order Operator to find the returned decision and its reason on the selected order revision. Independent Reviewer should be able to show the supporting document and verification state. A decision for the previous revision does not approve the current one.
Rehearse the case with a returned or uncertain outcome as well. The team should keep that result visible, assign an action with a due date where needed, and close the action with a resolution that points back to the order. The order trail should still show what happened before the correction.
What your team sees
- Pending Review Decisions — Find decisions still pending on a selected order revision.
- Open Follow Up Actions — See assigned actions that can hold up a review or correction.
Follow the work through
Follow the worked process and agree the implementation sequence before the first operating cycle.
What it keeps track of
Data model- Review decisions
- Independent revision-specific decisions on order evidence.
- Evidence documents
- Source evidence documents and verification metadata.
- Kitchen orders
- Parent order revisions routed through kitchen partners and pooled drivers.
- State history
- Immutable order status transition history.
- Follow up actions
- Open and completed actions required to resolve order exceptions.
Who uses it
Permissions- Independent Reviewer
- , Order Operator and Admin.
- The first named role owns the daily handoff; the others review the context or investigate exceptions.
Set up Ghost Kitchen Aggregator your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.