When the CFO asks how long it takes legal to review a contract, the answer is usually "it depends" followed by a number that represents signature-to-execution time for a recent deal that went smoothly. That number is not wrong, but it is not the number that tells you anything useful about where the process can be improved.
The useful numbers are narrower. They are the cycle times for specific sub-stages of the review process, and they behave differently depending on what is driving them. Teams that improve review velocity have learned to distinguish between the stages they control and the stages they do not — and to focus their process work accordingly.
Breaking Down the Contract Cycle
A complete contract cycle has roughly six distinct stages, each with its own clock:
- Intake to assignment: time from contract receipt to the point where a specific reviewer has been assigned. This is entirely an internal process time and should be near zero in a well-structured intake system. In practice, it ranges from minutes to days depending on how the team handles routing.
- Assignment to first-redline: time from reviewer assignment to the first substantive markup sent to the counterparty. This is the stage legal ops teams most directly control, and it is the stage where systematic review tooling has the most direct impact.
- First-redline to counterparty response: this clock belongs to the other side. Legal has no leverage over it except relationship and urgency, and it often accounts for a large share of total cycle time on deals where counterparties are slow.
- Negotiation round-trip time: the average elapsed time per negotiation round, across however many rounds are required to reach agreed terms. Affected by redline quality (fewer rounds = faster resolution), by counterparty responsiveness, and by internal escalation pathways when issues require business sign-off.
- Final execution: time from agreed terms to fully executed signatures. Signature workflow tooling has largely standardized this stage; it should be under 24 hours for most agreements.
- Total elapsed time (time-to-signature): the aggregate of all of the above. This is the number CFOs and deal teams track. Improving it requires knowing which sub-stage is the bottleneck.
Most legal teams track only total elapsed time. They often do not track intake-to-assignment, assignment-to-first-redline, or negotiation round-trip times separately. As a result, they cannot distinguish between "our reviews are slow" and "the counterparty takes two weeks to respond" — two completely different problems requiring completely different responses.
The Assignment-to-First-Redline Metric
This is the metric legal ops teams actually control, and it is where we focus when working with teams on process improvement. It measures the time from when a reviewer has the contract in hand to when the first substantive position goes back to the counterparty.
What drives variation in this metric:
Contract complexity: a standard NDA should produce a first-redline in two to four hours for an experienced reviewer. A complex master services agreement with custom IP provisions, data handling requirements, and service level schedules is legitimately different. Teams that do not segment by contract type cannot distinguish between complexity-driven variation and process-driven variation.
Playbook retrieval time: how long does it take the reviewer to confirm the approved position on the clause types present in the agreement? For teams with accessible, current playbooks, this is minutes. For teams with PDF playbooks in shared drives that may or may not be current, it is longer and introduces uncertainty about whether the position retrieved is still the approved one.
Deviation identification completeness: a reviewer who does a complete first-pass identification of all deviations from standard before starting to redline produces a more accurate first-redline and often requires fewer subsequent rounds. A reviewer who redlines as they read, addressing deviations in order, sometimes produces redlines that require additional passes when a later clause interacts with an earlier one.
Escalation and consultation: when a reviewer encounters a non-standard clause requiring business input or senior counsel sign-off, the clock stops until that consultation is complete. Teams with clear escalation paths and fast internal response times have shorter pauses at this stage than teams where escalation is informal and response times are unpredictable.
Negotiation Round-Trip Time and Redline Quality
There is a direct relationship between first-redline quality and total negotiation round-trip time. A first-redline that is thorough — addressing all meaningful deviations, providing clear position statements, offering alternative language where useful — gives the counterparty everything they need to respond substantively on the first pass. A first-redline that is partial, or that addresses one issue while leaving a related issue unremarked, generates a counterparty response that reopens issues the reviewing party thought were closed.
This doesn't mean every first-redline needs to be exhaustive. There is a judgment call about which deviations are worth addressing explicitly and which can be accepted. But that judgment call should be conscious — a decision to accept rather than an oversight. Teams with systematic deviation identification make that distinction more reliably than teams relying on unassisted reading under time pressure.
We're not saying that fewer negotiation rounds is always the goal. Some deals require extensive back-and-forth because the parties have genuinely different interests on material terms. The goal is to eliminate the extra rounds caused by redlines that left issues unaddressed, not the rounds caused by legitimate substantive disagreement.
What Baseline Numbers Look Like
For context, here are representative ranges based on what we see across early-stage and growing in-house teams processing commercial contracts at moderate volume (50-200 agreements per quarter):
- Intake to assignment: 2 hours to 3 business days, depending on intake structure. Best practice is under 4 hours.
- Assignment to first-redline on a standard NDA: 2 to 8 hours. Teams with playbook access and deviation-identification tooling are consistently at the lower end.
- Assignment to first-redline on a vendor MSA (30-50 pages): 4 hours to 3 business days. Median is around 1 business day.
- Negotiation round-trip time: 3 to 10 business days per round, dominated by counterparty response time. Legal team's internal turnaround on counter-proposals should be 1 business day or less.
- Total time-to-signature: 10 to 45 business days on vendor MSAs, depending heavily on counterparty responsiveness and number of negotiation rounds.
These ranges are illustrative, not industry benchmarks. The useful comparison is to your own historical data segmented by contract type, not to an external average that may reflect a different volume and complexity mix.
Setting Up the Measurement
The prerequisite for improving cycle time is measuring it. Specifically: capturing timestamped events at each stage transition, at the contract-type level, consistently. This requires an intake structure that logs receipt time, a routing mechanism that logs assignment time, and a mechanism for capturing first-redline send time.
Many teams have some of this in their CLM system, if they have one. Teams without a CLM — which includes most early-stage in-house legal functions — can capture it in spreadsheet form, though consistently doing so requires discipline. The minimum useful data set is: contract type, intake date/time, first-redline date/time, execution date/time, and number of negotiation rounds.
With three to six months of data segmented this way, a legal ops team can identify the specific stage or contract type driving overall cycle time, target process improvement at that stage, and measure whether the improvement has the intended effect. Without that data, improvement efforts are directional at best — the right intuition about where the problem is, but no way to confirm whether the fix worked.
The teams that improve consistently are the ones that close that feedback loop. Cycle time measurement is the mechanism that makes it possible.