Review queues work best when the first pass is strict
A review queue is not just a holding pen for files. It works better when each item enters with a clear label, a matter reference and the reason it needs attention, so the right person sees the right item first.
In a South African firm, that can mean separating urgent court papers from routine correspondence, or splitting incoming evidence by matter, document type and deadline. If the first pass is loose, people spend time sorting what should already be sorted, and the queue starts to feel like a shared inbox with a fancier name.
Set assignment rules that match the real office rhythm
Queue assignment should follow the way the firm actually moves work. A senior attorney may need final review on pleadings and settlement correspondence, while a paralegal handles initial checks on bundles, returns and proof of service. That kind of structure keeps work moving without forcing everyone into the same path.
- Use matter type to route files to the correct team.
- Use deadlines to push urgent items to the top.
- Use document class to separate drafts, signed copies and support material.
- Use status flags so nobody reviews the same item twice.
When those rules are visible, staff do not have to guess where a file belongs. The queue becomes a working list, not a puzzle.
Keep evidence review tidy, searchable and easy to audit
E-discovery work needs more order than a normal document tray. Evidence items should be searchable by matter, date, sender, file type and issue tag, with notes that explain why a document was kept, rejected or sent back for more detail.
That matters when a team in Sandton is working on a multi-party dispute and documents arrive from different offices, message chains and scanned bundles. If the review queue holds those items in a clean sequence, it is easier to track what has been seen and what still needs checking. The queue also supports a better audit trail, which is useful when internal teams need to show how a document moved through review.
POPIA concerns do not disappear just because a file sits in a queue. Access levels, logging and controlled views help limit exposure, especially where personal information appears in witness statements, medical notes or identity documents.
Make deadlines visible without turning the queue into noise
Deadlines should shape the queue, but not dominate every screen. A good setup shows due dates, filing dates and internal review dates in a way that helps the team plan the day. If every item screams for attention, nothing gets proper attention.
Queue design works well when urgent items are grouped by court date, matter stage or client instruction. For example, an urgent motion in Johannesburg can sit above general correspondence for a Bloemfontein matter, but only if the queue makes that priority plain. The point is not speed for its own sake, it is calm control over what must be done first.
- Display due dates next to the document title.
- Show who last handled the item.
- Keep priority markers limited to a few clear levels.
- Separate incoming work from items waiting for approval.
A Pretoria team will use the queue differently from a Cape Town team
One firm may have a central review team in Sandton, while another splits review between branches in Pretoria, Cape Town and Durban. Review queues need to handle those differences without extra admin every morning. If a matter moves from one office to another, the queue should carry the same labels, status notes and permissions with it.
In practice, that means a reviewer in Rosebank can see a matter’s full path, while a team in Centurion only sees the items assigned to them. A queue setup that respects office structure helps reduce misrouting and keeps local teams focused on their own workload. It also avoids the awkward situation where someone in the wrong office has to chase context across folders and messages.
Build handover rules for the next person in line
Review queues often fail at the handover point. One person checks a document, adds a note, and moves on, but the next person cannot see what changed or what still needs attention. That breaks the flow and leads to duplicate checking.
Good handover rules record the reviewer, the action taken and the next step. A simple note like “needs signature page” or “ready for matter update” saves time later, especially when a file is reassigned after leave, sick time or an urgent court matter. It also gives support staff and operations teams a cleaner view of where each item sits in the process.
At Law Machines, queue setup sits alongside template builds, workflow configuration and permissions setup, so the review path matches the way the firm already works. That makes the system less fragile when staff change roles or take on new matters.
A working queue leaves less room for drift
The strongest review queues are not packed with features. They are clear, repeatable and built around the work that lands on a legal team every day. If a queue shows matter type, review stage, deadline and owner, the firm can handle more documents without losing track of what needs attention.
For firms in Johannesburg, Pretoria, Cape Town, Durban and Bloemfontein, that sort of setup is useful where document volume moves up and down through the month. A steady queue keeps the work visible, reduces back-and-forth and gives the firm cleaner control over review and assignment. It is a practical way to keep matter movement under control without adding extra admin to every file.
