The Contract Management Process: A Complete 2026 Playbook

A contract management process is the sequence of steps a business runs every time it creates, negotiates, signs, and later manages a contract, plus the rule for who owns each step. Most companies already have one, informally: someone drafts, someone approves over email, someone signs, and the PDF ends up in a folder. It breaks down not because a step is missing, but because nobody has written down who owns it, so it only works while the one person who remembers everything stays at the company.

Adira, which publishes this guide, sells contract management software. This page works as a standalone playbook whether or not you ever use ours, and it names the one gap in this process specific to India that most guides, written for the US market, skip: what "signed" actually means once stamp duty is in the picture.

This is a pillar guide, walking through all nine stages in order, with a goal, a common failure, and a concrete fix for each. For depth on one stage, jump to what CLM software actually does or building an approval workflow.

The nine stages, and who owns each

1. Intake: the request that starts everything

Goal: capture what is being asked for, with enough detail that whoever picks it up next need not chase the requester for basics.

Common failure: requests arrive as a one-line Slack message, "can legal look at this vendor contract by Friday," with no counterparty name, no value, no note of what is unusual about it. Legal does detective work before it can even start reviewing.

Fix: one structured form or channel, capturing counterparty, contract type, value, deadline, and anything already agreed. Route low-value, standard requests to a self-serve template; route everything else to a human. Owner: the requester, with legal or ops defining the form.

2. Drafting: templates and the clause library

Goal: produce a first draft that starts from your approved positions, not a blank page or whatever the other side sent.

Common failure: someone drafts from an old contract found by searching their inbox, carrying forward a clause negotiated away for a specific reason years ago, or drafts on the counterparty's paper by default because pulling your own template is more effort.

Fix: a small set of current templates per contract type, backed by a clause library of pre-approved wording, so a drafter assembles known-good parts instead of writing from memory.

There is a legal floor here a template cannot skip. Section 10 of the Indian Contract Act, 1872 sets out what makes an agreement a contract at all:

"All agreements are contracts if they are made by the free consent of parties competent to contract, for a lawful consideration and with a lawful object, and are not hereby expressly declared to be void." Source: Section 10, Indian Contract Act, 1872

A template missing a clear consideration clause, or drafted for a party not competent to contract, is not a contract at all, however well it is formatted. Owner: legal, for template upkeep; the drafter, for a specific deal.

3. Review and risk assessment

Goal: decide, quickly and consistently, how much scrutiny a contract needs.

Common failure: every contract, a two-page NDA and a seven-figure supply agreement alike, gets the same deep manual review, so reviewers burn hours on low-risk paper while high-risk deals wait in the same queue.

Fix: score risk against fixed dimensions (financial exposure, indemnity scope, IP terms, data handling, counterparty history) and let the score set review depth. AI-assisted first-pass review can flag playbook deviations fast; a human still judges whether a flag is actually acceptable for this deal. See how contract risk scoring works, and what it misses. Owner: legal or contract ops.

4. Approval workflow

Goal: get the right sign-offs without every contract routing through one overloaded general counsel.

Common failure: approvals run sequentially (finance waits for legal, which waits for the business owner), so a contract needing three sign-offs takes three separate multi-day waits instead of one parallel round, and nothing moves while an approver is on leave.

Fix: an approval matrix keyed to value and risk tier, run in parallel, with named backups. Low-risk, in-playbook contracts can auto-approve. See how to set up contract approval workflows. Owner: legal or finance ops, jointly.

5. Negotiation and redlining

Goal: converge on final terms through tracked, version-controlled rounds, conceding only what the playbook allows.

Common failure: redlines fly back and forth by email with no single source of truth for the current version, and negotiators assume nothing is binding until a formal signature page. That assumption is not safe in India.

The case to know is Trimex International FZE Ltd v Vedanta Aluminium Ltd (2010) 3 SCC 1. Trimex and Vedanta never signed one combined contract document; they exchanged terms by email, and Vedanta's email of 16 October 2007 confirmed acceptance of Trimex's offer on price, quantity, delivery, payment terms, and the arbitration clause. The Supreme Court held that once the essential terms of a commercial offer are accepted unequivocally, with no condition that a formal purchase order must follow, a concluded, binding contract exists, arbitration clause included, without a single signed document. Full judgment: Indian Kanoon.

Fix: mark negotiation drafts "subject to contract" until your side is actually ready to be bound, and train negotiators that an email confirming the last open point can itself close the deal. Owner: the deal lead, with legal setting fallback positions in the negotiation playbook. See how to build a contract negotiation playbook.

