CLM Dashboard & Contract Request Center
LiveA contracts dashboard where every figure states its basis, and a request desk where triage is decided by your rules, not a model.
- ✓Dashboard figures each with a basis sentence; null when not computable
- ✓Cycle time median and p90 over 365 days, from three contracts up
- ✓Request types with their own forms; invalid fields named
- ✓Rule-based triage — reviews and signatory band name their rule
What it is.
The CLM Dashboard covers your agreements: status breakdown, expiries, analysis and risk, review workload and cycle time. Each block carries a sentence saying how it was computed. A figure that cannot be computed is shown as empty with the reason; cycle time needs at least three contracts, because a median of two is an anecdote. Expiry tiles use the same rule as the vault filter they link to.
The Contract Request Center takes a request for an NDA, a DPA, a vendor agreement, an amendment, a renewal or a termination, asking only the questions each type needs. Triage evaluates your Deal Desk rules: who must review and which signatory band applies, each naming its rule; with no rules set, legal review is always required and privacy review is added when the purpose names personal data. No money threshold is assumed. Values are kept in the currency typed, never converted. A submitted request can start the contract lifecycle workflow.
Three steps.
End to end.
Pick the type; answer its form; attach documents.
Your rules decide the reviews and signatory; an owner is assigned and gets a task.
Start the workflow; watch the contract on the CLM Dashboard.
What you get.
- ✓Dashboard figures each with a basis sentence; null when not computable
- ✓Cycle time median and p90 over 365 days, from three contracts up
- ✓Request types with their own forms; invalid fields named
- ✓Rule-based triage — reviews and signatory band name their rule
- ✓No default money threshold; no currency conversion
- ✓Contract lifecycle workflow with role-gated steps, from request to archive
Quick answers.
No. Your rules decide; a model never chooses the reviewers.
A request moves only through its defined states; starting the workflow needs a submitted request.
More in Contracts & Documents.
Documents stored in AWS Mumbai with server-side encryption, over TLS, scoped to your organisation.
Per-document share links with an expiry, a view cap, granular permissions, and recipient-tagged watermarking.
Chain successive drafts of a contract together, and compare any two clause by clause.
Every upload is a document with a category — agreement, evidence, court order, correspondence, identity — and the category decides what runs. Nothing is analysed unless you ask.