Document management for law firms and corporate legal teams

Legal work runs on documents that have to be exactly right: the wording of a clause, the version that is in force, and who is allowed to read it. This page covers the document problems that legal teams meet most often and how Obscura handles them, from standard agreement templates to signing with the counterparty.

The document problems legal teams face

An agreement rarely ends with its first signature. Addenda, notices, acceptance records and invoices follow, and they arrive through different inboxes and folders. When someone asks which wording is in force today, the team first has to rebuild the history of the contract by hand.

Working drafts cause a second problem. Drafts travel back and forth by email, someone edits a downloaded copy, and the signed PDF ends up in a shared folder. When a reviewer or a client asks which copy is the official one, the answer often depends on someone's memory.

The third problem is confidentiality. Client files and contracts under negotiation should not be open to everyone in the office, and they certainly should not leave it. When a copy leaks, the team needs to know who held it, and identical copies give no clue.

Standard agreements take time as well. Many teams start from the last contract they can find and replace the party names, dates and amounts one by one, and a single field that gets missed can reach the counterparty.

Four workflows legal teams use

1. From template to signing with the counterparty

The team picks an approved agreement template from the shared template library and fills in a short form. Obscura reads the fields straight from the template file, so nobody maintains a separate list of what to fill in. The rendered document appears beside the form, which lets the team check names, dates and amounts before the document is created. The template also sets the folder, classification, document type and title pattern, so the new document is filed in the right place from the start.

After the draft is edited, a reviewer compares two versions of the document with their saved metadata before approving the revision. The document then follows the approval route you set, with deadlines, delegation and escalation, and every decision is kept with its note. At the signing step the counterparty can sign as one step in the route without an Obscura account. Certified signing and e-Meterai run through a connected PSrE provider. Without a provider, Obscura signs with its own internal certificate authority, which is not PSrE-certified.

Which kind of signature is enough for a particular document is a legal judgement for you to make. The basics are covered in the guide to electronic vs digital signatures.

2. Addenda and the wording in force

In the Contract & Project Intelligence module, each agreement has a workspace that holds its terms, obligations and review history. The project relationship graph shows an addendum beside the agreement it changes, together with the proposal, orders and billing documents around it. When a new version of the agreement becomes current, Obscura opens a review task so that someone checks the terms, the parties and the obligations again. The record shows who finished the review and when.

When an addendum changes a term that was already reviewed, Obscura shows the earlier term beside the suggested replacement, and the earlier period stays on record. Each extracted fact is shown beside its source quotation and the document version it was read from, so a reviewer can check it before relying on it. The guide to contract addenda explains what an addendum contains and how to keep a register of them.

3. Obligations and deadlines with owners

A term suggested by AI only counts once someone on the team has reviewed it and recorded why. After an obligation is confirmed, you choose who is responsible for it and how many days ahead Obscura should remind that person. Open obligations and required reviews therefore always have a name beside them.

Extracting terms with AI needs the AI module. The team can also use Contract & Project Intelligence by hand, with the information and links they enter themselves.

4. Asking a contract a question, and sharing files outside

With the AI module, the team can ask a single contract about its terms. The answer is drawn from the contract, its reviewed sources, its findings and the linked project documents that the person asking is allowed to read, and each answer cites its sources. The same kind of question can go to the whole archive, which still uses only documents the person asking can open. AI can be wrong, so anything important should be checked against the document itself.

For sharing outside, you set who can use a share link and when it expires, and you can revoke it once the need ends. With the AI module you can also turn on document Q&A for selected share links, with a question allowance for each link, and every question and answer is logged.

Confidentiality of client files

Access to each document follows responsibility, because you decide who can view a record and who can change it. Members-only folders and step-up verification are already part of the core. For your most sensitive files, the Secure Folder module encrypts selected folders with their own keys and records each decryption in the audit trail. The audit log also records changes, decisions and activity on each document.

In secure preview, the viewer's identity appears as a visible watermark. Downloaded or shared copies can carry an invisible mark for their recipient through the Watermarking module, and an issuance ledger links the file, the version and the recipient. If a leaked image or copy turns up, the team examines it in the verification console to see which recipient it was issued to.

This tracing has limits. It works best on the original file or on a clear screenshot that shows at least two paragraphs of body text. Photos of a screen are not supported, and results on recompressed images depend on how much text survives. A watermark points to who received a copy, and it does not replace your own judgement. More is in the guide to watermarking confidential documents and on the watermarking page.

For AI, you decide whether it is used at all and where the model runs. An administrator can switch AI off for the whole deployment, run a local model, or use a provider your organisation has approved. Full-text search and document management keep working without AI. More security detail is on the security page.

Where Obscura runs

Obscura Cloud is run by Valid in Indonesia, and each organisation is a separate tenant. Obscura Private and Enterprise run in your own cloud environment, where we recommend AWS. By special arrangement, both can also run on on-premise servers or on a closed network. The modules are the same in every edition, so the choice is about who runs Obscura. The editions are compared on the deployment page.

Start with one agreement

Bring one agreement your team manages, together with one of its addenda. We will follow it through Obscura with you using a safe sample, and then agree on what a pilot should test. To get started, reach us through the contact page.

Learn more: Contract & Project Intelligence and Project Intelligence, document templates, approvals and e-signatures, document control and the module overview.