Workflow stack · Matter readiness

Matter files ready before the deadline.

Scellus reads every new matter against the checklist, verifies key data against source records, chases missing documents early, and hands the fee earner a clean review queue before filing pressure arrives.

Included
Checklist match
Included
SSM + LHDN checks
Included
Audit log per matter

Built for Malaysian law firms running conveyancing, litigation, corporate, and family matters across a DMS, shared inboxes, WhatsApp, and practice-management records.

Readiness readout · checklist verified

Where matter prep breaks today

The deadline arrived. The file was not ready.

  1. The filing-day gap.

    The file is pulled on the morning it is due. The consent letter is missing, the client is not answering, and the deadline starts moving.

  2. Names that do not match.

    The intake form, identity document, SSM search, and client record carry small differences nobody catches until lodgement.

  3. Documents chased too late.

    IDs, addresses, and signed forms are requested the night before, often by whoever last spoke to the client.

  4. SRO worked under pressure.

    The fee figure is calculated by hand when the file is already urgent. A rounding slip becomes a billing conversation later.

  5. Review means investigation.

    The fee earner is asked to sign off, then has to hunt through email, WhatsApp, and the DMS to understand the exception.

  6. No clean audit trail.

    When a partner asks what was checked, chased, and signed off, the answer is reconstructed from memory.

Operating truth

A stored file is not a ready file.

Readiness is the moment every required document is present, every key field has a source, every exception has an owner, and the fee earner reviews judgement rather than doing the hunt.

The stack

Six blocks. One ready matter file.

Matter readiness runs the full public block sequence. It starts with matter-file collection, reads and verifies the fields that matter, chases gaps before the deadline, pauses for fee-earner judgement, and delivers a readiness report with the audit trail attached.

  1. 01
    Collect
  2. 02
    Read
  3. 03
    Verify
  4. 04
    Chase
  5. 05
    Review
  6. 06
    Deliver

Blocks used

Each block has a source, an output, and an owner.

01

Collect

Pulls the intake form, IDs, supporting documents, emails, portal uploads, and DMS records into one matter queue.

Your team Opening the matter and naming the matter type.
02

Read

Extracts names, identity numbers, company numbers, addresses, deadlines, amounts, and matter-specific checklist fields.

Your team Confirming unusual formats and handwritten records.
03

Verify

Checks key fields against SSM, LHDN where relevant, the client master, and the firm's matter requirements.

Your team Setting confidence thresholds and source priority.
04

Chase

Requests missing IDs, signed forms, address proof, and supporting documents while there is still time to act.

Your team Approving chase wording and escalation rules.
05

Review

Holds mismatches, incomplete files, SRO questions, and judgement calls for fee-earner sign-off with the source attached.

Your team Making the legal judgement and sign-off call.
06

Deliver

Hands over the readiness report, exception queue, SISPAA-ready checklist, SRO working, and matter audit log.

Your team Filing, client delivery, and final matter ownership.

What you receive

Not a folder. A readiness record.

The output is not a claim that the file is probably complete. It is the evidence that the matter was checked, chased, reviewed, and ready before pressure arrived.

  • A daily matter-readiness report showing each file due, what is complete, what is missing, and who owns the next action.

  • A live exception list for missing documents, data mismatches, incomplete client details, and unclear SRO or filing items.

  • A SISPAA-ready checklist per matter type, checked against the documents actually on file, not against memory.

  • A reviewer queue that gives the fee earner the discrepancy, source record, document, and recommended next step in one place.

  • SRO working and supporting fields prepared before sign-off, so the fee figure is reviewed calmly rather than recreated under pressure.

  • An audit log linking matter, field, source, missing item, chase, sign-off, and timestamp for partner review or compliance checks.

The transition

What changes when Scellus runs matter readiness.

Missing documents

Today

The gap is found when the file is pulled for filing, with hours to spare and the client not answering.

We handle

We read each matter against the checklist when it opens and chase missing items days before the deadline.

Your team

Approves the request wording and escalation path.

Source verification

Today

Names, IDs, company numbers, and addresses are checked by eye, then a mismatch appears at lodgement.

