How to cut contract turnaround time between sales and legal
Contract turnaround time between sales and legal is the elapsed time from a salesperson needing an agreement to having one they can send. Most teams measure only the part where a lawyer is working on the contract, which is why the number legal reports and the delay sales experiences almost never match.
That gap is the whole problem, and it is where the fix lives. In most mid-market companies the review is not the slow part. A lawyer can read a standard order form in twenty minutes. The reason it took four days is that it waited three of them.
This guide covers where the time actually goes, how to measure it without a project, the three fixes in order of payoff, and how to tell whether a tool will help you or just make the queue faster.
Cycle time, turnaround time and queue time are three different things
These get used interchangeably and the confusion is expensive, because each responds to a different intervention.
Contract cycle time is the whole lifespan of an agreement, from first request to signature. It includes everything the counterparty does, which you do not control.
Turnaround time is your organisation's portion. It is what you can actually manage.
Queue time is the part almost nobody measures: the hours a contract spends waiting, in an inbox, behind other work, in an approval chain, or for someone to come back from leave.
A thirty-day cycle can easily contain four days of turnaround and twenty minutes of genuine review. If you only track cycle time you will blame the counterparty. If you only track turnaround you will conclude your lawyers are slow. Neither is usually true.
Review time falls when you give the reviewer better tools. Queue time falls when fewer things need a reviewer at all. Buying tooling to accelerate review when your problem is queue depth produces a faster version of the same wait. This is the single most common and most expensive misdiagnosis in contract operations.
Where the time actually goes in the sales-to-legal handoff
The handoff has five points where a contract can stop, and only one of them is review.
- Request. Sales needs an agreement and has to work out how to ask. If the route is "message whoever answers", the clock starts with a delay nobody records.
- Triage. Someone decides whether it is standard, who owns it, and how urgent it is. In teams without a triage rule this is where the longest silences happen, because the contract is nobody's until it is someone's.
- Review. A lawyer reads it. Genuinely the fastest step for standard paper.
- Approval. Often several people, often sequentially, sometimes including someone who has never rejected anything.
- Return. Getting the reviewed version back to sales in a form they can send, which is not instant if it involves reformatting or re-explaining what changed.
Steps 1, 2, 4 and 5 are queue. Step 3 is review. When teams say legal is a bottleneck they usually mean steps 2 and 4, and they usually try to fix step 3.
How to measure it without starting a project
You do not need a system to get an honest baseline. Take the last twenty standard agreements and record three timestamps for each.
- A: when the salesperson first asked
- B: when legal first opened it
- C: when sales had a version they could send
Then:
- Queue time = B minus A
- Review time = C minus B
- Turnaround = C minus A
Do it for standard agreements only. Mixing one heavily negotiated enterprise MSA into twenty order forms destroys the signal, because the hard contract dominates the average and leads you to conclude review is slow when the queue is the problem.
Two things usually emerge. Queue time is a large multiple of review time. And the variance is worse than the average, which is what sales actually feels. A deal that unpredictably takes six days is harder to forecast than one that reliably takes four, even though the average looks similar.
If you want one number to report, use the ratio of queue time to review time. It is more actionable than any absolute figure, and it tells you immediately which of the fixes below to spend on.
The three fixes, in order of payoff
1. Decide in advance what standard agreements may say
This is the fix with the largest effect and it needs no software.
Most contract review is a lawyer re-deciding something the business already settled: what liability cap is acceptable, what payment terms, how long a notice period, whether an indemnity can be mutual. Those are policy decisions, not per-deal legal judgements, and once they are written down they stop consuming a review each time.
The written form of that is a playbook: your position on each term that matters, plus the fallback you will accept, plus the point at which it must escalate.
The test of whether you actually have one is not whether a document exists. It is whether a salesperson can look at a counterparty's markup and know, without asking, whether it is acceptable. If they still have to ask, you have a reference document, not a playbook.
Start with the five terms that generate the most back-and-forth. In most commercial agreements those are liability cap, indemnities, payment terms, term and termination, and data protection. Getting those five decided removes more queue than any tool will.
2. Let commercial teams work inside those positions
Once positions are set, routine agreements do not need to enter the queue at all. Sales generates from an approved template, checks the counterparty's markup against the agreed positions, and escalates only what falls outside them.
The objection is always risk, and it deserves a serious answer rather than a dismissal.
Self-serve increases risk when it means people making judgement calls without guidance. It reduces risk when it means people applying decisions a lawyer already made. The difference is entirely whether the guardrails exist, which is why fix one comes first. Sequencing them the other way round is how self-serve earns its bad reputation.
Done properly this is not legal losing control. It is legal setting the standard once instead of re-applying it fifty times, and seeing every agreement rather than reviewing every agreement. That distinction is the whole point.
This is where GenieAI fits. It holds your agreed positions and checks incoming contracts against them, so a commercial team can draft and review and negotiate standard agreements inside the boundaries legal set, while anything outside them routes to a lawyer. Customers working this way report closing 70% faster, and the reason is queue removal rather than faster reading.
3. Remove approvals that exist for comfort
Most approval chains contain at least one step that catches nothing.
The signs are consistent. The approver has never rejected anything. They cannot describe what they are looking for. They are approving something already covered by an earlier step. Or the approval exists because of one bad contract several years ago and nobody has revisited it since.
A useful exercise: for each approval, ask what would happen if it were removed. If nobody can name a specific risk it catches, it is a notification rather than a control, and it can become one. Telling someone is instant; asking someone is a queue.
Sequential chains deserve particular attention. If four people must approve in order, the elapsed time is the sum of four waits, not four reviews. Approvals that do not depend on each other should happen in parallel, and most do not depend on each other.
Two rules that hold up well in practice: set a value threshold below which a contract needs one approver rather than three, and make every approval time-boxed, so silence past a set period counts as approval rather than as an open loop.
Quick wins you can make this week
The three fixes above are the structural work. These are the changes that need no budget, no software and no project, and they usually move the number on their own.
- Give requests one front door. One channel, one form, one place. Most triage delay is caused by requests arriving in five different inboxes, where each one waits for the person who happens to own that inbox.
- Time-box every approval. Agree that silence past a set period, say two working days, counts as approved. Open-ended approvals are where contracts go quiet, and nobody is ever accountable for a delay that has no deadline.
- Set a value threshold. Below an agreed contract value, one approver instead of three. Most approval chains were designed for the largest deal the company has ever done and then applied to every deal since.
- Write down your position on five terms. Liability cap, indemnities, payment terms, term and termination, data protection. Not a full playbook, just those five, agreed and written where sales can see them.
- Publish legal's target and current actual. Sales chases because it cannot see progress. A visible target reduces chasing, and chasing is itself a meaningful drain on review capacity.
- Measure twenty contracts. The exercise above takes an afternoon and it tells you which of the three fixes is worth your quarter.
None of these require anyone to work faster. They all remove waiting, which is where the time actually is.
What good looks like
A target state worth aiming at, for a mid-market company with a small in-house legal function:
- Standard agreements, meaning your paper with no material amendments, never reach a lawyer. Sales generates, sends, and closes. Legal sees them in the record.
- Lightly amended agreements are checked against the playbook automatically. If the markup sits inside your positions, sales proceeds. If it does not, only the offending clauses go to legal, with the deviation flagged rather than the whole document attached.
- Genuinely non-standard agreements, meaning new counterparty paper, unusual risk or real value, get a proper review, because that is what legal capacity was freed up for.
The measurable outcome is that legal's queue contains only the third category. That is what people mean when they say review by exception, and it is a more useful target than any turnaround figure, because it describes the shape of the work rather than its speed.
When a tool helps, and when it will not
A tool helps when review is genuinely the constraint: high volume, real complexity, or a team that cannot keep pace with contracts that do need a lawyer's judgement. It also helps when you have positions but no way to apply them consistently, which is the common case once a playbook exists.
A tool will not help if the delay is structural. If contracts wait three days because nobody has decided who owns the decision, software will not fix that, and buying a contract lifecycle management platform to solve a queueing problem is an expensive way to find out. The honest sequence is to fix the decision-making first, then automate whatever survives.
The question worth asking a vendor is not how much time their tool saves. It is what happens when a contract falls outside your standards, because that is the case that determines whether your risk actually reduces or simply moves somewhere less visible.
What we cannot tell you
Published turnaround benchmarks should be treated with caution, including any you find in vendor content and including the ones that look authoritative.
Turnaround varies enormously with contract mix, company size, sector, and where a given team starts the clock. Most published figures do not state their definition, so two numbers that look comparable often are not. A figure from a company with a ten-person legal function and heavily negotiated enterprise agreements tells you very little if you have two lawyers and a stack of order forms.
The more useful comparison is against your own baseline, measured the same way each time. That is why the measurement section above is deliberately manual. A number you produced and understand is worth more than an industry average you cannot interrogate.
Frequently asked questions
What is a good contract turnaround time?
There is no universal figure worth quoting, because it depends on contract mix and on where you start the clock. The more useful measure is the ratio of queue time to review time. If queue is several times review, your opportunity is in process rather than in how fast anyone reads.
Is contract turnaround time the same as cycle time?
No. Cycle time is the whole lifespan of the agreement including everything the counterparty does. Turnaround time is your organisation's portion. Measuring only cycle time hides where the delay sits, because counterparty delay and your own queueing look identical in the total.
Why does legal always seem to be the bottleneck?
Usually because legal is the only step with a name on it. Requests waiting to be triaged and approvals waiting in someone's inbox are invisible in most reporting, so the whole delay attaches to the step that is actually recorded. Measuring queue time separately tends to move the conversation from blame to process quite quickly.
Can sales review contracts without a lawyer?
Sales can work inside positions a lawyer has already set, which is different from reviewing without legal input. The risk is not that a non-lawyer looks at a contract; it is that a non-lawyer makes a judgement nobody has guided. With positions defined, routine agreements become an application of existing decisions rather than new ones.
What should we fix first if legal is a bottleneck?
Write down the positions your business will accept on liability, indemnities, payment terms, term and data protection. It costs a meeting, needs no software, and removes the single largest source of repeat review. Every subsequent decision, including any tooling decision, gets easier, because you will know what you are automating.
How do we reduce legal review time on standard sales agreements specifically?
Separate standard from non-standard at intake rather than at review. Most of the time lost on standard agreements is spent establishing that they are standard. If the check happens automatically against your playbook, the genuinely standard ones never consume review capacity at all.
Does going faster mean accepting more risk?
Not if the speed comes from removing queue rather than from skipping checks. Contracts that never needed a lawyer's judgement do not become riskier by reaching a customer sooner. Risk increases when you shorten the review of agreements that genuinely required one, which is the opposite of what review by exception does.
How does GenieAI help with this?
GenieAI holds your agreed positions and checks contracts against them, so commercial teams can draft and negotiate standard agreements inside the boundaries legal has set, while legal keeps sight of every agreement and spends its time on the exceptions. Customers report closing 70% faster as a result. There is more on how sales teams work this way on our legal AI for sales teams page.