6. Execution: signing is not the finish line in India

Goal: turn an agreed draft into a validly executed, usable instrument, not just a signed PDF.

Common failure: the team treats e-signature as the end of execution, the assumption most CLM software built for the US and Europe makes. In India, it usually is not the end.

Section 35 of the Indian Stamp Act, 1899 is the operative rule:

"No instrument chargeable with duty shall be admitted in evidence for any purpose by any person having by law or consent of parties authority to receive evidence, or shall be acted upon, registered or authenticated by any such person or by any public officer, unless such instrument is duly stamped." Source: Section 35, Indian Stamp Act, 1899

An unstamped contract is not void, it is legally binding under Section 10 above, but it cannot be produced as evidence or acted on by a court or public officer until the deficient duty, and usually a penalty, is paid. This was tested directly for arbitration clauses: a 2023 Constitution Bench first held an unstamped arbitration clause void, then a seven-judge bench reversed that in In Re: Interplay Between Arbitration Agreements under the Arbitration and Conciliation Act, 1996 and the Indian Stamp Act, 1899 (2023 INSC 1066, 13 December 2023), holding the defect is curable inadmissibility, not voidness. Full judgment: Indian Kanoon.

Fix: build "stamped" (and, for some documents, "registered") into your definition of "executed," as a tracked field, not an afterthought that surfaces only when someone needs to produce the contract in a dispute. Full mechanics: electronic signature validity in India and stamp duty by state and instrument type. Owner: whoever the contract names as responsible for stamping, explicitly, not left implied.

7. Repository: where the signed contract actually lives

Goal: one findable, structured store of every executed contract and its key metadata.

Common failure: the final signed copy lives in a salesperson's inbox or a shared drive with no naming convention. Finding one clause across a hundred contracts means opening a hundred PDFs by hand.

Fix: a central repository, even a well-organised shared drive with a metadata spreadsheet counts at small scale, capturing parties, contract type, value, effective and expiry dates, renewal-notice date, owner, and governing law at the point of filing. See how to build a contract repository, step by step. Owner: contract ops or legal ops.

8. Obligations and renewals

Goal: track what each contract still requires after signing, and act before a deadline, not after.

Common failure: a renewal-notice deadline (the date by which you must say no to auto-renewal, typically 30 to 90 days before the renewal date itself) gets missed because it lived in one person's calendar, and the contract silently rolls over on terms nobody re-checked.

Fix: extract every obligation and date at signing, assign a named owner to each, and set reminders with real lead time ahead of the notice date, not the renewal date. See obligation management and auto-renewal clauses in India. Owner: the business relationship owner, with legal or contract ops running the tracking system.

9. Reporting

Goal: answer portfolio-level questions, how many vendor contracts renew next quarter, what is our average payment term, without opening every document by hand.

Common failure: this stage simply does not exist. Contracts are signed, filed, and never looked at again as a set, so "what is our total exposure under indemnity clauses across live vendor contracts" has no fast answer.

Fix: structured metadata from the repository and obligation stages, aggregated on a dashboard or a spreadsheet pivot table. This is the stage that most clearly separates a repository from full CLM. Owner: legal ops, reporting to the general counsel or CFO.

A maturity model: spreadsheet to repository to full CLM

Most organisations sit at one of three levels; the honest answer to "what should we use" depends on which level you are actually at, not which one a vendor wants to sell you.

Level 1: spreadsheet and shared drive. PDFs in folders, key dates on a spreadsheet updated inconsistently. Fine under roughly 50 to 100 live contracts with one or two people responsible. Breaks the moment that person leaves, because the process lived in their head, not a tool.

Level 2: a structured repository. Contracts filed with consistent metadata at signing, searchable by counterparty, type, and date, with renewal reminders that do not depend on one calendar. Enough for most teams for years, but drafting, approvals, and negotiation still happen informally.

Level 3: full CLM. All nine stages run as one connected workflow, including India-specific stamping tracked rather than assumed, with an audit trail end to end. Earns its cost past a few hundred live contracts or real multi-approver chains.

Jumping to Level 3 without Level 1 basics, clean metadata, a real repository, usually means migrating messy data into an expensive tool and getting the same chaos with a nicer interface. For a lightweight start, mark up a single draft for free in Weave before deciding whether a full overhaul is even needed.

Red flags across the process

