Midrand Deadline Tracking

What the Midrand team needed from their matter board

The client was a litigation support team in Midrand handling a steady flow of court deadlines, filing dates and prep tasks across several attorneys. Their old setup lived in shared folders, inbox searches and separate spreadsheets, which made it hard to see the next step for each matter.

The brief was practical rather than flashy: keep hearing dates visible, attach reminders to the right matter, and make it easier for support staff to spot work that was waiting on documents, signatures or court papers. They also wanted cleaner access control so the right people could see the right files without handing out broad folder access.

• Town focus: Midrand, with staff also working across Johannesburg nodes.
• User groups: attorneys, paralegals, legal secretaries and ops staff.
• Core need: one live view of deadlines, tasks and matter notes.
• Security need: tighter permissions, with POPIA in mind.

The pressure points that slowed daily prep

The main problem was not a lack of information, it was the shape of the information. Hearing dates sat in different places, follow-up tasks were written in message threads, and document versions were saved under names that changed from person to person.

They also had a few practical constraints. The team needed a system that worked for busy users who were not interested in extra clicks, and the setup had to fit a firm environment where matter notes, deadline changes and evidence files needed proper order. A few users worked between office and court, so the screen layout had to stay clear on smaller laptops too.

• Dates had to show in a shared matter pipeline.
• Preparation tasks needed linked reminders, not stand-alone notes.
• Evidence files had to be searchable without digging through drives.
• Access rights needed to follow role, not guesswork.

How we set up the deadline tracking workflow

We configured a deadline tracking structure around matter stages, court dates and prep actions. Each matter could carry its own date markers, notes, file links and task prompts, so the team did not have to rebuild the same checklist for every new file.

Templates were adjusted to suit common litigation patterns, including appearance notes, filing follow-ups and internal prep reminders. We also set up permissions so the support team could work quickly without exposing the full file set to everyone in the firm.

The main build covered these pieces:

• Matter pipeline stages with date-linked status updates.
• Template fields for hearing dates, filing dates and task owners.
• Searchable evidence queues for imported files and indexed records.
• Role-based permissions for support staff, attorneys and admins.
• Audit-friendly matter notes for later review.

Cleaning up the old records without losing context

Data migration took careful handling because the team had several sources of truth at once. We mapped existing spreadsheets, live folders and message-based notes into a structure that made sense inside the new matter board, and we kept the old context where it mattered.

That work included normalising matter names, matching deadlines to the right files and sorting evidence into review queues rather than dumping everything into one general folder. A few historic records needed manual checking, especially where date formats had been used inconsistently, but the process stayed controlled and plain.

• Imported deadline lists were matched against current matters.
• Old file labels were standardised for search and review.
• Duplicate notes were removed where they added no value.
• Key attachments were grouped by matter and stage.

The rollout across five working weeks

The project ran over five working weeks from planning to go-live support. The first week covered discovery, data mapping and the matter flow design. The second and third weeks focused on template builds, permissions and the deadline structure. The fourth week was used for user training and admin handover, and the fifth week focused on launch support and early fixes.

The team had enough time to test the layouts before live use, which mattered because legal staff tend to spot gaps quickly when a deadline board is not shaped to the way their week actually runs. We kept the build grounded in the firm’s own matter types rather than forcing a generic layout onto their work.

Timeline points:

• Week 1: discovery, mapping and planning.
• Weeks 2 to 3: configuration, templates and permissions.
• Week 4: user training and admin training.
• Week 5: go-live support and final adjustments.

What changed after the new board went live

After rollout, the team had a clearer view of deadlines tied to each matter, and preparation work was easier to assign. Support staff could see which files were waiting on documents, which hearing dates were next, and which matters needed a nudge before the pressure built.

The biggest improvement was not dramatic, it was steadier day-to-day control. Fewer items sat buried in inboxes, and the team spent less time checking where a date had been written. They also had a cleaner path for reviewing evidence and keeping matter notes together, which helped during busy court cycles.

• One shared view for hearing dates and prep tasks.
• Less duplication across spreadsheets and folder notes.
• Cleaner access control for staff roles.
• Better traceability on files, reminders and updates.

What we would keep for a similar rollout

For a similar Midrand or Johannesburg matter, we would keep the build close to the firm’s own workflow and avoid overcomplicating the first release. That means a clear matter board, tight permissions, sensible template fields and enough training for admins to keep the structure healthy after launch.

We would also keep the evidence review process linked to the matter itself, rather than separating it into a second system that creates more checking. In a legal team, the cleanest setup is usually the one that makes deadlines, notes and file handling sit together without extra hunting.

• Start with the real matter sequence already used by the team.
• Keep the deadline view readable at a glance.
• Use role-based access from the first configuration.
• Leave room for admin-led updates after go-live.