Matter Pipelines

A live board for each matter, not a loose trail of notes

Matter Pipelines is the part of the platform that turns a file list into a working board. Each matter moves through defined stages, with clear owners, due dates, task flags and status markers that are visible to attorneys, paralegals and operations staff. That makes it easier to see which matters need drafting, which are waiting on documents, and which are ready for review or filing.

The setup suits firms that handle many active matters at once, where small delays can pile up quickly. In practice, it helps teams stop guessing where a file sits and start working from one shared view. Status changes can be structured around your own internal process, so the pipeline reflects the way your practice actually runs.

For firms in Sandton, Johannesburg, Pretoria, Cape Town, Durban and Bloemfontein, the value is consistency across offices and work groups. A matter opened in one branch follows the same visible route as a matter handled elsewhere, which keeps handovers cleaner and cuts down on repeated follow-up.

Pipeline structures that fit different practice sizes

The module works for smaller firms that want a neat, practical flow, and for larger practices that need more layers between intake, drafting, review and final action. A compact setup may use six to eight stages, while a fuller office may split matters into more detailed checkpoints for different practice areas. The point is not extra clutter, it is a clear route that matches the pace of the team.

Options can also be set per matter type. A litigation file may need steps for service, discovery, drafting and court dates, while a commercial matter may move through instruction, draft circulation, approval and execution. This helps the pipeline stay relevant to the work instead of forcing every file into the same pattern.

• Simple stage boards for smaller teams
• Detailed multi-step flows for busier departments
• Per-practice templates for repeat matter types
• Visible status rules for active, pending and completed work
• Priority flags for deadlines, reviews and urgent follow-up

Where the module earns its place in daily legal work

Matter Pipelines suits firms that need steadier control over active files without spreading the team across separate trackers. It is useful where there are many deadlines, changing instructions, document reviews and recurring status checks. The module works well for practices that need a dependable view of work in progress across property, commercial, litigation, family and debt-related matters.

It also fits firms that want stronger internal discipline around handovers. When one person updates the matter stage and another checks the next action, the file stays easier to manage. That matters in firms with multiple fee earners, rotating support staff or branch-based teams that need the same picture of progress.

In offices with high mail and file volumes, a structured pipeline can reduce the small errors that come from informal tracking. It gives the firm one place to see what is waiting, what is overdue and what has already been actioned. No drama, just a cleaner working line.

Setup details that matter before the pipeline goes live

Implementation begins with the way your team names stages, rules and matter types. The module can be configured around your current process map, including who may move a file forward, which steps need approval and what should happen when a due date is reached. Permissions can be set by role, so the right people can update files without opening every control to everyone.

For firms moving from spreadsheets or mixed folder systems, data migration needs careful attention. Matter names, responsible people, dates, notes, stage history and linked documents should be checked before import. If the firm also wants evidence handling in the same environment, the matter pipeline can sit alongside searchable review queues and document assembly tools, with security controls applied across both.

Power and network stability are part of the install planning in a real office, especially where hosted access and secure logins are used throughout the day. Where teams work from Sandton towers, shared offices or branch locations, onboarding should confirm connection access, user groups, device access and the level of admin control needed for each department.

Care, oversight and keeping the workflow tidy

A matter pipeline works best when it is kept clean and reviewed regularly. If stage names drift, or if old statuses are left in place after a process change, the board can become harder to trust. Periodic health checks help keep the rules current, make sure permissions still suit the team and confirm that matter labels are still being used in the same way across branches.

Security matters here too. Legal files carry sensitive information, so access controls, audit trails and careful user management are part of normal care. POPIA awareness matters in the background, especially where client data, evidence bundles and internal notes are stored in one place. If users leave the firm or change roles, their access should be adjusted promptly so the pipeline stays orderly.

Support also includes incident response where a stage rule, import or user setting needs attention. The aim is to keep matter movement visible and dependable, not to let the board turn into another hidden system that only one person understands.

What to confirm when ordering Matter Pipelines

Before the module is set up, the firm should confirm how matter stages need to work in practice. That includes the number of stages, the names used internally, the points where approval is required and the kind of alerts the team wants to see. It is also useful to confirm which office groups will use the same board and which need their own version.

For a legal office, the details matter more than broad promises. A pipeline for litigation may need different timing and visibility from one used for conveyancing or commercial work. If the firm wants the module tied to template builds, evidence imports or secure hosting setup, those pieces should be mapped at the same time so the handover is orderly.

• Number of stages needed for each matter type
• Names of roles that may move matters forward
• Deadline rules, overdue flags and escalation points
• Whether branch teams share one process or use variants
• Any document assembly, evidence or hosting links
• Required reporting fields for partner or ops review

When these points are clear, the pipeline becomes a practical working tool rather than an extra layer to manage. It gives the firm a straight view of active work and enough structure to keep matters moving with less noise.