Which requests need review?
Group current request statuses by organization and owner, then inspect the revision of any case waiting on a decision.
Reports help the team identify decisions still open and explain recorded stock effects. Start with the exact organization, item and location before comparing quantities across records.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 30 | ||
| Review | 8 | 27% | |
| Approved | 3 | 38% | |
| Executed | 1 | 33% |
Sample totals per stage
Group current request statuses by organization and owner, then inspect the revision of any case waiting on a decision.
Read target units by season and size-color alongside the parent request and required date.
Examine release state and expiry, then follow active reservations tied to a restricted lot.
Use posted signed movements and their request references; reservations describe claims rather than posted quantity.
Read failed and review-needed receipt outcomes with their effect references and reasons.
Group requests by organization and status to see work awaiting a decision.
Compare target units and required dates for each season and size-color label.
List lot release state and expiry beside the item and owner reference.
Sum claimed quantity by location, item and reservation state.
Show signed quantity, posting time, item, location, lot and source request.
Show each source revision, reviewer, decision, reason and decision time.
Show result state and failure reason for each operation key and request.
List attachment type, visibility, upload time and uploader under each request.
Start free, then use Proto to change fields, steps and approvals before your team goes live.