Legal Practice Management

Practice software that matches how the firm actually works.

Software the practice already runs on

A legal practice does not fail because it lacks a slogan. It fails because a limitation date lived in one person’s diary, a hearing moved and the file did not, and the bill went out late because time was in a notebook. LavisTech builds practice software for firms that want matters, documents, dates, and bills in one place they can change. We are a software shop in Chengannur, Kerala — not a law firm, not a bar association, and not a substitute for a qualified practitioner.

This page is about the system the office runs on: matter files, document versions, limitation and hearing calendars, time and billing. It is not legal advice. Nothing here tells you how to advise a client, how to draft a pleading, or how to compute limitation for a live brief. Those questions belong to the advocates and clerks who own the file. The software stores what they decide and reminds them of dates they entered. That is a high bar and a narrow one.

If you wanted a chatbot that “practises,” that is the wrong page. If you wanted AI on top of a matter file, that sits under Legal AI, and it still will not send a letter without a person. Start here if the file itself is still a cupboard, a shared drive, and a WhatsApp group.

This is not legal advice

We will repeat this until it is boring. LavisTech does not practise law. We do not certify that a limitation period is correct. We do not appear. We do not file. A date in the system is a date a person typed or imported, plus reminders they configured. If the date is wrong, the software is wrong in the same way a paper diary is wrong. The practitioner remains responsible for the file.

We will not print fake certifications, partner badges, or “approved by” seals we do not have. If a vendor shows you a gavel logo and a claim that their product replaces a junior, walk away. You are buying software. Buy it the way you buy any other system people work in: scope, permissions, handover, a way to get your data out.

Matters, not folders that only one person understands

A matter is the unit of work: parties, court or forum if any, our reference, their reference, status, the people inside the firm who may see it. Everything else hangs off that record. Documents, dates, time entries, bills, and notes should open from the matter — not from a personal desktop called “cases_new.” When a colleague is in court, another person should still find the file.

We model the way your office already talks. Some firms want client, then matter. Some want a corporate client with many matters. Some need a conflict check before a matter is opened. We do not force a foreign product’s idea of a “case” onto a Kerala practice that lives on notices, title work, and appearances. If a packaged practice system already fits and you will change how you work, buy it. If you have already spent years fighting the package, that is a custom versus off-the-shelf decision, not a theme change.

Closed matters stay searchable. Destroying history because a status changed is how you lose a limitation argument later. Retention is a policy you set with your own counsel. The software enforces the retention you chose. It does not invent one.

Documents that stay with the matter

Incoming PDFs, drafts, signed copies, consigned volumes, and the scan of a paper vakalat — they belong on the matter with a version, a date, and a person. A shared drive with three copies of every pleading is not a document system. It is a curation problem. We put the file in a store you can back up, with the same permissions as the matter. If a junior cannot open the matter, they cannot open the PDF. That sentence is the product.

Check-in and check-out matter when two people edit. So does a clear “filed / draft / incoming” mark that a clerk understands. We do not need an enterprise records product on day one. We need one place, one matter, one current version, and an audit of who replaced it.

WhatsApp still delivers documents. The system does not have to become WhatsApp. It has to make it easy to drop the file onto the matter and leave a note. If the practice will not do that, you will keep two realities. Software cannot fix a habit you will not name.

Limitation and hearing dates that cannot be a WhatsApp rumour

Dates are why firms ask for this software. Limitation, notice periods, filing deadlines, hearing lists, mention dates, and the personal diary of the advocate who is actually appearing. The system holds the date, the matter, who is responsible, and who gets reminded — mail, SMS, or a list on the clerk’s morning screen. The reminder is not a legal opinion. It is an alarm clock on a date a person entered.

We will not auto-compute limitation from a statute library and call it safe. Computation of limitation is legal work. If you want a calculator that applies a rule you wrote down for a matter type, a person still confirms the result before it becomes the date the firm trusts. The model, if any, does not file and does not send. A person does.

Cause lists change. The software should make it cheap to move a hearing and leave a trail. A date that vanished because someone edited a cell in Excel is the failure mode we are here to end. Parallel Excel after go-live means the calendar is not done.

Time and billing without replacing Tally

Time on a matter, disbursements, and a bill the client will recognise are practice work. Tally (or another accounts package) is often already the books. We do not pick a fight with Tally. The practice system holds work-in-progress and raises a bill the accountant can post — a voucher, an export, or a posting your Tally already understands. GST on fees and expenses belongs in fields a person can correct, not in a speech about disruption.