Normal	Red flag	Why it matters
One structured intake channel for requests	Requests arrive as scattered emails and Slack messages	No consistent record of what was requested, or when
Drafts start from an approved template	Drafts start from whatever old contract turns up in an inbox	Old, deal-specific terms carry forward unchecked
Approvals run in parallel with named backups	Approvals run sequentially through one person, no delegate	One inbox becomes the bottleneck for the whole company
Drafts marked "subject to contract" until ready to be bound	Negotiators assume nothing is binding until signature	An email confirming terms can itself form a contract, under Trimex v Vedanta
"Executed" means signed and stamped	"Executed" means only that both sides e-signed	Under Section 35, an unstamped contract cannot be used as evidence
Contracts filed with metadata the same week they are signed	Signed contracts sit in an inbox for weeks or months	Effectively unfindable when a dispute or audit needs it fast
Renewal-notice dates tracked separately, with lead time	Only the renewal date is tracked, not the notice deadline	Contracts auto-renew on old terms after the window closes unnoticed
A named owner for every contract post-signature	No one owns a contract once it is signed	Obligations and renewal risk get monitored by nobody

Fixing the approval stage: a bad clause vs a better one

Bad: "This Agreement shall be signed by an authorised representative of each Party."

What is wrong: it names no person or role, sets no internal approval threshold, and gives no way to check afterward whether the signatory had authority to bind the company for a deal this size. It surfaces as a problem only when someone disputes whether the contract was properly authorised.

Better: "This Agreement shall be signed on behalf of [Party A] only by [Name/Title] or another individual holding a valid, current delegation of signing authority under [Party A]'s internal approval policy for contracts of this value and risk tier, and [Party A] confirms that the internal approvals required under that policy have been obtained prior to execution."

What changed and why: it ties the signature to a named delegation of authority and an approval step that actually happened, instead of assuming anyone with a pen and a company email can bind the business. Not itself a statutory requirement, this is a drafting fix for the Stage 4 failure, closing the gap between what the approval matrix requires and what the signature page verifies.

These stages are not independent: a weak clause library (Stage 2) creates more review work (Stage 3); a cluttered approval matrix (Stage 4) slows negotiation (Stage 5); and an execution stage (Stage 6) that ignores stamping produces a document that looks finished in the repository (Stage 7) but is unusable if a dispute reaches court. Fixing one stage in isolation just moves the bottleneck to the next. See the full definition of CLM across all nine stages.

US and global contrast

Guides written for the US and European markets treat execution as complete the moment e-signature is collected, since those markets have no broad, ad valorem stamp duty sitting between a signed contract and an admissible one. Their maturity model and approval-workflow advice largely transfer as-is. Where it breaks is Stage 6: a process built around "signed equals done" will quietly produce validly agreed but practically unusable contracts in an Indian legal team, because it never asked the stamping question at all.

FAQ

What is the difference between contract management and contract lifecycle management (CLM)? Often used interchangeably, but strictly, "contract management" can mean just the post-signature stages (repository, obligations, reporting), while CLM covers all nine, intake through execution too. See what CLM actually is.

Which stage causes the most delay? Usually approvals, then negotiation. Sequential chains through one overloaded person are the biggest fixable bottleneck; negotiation delay follows when there is no fallback playbook. See how to reduce contract turnaround time.

Is an e-signed contract enough to be "executed" in India? Not always. E-signing makes the signature valid, but under Section 35 of the Indian Stamp Act, 1899, an unstamped or under-stamped instrument cannot be admitted in evidence or acted on by a public officer, whatever signature method was used. Registration may also be required, depending on the contract type. See electronic signature validity in India.

Can a contract be binding before anyone signs a formal document? Yes, if essential terms have been accepted unequivocally, including by email, as the Supreme Court held in Trimex International FZE Ltd v Vedanta Aluminium Ltd (2010) 3 SCC 1. This is a real negotiation-stage risk, which is why drafts should be marked "not an offer capable of acceptance" until your side intends to be bound.

What is the single most common failure across all nine stages? No named owner. Almost every failure above, a missed renewal, an unauthorised signature, a contract nobody can find, traces back to a stage where responsibility was assumed rather than assigned.

This guide gets you a working, stage-by-stage process and the India-specific legal points, formation under Section 10 and execution under Section 35, that most process guides written for other markets leave out. It does not tell you what risk tier your contracts should sit at, whether a specific signatory had valid authority, or whether a specific contract is properly stamped and enforceable. Those depend on your facts and your state's rules, and are not legal advice. Talk to a lawyer, or your state's stamp authority, before relying on a contract's execution status in a dispute.