Subharti IT Solutions Discuss your project

Legal Technology, Enterprise Applications

Institutional Legal Management System

Matter, document and approval management for an institutional legal department, built around clearance levels, matter-level confidentiality and a tamper-resistant audit trail.

See 7 use cases Discuss a similar project
A notebook, glasses and magnifier on a desk
Illustrative photo

The problem

An institutional legal department handles litigation, legal notices, contracts, MOUs, opinions and RTI requests for several related entities. Work arrives from many departments, is drafted by attorneys, reviewed by senior authorities and sometimes paid out through finance. Without a shared system, assignments, deadlines and approvals are tracked by hand, and confidential drafts travel by email with no record of who saw them.

The department needed one system where people can do their own work without seeing matters, drafts or strategy they are not authorised to see.

The solution

The system is designed around role-based and matter-level access control. Management users sit at defined clearance levels, and each level can supervise, reassign and restrict work below it but cannot override the levels above. Attorneys see only their assigned matters, trainees work in a separate suggestion layer, and a nodal officer can allocate and track work using metadata alone, without opening the confidential content.

Finance, audit, external advocates, contract owners and the RTI officer are separate functional roles with narrowly scoped access. Every change to a record, a permission or an approval is written to an audit trail that ordinary application functions cannot alter.

Use cases

How each role uses Institutional Legal Management System, and what changes for the organisation.

  • Legal administration (nodal officer) Specified

    Assigning a confidential matter

    A department raises a legal request. The nodal officer registers it, sets priority and a deadline, and assigns it to an attorney using the matter’s details only.

    ResultWork is allocated and tracked without the coordinator seeing the attorney’s confidential opinion or strategy.

  • Attorney Specified

    Keeping each attorney’s matters separate

    An attorney drafts notices, opinions and contracts for the matters assigned to them, records hearings and submits work for review.

    ResultAttorneys see only their own matters unless access is explicitly shared with them.

  • Trainee Specified

    Supervised research by trainees

    A trainee reads the documents assigned to them and adds research notes and suggested changes.

    ResultSuggestions stay separate from the official record until an authorised user accepts them.

  • Director Specified

    Restricting a sensitive document

    A director restricts a document from users below their clearance and records the reason.

    ResultThe restriction applies at once, cannot override higher authorities and is written to the audit trail.

  • Finance officer Specified

    Processing an advocate’s bill

    Finance checks an external advocate’s invoice, taxes and deductions, then records the payment reference.

    ResultBills are processed without access to privileged opinions or litigation strategy.

  • RTI officer Specified

    Tracking an RTI application

    The RTI officer registers an application, sends information requests to departments and watches the statutory deadline.

    ResultReplies and appeals go out on time, with the full correspondence trail kept.

  • Management Specified

    Reviewing who changed what

    A management user opens a matter to see every change to its records, permissions and approvals.

    ResultA complete history, which ordinary functions cannot erase, supports oversight and audits.

“Specified” use cases are defined in the project’s requirements documents.

Features

  • Clearance-based hierarchy

    Six institutional clearance levels, each able to supervise and restrict the levels below it without overriding those above.

  • Matter- and document-level confidentiality

    Standard, confidential, restricted and highly restricted classifications, with separate view, edit, download and share permissions and time-limited grants.

  • Metadata-only coordination

    A nodal officer can register requests, assign attorneys and monitor deadlines without access to privileged drafts or opinions.

  • Configurable approval workflow

    Request, assignment, drafting, review and approval steps, configurable for litigation, notices, contracts, MOUs, opinions and RTI.

  • Scoped functional roles

    Finance, internal audit, external advocates, contract owners and RTI officers each see only what their task needs.

  • Protected audit trail

    User, time, record, previous and new value and reason are recorded for every important change, and cannot be erased through the application.

Need something like this?

We can adapt the approach to your organisation’s rules, roles and existing systems.

Discuss your project