Durban Evidence Review

A disputes team in Durban with too much paper and not enough order

The matter started with a familiar problem for a busy litigation group in Durban. Records had been scanned from paper files, but the digital copies were spread across shared folders, loose naming styles and inconsistent file dates. When affidavits, notices and supporting records had to be checked together, the team spent too long hunting for the right version and too much time confirming whether a scan was complete.

The brief was to build a review flow that made evidence easier to sort, tag and search. The team wanted a practical setup for disputes work, not a generic storage area. They needed matter based queues, a clearer view of document status and a structure that would hold up when several people were working on the same file at once.

• Client type: disputes and litigation team
• Town: Durban
• Main need: searchable evidence review across active matters
• Core problem: scanned records were stored, but not organised for daily use

What made the review workflow difficult to run

The team worked across multiple matters with records arriving in batches from different sources. Some scans were complete, some had blank pages or poor image quality, and some were saved in folders that gave little clue about the matter they belonged to. That made it hard for attorneys and paralegals to check evidence in a steady way, especially when deadlines were close and several matters were moving at once.

There were also practical constraints around security and access. Not every user needed the same view. Senior staff had to see the full record, while support staff only needed the sections tied to their tasks. The team also needed a structure that would support POPIA aware handling of personal information, with controlled access and a record of who could see what.

• Mixed scan quality across older records and new uploads
• Folder names that did not match matter references
• Different permission levels for staff groups
• Need for secure handling of personal information

The queues, tags and controls we set up

We configured a review flow with searchable queues for each matter stage. Incoming evidence could be assigned to a matter, tagged by document type and pushed into a queue for review. That let the team separate affidavits, bundles, correspondence and annexures without building a complicated process that only one person understood.

Template fields were added for matter number, opposing party, date received, source of scan and review status. We also set up permissions so the right users could add, edit or archive documents without exposing the full evidence set to everyone on the team. Where scanned records were poor, the workflow flagged them for re-scan or manual checking. It was not fancy work, just clean structure that made daily use easier.

• Matter level queues for sorting and checking records
• Tags for document type, date and review status
• Role based permissions for staff and supervisors
• Flags for incomplete scans and unreadable pages

How the rollout ran over six weeks

The project ran over six weeks. The first week covered planning, matter grouping and a review of how the team named and stored files. The next two weeks were used for evidence imports and the setup of the review queues. After that we tuned the template fields, permissions and the layout used for checking incoming scans. The final two weeks covered user training, admin handover and live testing with active matters.

The work had to fit around real disputes deadlines, so the process was staged. That kept the team working while the new structure was being introduced. A few older files needed cleanup where page order was not right and some scans had been saved twice under slightly different names, so we corrected those before the live review stage. It was steady work, but it saved time later.

• Week 1: planning and file structure review
• Weeks 2 and 3: imports, queue setup and tagging rules
• Weeks 4 and 5: permissions, layout tuning and training
• Week 6: live testing and admin handover

What changed once the records were searchable

After the rollout, the team could search evidence by matter, document type and review status instead of opening broad shared folders and guessing where something had landed. That made it easier to prepare for deadlines, draft from the right set of records and check whether an annexure or supporting scan had already been reviewed. The flow also gave the office a clearer audit trail for who handled each item.

The biggest gain was not only speed, but calmer work. People knew where to look and what still needed attention. During busier stretches the queue view helped supervisors spot stuck items before they turned into late night scrambles. The system did not remove the pressure of disputes work, but it reduced the noise around the files. That matters more than many teams expect.

• Cleaner search across scanned records
• Better visibility on review status
• Less time lost to duplicate file checks
• Stronger control around document access

What we would keep on a similar Durban matter

On a similar project, we would repeat the same order of work: map the file naming first, set matter based queues next and only then bring in the bulk of the records. That sequence keeps the migration tidy and avoids building a system around messy source data. We would also keep the permissions model narrow from the start, because review work often expands faster than teams expect.

For Durban teams handling scanned bundles and active disputes, the useful part is not only the storage. It is the path from intake to review to sign off, with enough control to keep personal information protected and enough clarity for the team to use it every day. That is where the value showed up here, and it showed up quickly enough for the office to feel the difference in ordinary work.

• Set the file structure before bulk imports
• Keep access levels tight from the start
• Build review queues around real matter stages
• Leave space for rescans and corrections

Key facts from the Durban evidence review

The work centred on disputes evidence, scanned record cleanup and searchable review queues for a Durban team. It covered imports, tagging, permissions and live use on active matters. The setup was built for legal staff who needed clear access to records without long folder hunts or mixed naming systems.

It also gave the office a steadier way to manage documents under everyday pressure. That matters in litigation, where a missing annexure or a misfiled scan can slow the whole file down. With the new structure in place, the team had a better handle on what was in the system and what still needed attention.