The brief from a busy estates team in Stellenbosch
The team handled a steady flow of estate matters with repeating letters, stage-based documents and progress notes that had to stay aligned across attorneys, paralegals and support staff. Files were moving through shared folders, message threads and local spreadsheets, which made it harder to see where each matter sat and which version of a pack was current.
The brief was practical. They wanted cleaner document assembly, a clearer matter pipeline and a way to hold evidence and correspondence in one searchable place without adding clutter. The roll-out also had to suit a firm working under real deadlines, with users in Stellenbosch and related offices needing a layout that felt familiar from day one.
- Recurring estate packs had to be built from approved templates.
- Progress notes had to sit against the correct matter stage.
- Search had to work across documents, notes and evidence items.
- Access had to be controlled for different roles across the team.
What the file room looked like before the rollout
Before the setup, the main pain point was version drift. One person would update a draft, another would save a copy into a different folder, and a third would add notes in a separate register. That made it harder to follow the chain of work, especially where an estate file needed a clean paper trail and a record of who touched what.
The team also needed a stronger structure for evidence and scanned material. Some matters had family correspondence, asset schedules and signed documents spread across multiple storage locations. That created delays when a file had to be checked, handed over or reviewed during a busy week. The storage system had to support orderly retrieval, not just bulk holding.
- Shared drives were holding too many loose copies.
- Stage notes were not tied to one clean workflow.
- Evidence and scanned packs were hard to sort by matter.
- Role-based access had to be clearer for internal control.
The setup we put in place over four weeks
The rollout ran over four weeks and was split into planning, configuration, migration, training and go live support. In week one we mapped the existing matter flow and listed the estate documents used most often. In week two we built the template structure, stage gates and naming rules. Week three covered data migration, permissions and evidence imports. Week four focused on user training, admin training and live checks.
The build centred on three parts: template assembly, matter management and searchable review queues. Recurring packs were turned into structured templates with fields for party details, dates, property notes and matter references. Matter stages were configured to reflect the team’s own sequence, so each file showed where it sat without guesswork. Evidence items could then be linked back to the right file and reviewed from one place.
- Template Builds for recurring estate packs and letters.
- Workflow Configuration for stage based matter movement.
- Permissions Setup for attorney, paralegal and admin roles.
- Evidence Imports for scanned packs and supporting records.
- Secure Hosting Setup with controlled access and audit-friendly handling.
Keeping deadlines visible without cluttering the workflow
Deadlines matter in estate administration, especially when multiple documents are waiting on sign-off, internal review or external input. We set reminders and task points around the matters rather than leaving dates hidden in message chains. That gave the team a steadier view of what needed attention, while still keeping the screen uncluttered.
The system also made it easier to separate active work from archived records. Current matters stayed in the review queue, while older files could be found through search without sitting in the way of daily work. This is useful when a firm has to answer a question about a document trail or pull a note from a matter that was opened months earlier.
- Stages were visible at a glance for each matter.
- Deadline markers sat inside the workflow, not in side notes.
- Search could find names, references and uploaded records.
- Archived material stayed available without crowding active files.
Security, access and POPIA-aware handling
Because the platform handled client records and estate material, access control was set up with care. We configured permissions so that users only saw the parts of the system they needed for their role. That matters when a team is dealing with personal information, attachments and working notes that should not be open to everyone in the office.
We also reviewed how files were stored, named and imported so the structure supported safer handling rather than loose duplication. POPIA was treated as a general compliance consideration throughout the build, with secure hosting setup and sensible access boundaries forming part of the rollout. No part of the configuration relied on casual sharing or open folders.
- Role based access reduced unnecessary file visibility.
- Secure hosting setup supported controlled document storage.
- Audit friendly structure helped track who touched each file.
- Import rules kept evidence and notes in the right place.
What changed once the team was live
Once the system was in use, the biggest change was order. Recurring packs no longer had to be rebuilt from loose drafts, and progress notes were easier to tie to the correct stage. That saved time across the office because people spent less of the day checking where a file had gone or whether a document had the latest wording.
The team could also hand matters between users with less friction. A matter opened in one place, moved through the agreed stages, and kept its notes, evidence and templates in the same flow. For a Stellenbosch practice handling estates work with moving parts, that brought a calmer rhythm to daily admin and less duplication in the back office.
- Cleaner matter history for each estate file.
- Less duplication of draft packs and notes.
- Faster internal handovers between users.
- Better visibility when evidence had to be reviewed.
What we would keep on a similar estate rollout
We would use the same sequence again on a similar project: map the live process first, then build the templates around the way the firm already works. That keeps the system practical for the people who use it every day. It also helps when a firm has both experienced staff and newer users who need the workflow to be obvious from the start.
We would also keep the migration staged, rather than trying to move everything at once. Starting with active matters, current templates and essential evidence makes the go live cleaner and easier to manage. After that, extra files, historic material and less urgent records can be organised into the structure without crowding the main rollout.
- Start with active matters and the most used templates.
- Keep permissions simple until the team settles in.
- Import evidence in stages, not all at once.
- Leave room for template tweaks after live use.
Key facts
| Project type | Estates workflow rollout for a law firm team |
|---|---|
| Town | Stellenbosch, Western Cape |
| Timeline | 4 weeks from mapping to go live support |
| Core modules | Templates, matter pipelines, review queues, permissions |
| Data work | Data migration and evidence imports |
| Security focus | Controlled access and secure hosting setup |