We handle

We cross-check fields against SSM, LHDN where relevant, and your client record, then attach the source to every exception.

Your team

Decides how to resolve genuine discrepancies.

Fee-earner sign-off

Today

Review means opening emails, folders, and message threads to understand what the clerk is asking.

We handle

We hold unclear cases in one reviewer queue with the record, discrepancy, checklist item, and working shown.

Your team

Signs off exceptions and legal judgement calls.

Division of labour

We run the readiness queue. You keep legal judgement.

Scellus handles Your team owns

Collect matter documents from DMS, email, forms, portals, and upload links

Open the matter and name the matter type

Read fields and match the file against the matter checklist

Confirm matter-specific requirements

Verify fields against source records and flag mismatches

Set source priority and confidence thresholds

Chase missing documents before the deadline

Approve wording and escalation rules

Prepare the reviewer queue, readiness report, and SRO working

Make fee-earner sign-off decisions

Maintain the audit log and monthly operating report

Own filing, client advice, and matter responsibility

Compliance and data

Client records stay traceable while they move.

Matter data, including client names, identity numbers, addresses, company records, filing details, and source documents, stays under PDPA 2010 and the 2024 Amendment.

Bar Council confidentiality and retention obligations shape the permission model, reviewer queue, source checks, and audit log. Data residency is confirmed before processing.

Traceability is built into the deliverable: matter, source field, record checked, missing item, chase status, fee-earner decision, and timestamp.

Data handling · Security and governance

Integrations

We meet your matter stack where it already is.

Documents and workspace

  • iManage, NetDocuments, and in-house DMS
  • Microsoft 365, SharePoint, OneDrive
  • Google Workspace and Shared Drives
  • Matter folders and shared inboxes

Client communication

  • WhatsApp Business API for document chasing
  • Email ingest from the matter inbox
  • Web intake and onboarding forms
  • Secure client upload links

Reference checks

  • SSM e-Search for company and director records
  • LHDN checks where relevant
  • Client master and conflict records
  • Land office and filing requirements

Operating cadence

Read, verify, chase, then review.

01

Daily

New file intake and checklist match

We pull new matter files, read the required fields, match them to the checklist, and surface missing items before the day starts.

The day's files are known, not guessed.
02

Weekly

Exceptions and chase status

Open exceptions, missing client documents, and matters near deadline are reviewed and chased with owners attached.

No matter waits on a follow-up that never went out.
03

Monthly

Operating report and rule-book review

Matters readied, exceptions resolved, days cleared before deadline, and checklist changes are reported for partner review.

The process improves from the audit trail.

Indicative scope

Checked enough to file. Logged enough to prove.

Build phase

Four to eight weeks

DMS and workspace connections, checklist capture per matter type, SSM and LHDN verification rules, chase templates, readiness-report format, reviewer queue, SRO working, parallel run, and go-live.

Operating retainer

Monthly engagement

Daily readiness reports, exception handling, document chasing, reviewer-queue operation, audit logs, monthly operating report, and quarterly checklist and rule-book reviews.

Final scope, duration, and fee are confirmed at the Workflow Review against matter volume, matter mix, DMS footprint, verification sources, and deadline pressure.

What firms ask first

The questions that decide whether files are ready.

Will AI miss something a clerk would catch?

We do not pass low-confidence fields through. They are held for review with the source attached. Scellus does the legwork; the fee earner keeps judgement.

How is client confidentiality handled?

Matter data stays under PDPA 2010 and the 2024 Amendment, with Bar Council obligations respected. Full posture is on the data handling page.

We already have a DMS. What does this add?

Your DMS stores the matter file. It does not read the file against the checklist, chase missing IDs before the deadline, verify names against source records, or prepare the reviewer queue.

How quickly can matters come under control?

Typical builds reach a clean parallel run against one intake cycle in four to six weeks, with handover by week eight. The Workflow Review confirms the firm-specific scope.

Find out what your matters would look like, ready before the deadline.

Start with the matter type that keeps slipping. We will map where the file breaks, what needs to be verified, and the first managed workflow to operate.