If the firm bills by appearance, by hour, or by a fee agreed on the matter, we model that. We do not force hourly on a practice that has never kept hours. We do not invent a realisation dashboard that shames people in the first slice. First slice: time or fees can be entered against a matter, a bill can be drafted, and accounts can post it. Reports come when the entries are true.

Excel billing workbooks are a source, not a personality. If you must import last year’s WIP, that is a small data migration, with mapping and a rehearsal — not a paste the night before training.

What we will not print on the homepage

• A claim that this software is approved by a court, a council, or a bar body unless that is a fact we can show.
• A claim that the system replaces a junior advocate or a clerk.
• A claim that limitation is “taken care of” by the vendor.
• Fake client names or invented rupee recoveries.
• Legal advice, templates sold as advice, or a model that sends to a client alone.

We will print what the software does: stores the file, shows the dates you entered, drafts the bill from time you recorded, and keeps permissions aligned with the matter. That is enough work to do honestly.

A first slice a clerk can finish

Write the assumption as a sentence. “On Tuesday the clerk can open a matter, attach today’s PDF, and see the next hearing without asking the senior.” Build only that: login, matter, document, date, a list for the day. Conflict checks, client portals, and realisation reports can wait. An MVP that tries to be a full practice suite is a full project in denial.

We sit with the clerk if we can. We watch the diary, the WhatsApp group, and the Excel that actually runs the week. The slice is done when they complete yesterday in the system without us in the room. “They said the screens look clean” is not a pass.

Hosted, backed up, with a way to undo a bad edit on a date. Cutting those to look lean produces a prototype you cannot leave with a practice. Call it a prototype if you must. Do not call it the system and then vanish.

Permissions the way the firm already divides work

Seniors, juniors, clerks, accounts, and visiting counsel do not see the same files. A family matter and a corporate retainer should not share a browse list because someone used a weak search. The signed-in user sees the matters they are on, plus what a partner explicitly shared. That is the same rule we use when a model later reads a file: the model inherits the person’s permissions. It does not get a back door.

Audit is not optional. Who opened, who changed a date, who downloaded a PDF. A practice that cannot answer “who sent that draft” will not survive the first argument about a leaked file. We log it. You decide retention with your own counsel.

If you want a client to see selected orders or bills, that is a portal with a smaller permission set — not a second copy of the whole matter on the open internet. Many firms should wait. A WhatsApp update from the clerk is still how a lot of Kerala practice talks to clients. A portal is a product, not a moral improvement.

Cost and calendar

A focused first slice — matters, documents, dates, one bill export — is often in the same band as other internal tools: eight to sixteen weeks when the data is willing and Tally already has a home for the posting. A fuller practice system with portals, richer billing, and a migration of years of files is a programme, usually phased over several months. Discovery that produces a written mapping of your diary and your drive is weeks, and it is worth paying for.

We will not invent a rupee total before we have seen the drive and the diary. Licences for mail or SMS reminders are yours to keep paying. Hosting and backups do not disappear at handover. If a vendor quotes a precise package price without seeing how you store PDFs today, treat it as marketing. How we estimate any custom system is on how much custom software costs.

Your hours: a partner or a senior clerk, regularly. Date rules and matter types cannot be guessed from Chengannur. If that person cannot be named, wait.

WhatsApp, Excel, and the diary that still exists

We do not shame a practice for WhatsApp. We ask whether the system is the place the date is written first. If the diary remains the truth and the software is a copy, you bought a reporting problem. The first week after go-live should retire the competing list, or you should admit the slice was the wrong job.

Excel will linger for a report someone trusts. That is fine if it is an export. It is not fine if it is a second ledger of dates. We would rather ship a dull morning list than a colourful dashboard that nobody opens.

How this sits next to Legal AI and .NET

The practice system is the system of record. Legal AI, if you add it later, drafts from the matter, extracts from a PDF, or searches precedents with a citation a person can open. It does not become the record. It does not advise the client. It does not file. Read that page before you buy a “legal GPT” skin.

Most of this work we build in .NET because that is the stack we staff for long-lived systems with roles and audit. If your office already lives in another stack and has people for it, say so. The discipline does not change: permissions, backups, a handover, a definition of done a clerk would recognise.

How to brief us

Send how many live matters you expect, where PDFs live today, how dates are kept, and whether Tally must stay. Send the one failure you will not repeat — a missed limitation, a lost scan, a bill that took a month. Do not send a wish list of twenty modules. Send the Tuesday job.

Say whether you need a client login. Say who must never see family matters. Say what “closed” means in your office. Those sentences are the design.

If you want to talk it through, contact us with the diary and the drive, not a slogan. We will tell you whether a package is enough, whether a first slice is enough, and what we will refuse to automate. We will not pretend the software is a lawyer.