Vault & Document Management

Contract lifecycle

Live

Every contract has a status, only legal moves between them, a notice deadline derived from the record, and a renewal decision written down.

Try LexVio free →Open scanner

What you get

✓Thirteen statuses: draft, in review, in negotiation, pending approval, approved, pending signature, executed, active, expiring, expired, renewed, terminated, archived
✓A transition table — a move it does not list is a 409, for a person, the Deal Desk and the sweep alike
✓Every status change audited with before and after, scoped to the matter
✓The daily sweep: expiring 30 days before the end date, expired the day after it

+7 more capabilities below

Overview

What it is.

Until September 2026 a contract in the vault was "active" from the day it was uploaded and nothing ever changed that. Now every contract carries one of thirteen statuses — draft, in review, in negotiation, pending approval, approved, pending signature, executed, active, expiring, expired, renewed, terminated, archived — and only the moves the lifecycle table allows are accepted; anything else is refused with a 409, whoever asked. The moves are driven by the modules: an approval outcome, the daily sweep that marks a contract expiring 30 days before its end date and expired the day after it, and archiving, which is its own role-gated action rather than a status you can type.

The non-renewal notice deadline is derived, not guessed: expiry date minus the notice period, recomputed whenever either changes. The sweep flags it at 30, 7 and 1 days and, at 30, files one task — decide: renew, renegotiate or terminate — that is never filed twice. Whether a contract auto-renews is read from the renewal clause by a fixed phrase list and is either true or unknown, never false because the clause said nothing. The decision you make is recorded on the contract with who made it and when; it does not move the status, because deciding to terminate is not the termination.

How it works

Three steps.
End to end.

1. Correct the record

Edit the extracted metadata — parties, dates, value, governing law, renewal terms, notice period. The edit is stamped with who and when, an expiry you correct is marked as a person's reading rather than the model's, and the notice deadline is recomputed.

2. Let the modules move it

An approval moves it to approved, or back to negotiation on rejection; the daily sweep moves it to expiring and expired; an explicit status call handles the rest, and refuses a move the table does not allow. Archiving needs the delete role.

3. Upload the next version

The counterparty's returned draft or the signed copy is uploaded onto the chain, passes every check the first upload did, and becomes the next numbered version — a parent that is not yet signed puts it in negotiation.

Capabilities

What you get.

✓Thirteen statuses: draft, in review, in negotiation, pending approval, approved, pending signature, executed, active, expiring, expired, renewed, terminated, archived
✓A transition table — a move it does not list is a 409, for a person, the Deal Desk and the sweep alike
✓Every status change audited with before and after, scoped to the matter
✓The daily sweep: expiring 30 days before the end date, expired the day after it
✓Notice deadline = expiry date − notice period, derived and recomputed, never typed in
✓Flags at 30, 7 and 1 days before the notice deadline, and one system-filed task at 30 days
✓Auto-renews read from the renewal clause: true or unknown, never false by absence
✓A renewal decision — renew, renegotiate, terminate, let lapse — recorded with who and when, separately from the status
✓Metadata corrections stamped with the editor and the time; a corrected expiry is marked as a person's reading
✓New versions uploaded onto the chain with the same accept list, size, storage-quota and antivirus checks as the first upload
✓Archiving is a role-gated action; archived contracts are hidden from the vault unless you ask for them

FAQ

Quick answers.

Can I set a contract to any status I like?

No. The lifecycle table lists the moves that make sense — a draft can go into review, not straight to expired — and anything else is refused. You can archive from most states, and unarchive brings a contract back to active.

Does the product decide whether to renew?

No. It derives the deadline and files the task; the decision is yours and is written on the record with your name. Deciding to terminate does not terminate anything — that status move is a separate, explicit step when it actually happens.

Is there e-signature?

No. Pending signature and executed are statuses you move a contract through; nothing here sends a document out for signing.