Contract Lifecycle & Legal Review
Complements Contracts & Signatures: this page details states, the review gate and the AI layer.
Apps: Contract Management · Signatures · Documents
1. Contract lifecycle
- New contracts always start in
draft.on_holdcan be entered and left from most working states. expiring_soon/expiredare set by the expiry reminder and the passage of time — never by a user button.terminatedrequires a reason. The full status history is recorded.
2. Legal review
| Step | Role | Permission | Result |
|---|---|---|---|
| Create a review linked to a contract | Legal | contract_management:review | pending |
| Review: comments, template checklist, clause risk (low → critical) | Legal | contract_management:review | in_review |
| Decide | Approver | contract_management:approve | approved / rejected / needs_revision |
The creator of a review cannot decide that same review.
3. E-signatures
draft → sent → in_progress → completed, or declined / cancelled / expired. Providers: internal (public signer portal), DocuSign, Viettel, VNPT — the three external providers need a PDF in Documents. Completing signatures does not advance an approval workflow by itself; each domain decides the consequence.
4. Contract amendments
draft → pending_signature → signed → effective (manual activation), or applied directly without e-sign. An amendment that is not effective does not affect figures; an effective amendment is immutable — mistakes are fixed with a new amendment. A signed contract only allows metadata edits; scope and price must go through an amendment.
5. AI contract reading (Contract Intelligence)
The clause playbook holds the company’s own position (standard, acceptable fallback, red line). Classifications edited by hand are never overwritten by AI.