Process your queue without spending the whole day on it
01The problem #sec_d9e1d282
Two thousand four hundred requests are not processed one by one. They are not processed by checking everything either: a mass certification without review is exactly what recertification is supposed to replace.
The screen offers a middle ground. It consists of three steps.
02Reduce before deciding #sec_e6f69730
Filter first, then decide. A homogeneous batch is judged quickly; a heterogeneous batch is judged poorly.
Three tools, from the broadest to the most specific:
Status badges — IN PROGRESS, DELEGATED, ESCALATED, CONTESTED. Start with IN PROGRESS: this is what really awaits you.
The + Filter button — it adds a criterion. Active filters appear as chips under the bar, with a cross to remove them one by one, and Clear all to remove everything.
Search — to find a specific resource whose name you know.
A useful shortcut: the... menu of a line offers Filter on this resource. You start from a concrete case and the screen narrows around it.
03Decide in batches, when it's legitimate #sec_aaacb601
Check several lines: an action bar appears above the table.
2 selected · Certify as compliant (0) · 2 excluded — individual review ·
↑ Escalate · Clear all
Two things deserve attention.
The counter in parentheses is not that of your selection. Certify as compliant (0) means that zero of the selected lines can be certified in bulk.
Exclusions are announced, not silent. 2 excluded — individual review means that these lines require a one-by-one review — because the policy requires it, or because their status does not allow it. They are not ignored: they are sent back to the individual panel.
This is what makes mass certification acceptable: it is never applied to what required a review.
04Go fast without going fast everywhere #sec_4a62a40f
A method that works, in this order:
- Filter on a homogeneous batch — a policy, a type of resource, a user.
- Browse the criteria of three or four lines in the individual panel. You
understand the reason for the batch in a few minutes.
- Process the rest in bulk if the reason is clear and nothing is excluded.
- Isolate the exceptions and give them the time they deserve.
The time you save on obvious cases is the time you give back to difficult cases. That's the whole point of the maneuver.
05Line tools #sec_a176d8dc
Each line carries a few icons in the TOOLS column, then a... menu:
| Entry | What it does |
|---|---|
| Linked campaigns | Other campaigns affecting this resource |
| Filter on this resource | Reduces the queue to this resource |
| Timeline | The history of the resource: what was decided before, by whom |
| Consult | Ask for a third party's opinion without transferring the decision |
| Escalate | Move the case up — see the [next page](tuto-reviewer-blockages) |
Timeline is the most underestimated. Before revoking access, knowing that it has been maintained twice in a row with the same justification changes the judgment.
06Track your progress #sec_20e7a6ef
At the bottom of the screen: 2,471 requests · 2,452 awaiting decision, pagination, and the Lines selector (10 by default).
Increase it to 50 or 100 when processing a homogeneous batch: fewer pages to turn, and bulk selection applies to more lines at once.
07Ask RITA #sec_dabb6eb3
The Ask RITA button, at the bottom right, answers in natural language about your campaigns and your requests—how many you have left, what is overdue, what has already been decided on such a resource.
It is a guidance tool, not a decision-making one: it tells you where to look, you judge.
08To remember #sec_50f50073
Filter, understand the reason for a few cases, process the rest in bulk, isolate the exceptions. And read the announced exclusions: they name exactly what could not be dispatched.