Centurion Intake Automation

A busy Centurion office needed cleaner matter opening

The client was a mid-sized Centurion practice handling commercial, litigation and general advisory work for corporate and private clients. New instructions were arriving through our contact form, phone notes and scanned forms, which meant the first hour of a matter often involved tidying up incomplete details before anyone could draft, diarise or allocate work.

The brief was direct. Reduce back-and-forth at intake, standardise the information captured at the start, and make sure each matter entered the firm’s workflow with the right documents, tasks and people attached. The partners wanted something practical for day-to-day use, not a system that looked neat in a demo but broke down when matters piled up mid-month.

One concern sat above the rest: the firm needed a structure that could hold sensitive client data properly. That meant controlled access, cleaner audit trails and a storage approach that fitted common POPIA duties without turning the admin team into security specialists.

What the intake flow had to do in real use

The new intake process had to work for different matter types without asking staff to build every file from scratch. It also had to keep the front office, legal team and operations team aligned on the same record. The firm wanted a system that could gather core data once, then push it into matter records, document templates and workflow stages with less manual typing.

• Capture client name, contact details and matter category in a structured form
• Trigger the right template set for letters, mandates and opening documents
• Route the matter to the right team member by practice area
• Track deadlines, follow-up actions and status changes from one queue
• Keep permissions tight so staff only saw what they needed

The team also asked for a calmer approach to evidence and attachment handling. Large bundles, scans and correspondence were getting lost in message threads, and some files carried multiple versions with no clear owner. That was slowing prep work and creating avoidable checking later on.

How the intake system was put together

We supplied implementation planning, template builds, workflow configuration and permissions setup, then layered in evidence imports and secure hosting setup. The intake form was designed around the questions the firm actually asks at first contact, with field rules that reduced incomplete submissions and a clear split between mandatory and optional data.

From there, the matter pipeline was mapped in stages the team recognised immediately: new instruction, review, opening, active work, waiting on client, and closed. Each stage carried visible tasks, responsible users and reminders so the file did not rely on memory or inbox searching. Document assembly was linked to the intake record, which meant opening packs could draw from consistent details rather than being rebuilt line by line.

Security Engineer Sibusiso Tau reviewed access groups and sharing rules with the office leads. That included limiting who could export evidence, who could edit opening data and which roles could see matter notes. For the support team, the structure reduced the risk of old forms drifting around in shared folders, while still keeping the workflow easy enough for daily use.

• Structured intake fields for contact, matter type and urgency
• Template logic for opening packs and routine correspondence
• Permission tiers for attorneys, paralegals and admin staff
• Searchable review queues for evidence and attachments
• Hosting and access controls aligned to common confidentiality duties

A five week rollout with staged handover

The project ran over five weeks in a staged sequence so the firm could keep working while the new intake process was shaped around live matters. Week one covered discovery, field mapping and the opening file structure. Week two focused on template builds and the first workflow draft. Week three handled permissions, matter queues and test records.

Week four was used for user training, admin training and evidence import checks. Week five covered go-live support, issue handling and a health check across the first matters opened through the new process. Ayesha Sekgobela led onboarding discussions with the office team, while Naledi Hadebe and Johan Ebrahim handled process fit and product configuration.

The handover did not try to turn every habit upside down in one step. Existing intake habits were folded into the new flow where they made sense, and only the weak points were changed first. That kept the team moving while the new structure settled in across the office.

What changed after the first matters moved through

Once the intake forms were in use, the biggest shift was the drop in administrative chasing. The front office could capture the core matter details once, and the rest of the team worked from a cleaner record. The legal staff no longer had to piece together opening information from scattered message threads or repeat the same questions to different people.

Document assembly became steadier because the templates drew from structured data rather than free-text notes. Matter owners had a clearer view of what still needed attention, and evidence was easier to find when a file needed review. The searchable queues were especially useful for matters with several attachments, since staff could sort by matter, item type or stage instead of hunting through shared folders.

The firm also reported better control over permissions and a more orderly handoff between intake and active work. That mattered in a practice where multiple people may touch the same file, but not all of them need the same level of access. It also made client data handling feel less exposed, which suited the firm’s internal compliance discipline.

• Less manual retyping from messages and scanned notes
• Cleaner matter opening records across practice areas
• More predictable document assembly from standard fields
• Better visibility on deadlines and follow-up steps
• Stronger control over access to sensitive matter material

What we would carry into the next Centurion intake project

For a similar practice, we would keep the intake scope tight at the start and build around the documents and matter types that are opened most often. That avoids overbuilding a form that looks complete but is awkward for the staff who use it every morning. We would also leave room for a second pass on permissions after the first live week, because real filing habits often show up only once the team has used the system under pressure.

In this project, the best results came from pairing document automation with matter management from the start instead of treating them as separate workstreams. The intake form fed the opening pack, the opening pack fed the pipeline, and the pipeline kept the deadline work visible. That order mattered more than any single feature on its own.

Centurion staff were already working hard, so the system had to fit the pace of a real practice rather than asking the practice to adapt to software habits. That is the part we would keep intact on the next intake rollout: fewer moving pieces, cleaner handovers and a setup that makes the first step of every matter easier to handle.