The Pending Disposition page shows batches of records that have matured under a retention policy and are waiting on a human decision (ISO/IEC 17025 §8.4). Batches are created automatically by the nightly job that an approved Retention Policy activates — they are never added by hand, which is why the page has no create button.
Found under: ISO 17025 → Records Lifecycle → Pending Disposition.
| Button | Action |
|---|---|
| Add — Create a new record | |
| Columns — Show/hide table columns | |
| Filters — Open/close the filter panel. A red dot indicates active filters | |
| Export CSV — Download table data as a CSV file | |
| Orientation — Toggle between portrait and landscape printing | |
| Print — Generate a PDF of the current view | |
| Help — Open the help dialog | |
| Search — Quick search through table data |
Clicking the icon on each row shows:
| Column | Description |
|---|---|
| Number | The batch number |
| Record Type · Action | What it holds and what will be done to it |
| Quarter | The quarter of maturity |
| Records | How many records it covers |
| Policy Version | Which policy version produced it |
| Status | Pending, Deferred or Authorized |
| Deferred Until | The review date, if it has been deferred |
View / Authorize on the row action menu opens the batch. There you see the cascade tree — which child records will follow — and a sample of the identifiers. All three actions are taken from that panel.
| Action | What it asks for | When it is allowed |
|---|---|---|
| Authorize | A reason and an explicit confirmation | On Pending, or on Authorized awaiting a second signature |
| Defer | A future date and a reason | On Pending only |
| Cancel | A reason | On Pending or Deferred |
Authorising executes immediately: the destruction or archival happens there and then, together with linked child records and photo files on disk. It is not scheduling, it is execution. That is why it asks for a reason and for confirmation that you have reviewed the cascade tree.
When a batch requires two signatures, the first authorisation leaves it as Authorized with an amber notice showing who signed first. The second authoriser must be a different person — the button is disabled for the first.