Master Service Agreements are foundational documents. They govern the terms under which a vendor relationship operates for years — sometimes indefinitely, through multiple order forms and amendments. A poorly reviewed MSA is a risk that compounds over time, with every order form that gets executed under it.
Most legal teams would say their MSA review process works fine. Most of them are wrong, and the signs are recognizable if you know what to look for. These aren't hypothetical warning flags — they're patterns we see consistently in legal teams that come to us after something has gone sideways.
Sign 1: Associates Are Spending More Than 2.5 Hours Per Standard MSA
A standard inbound vendor MSA — 20 to 35 pages, no exotic provisions, off a recognized technology vendor's paper — should take a trained associate 1.5 to 2.5 hours to review thoroughly and produce redlines on. That range assumes the associate has access to a current playbook and a clear understanding of the company's risk tolerance by contract category.
When review time consistently runs above that range, there are usually one of three causes: the associate is doing context research that should have been done during intake (who is this vendor, what's the commercial value, what's the risk tier), the associate is wrestling with playbook ambiguity (what's our actual position on this clause type?), or the associate is reading the document more than once because they're uncertain about their first pass. All three are process problems, not associate skill problems.
The benchmark matters because time overrun on MSAs tends to cascade. If MSA review is taking four hours when it should take two, the associate's daily and weekly capacity is materially constrained, other reviews get delayed or rushed, and the queue builds. The hourly cost of contract review for a fully-loaded associate is meaningful — consistent overrun on commodity MSAs represents real budget impact, not just schedule friction.
Sign 2: Partners Are Re-Reviewing Associate Redlines and Consistently Finding Issues
Partner or GC review of associate work product is normal and appropriate for high-stakes agreements. It's a problem when it becomes a consistent quality control function rather than a light-touch sign-off. If a partner re-reviews associate MSA redlines and regularly identifies missed clauses, incorrect fallback positions, or overlooked non-standard provisions, the review quality problem has to be traced upstream — it's not getting fixed by reviewing more carefully at the partner level.
Consistent partner findings typically indicate one of three things: the associate training on the specific contract type is insufficient, the playbook guidance for that contract type is too abstract to be reliably applied, or the associate is reviewing under time pressure that degrades quality. The third is the most common and the hardest to fix because it's structural rather than individual. Pressure-driven quality degradation in commodity review is a workload problem, not a performance problem.
We're not suggesting partner re-review should be eliminated — for material agreements, senior oversight adds genuine value. What we are suggesting is that when partner re-review consistently turns up the same categories of issues, that pattern is telling you something specific about where your process is weak.
Sign 3: Your Fallback Positions Are Held in Attorneys' Heads, Not in Documents
This one is easier to identify than people expect. Ask your associates: what's our acceptable fallback on mutual limitation of liability caps for a mid-tier SaaS vendor? What's our minimum acceptable cure period before termination for cause? What's the threshold contract value at which IP indemnification carve-outs are required?
If the answers are "I'd have to ask [senior person]" or "it depends on the deal" without further specificity, your fallback positions are institutionally held rather than institutionally documented. That's not inherently wrong — experienced legal teams carry a lot of legitimate judgment — but it creates fragility. When that senior person is out, or on a larger deal, or the team grows, consistency degrades. Every associate ends up negotiating from their own calibration rather than from a shared standard, and you end up with materially different outcomes on structurally similar contracts.
Sign 4: You've Had a Post-Signature Surprise More Than Once
One post-signature surprise is an edge case — a provision that was read correctly but whose implications weren't anticipated given the specific facts that later arose. Two or more post-signature surprises on MSAs reviewed by your team in the past 24 months is a pattern worth examining.
The most common sources: auto-renewal provisions with notice windows shorter than the organization's procurement cycle (the contract renewed before anyone noticed), liability carve-outs that seemed theoretical but became relevant when the vendor's performance degraded, and governing law provisions that created forum or choice-of-law problems that weren't apparent at signing. All three of these are detectable during review. Their appearance as post-signature surprises means the review process didn't catch them.
The diagnostic question after a post-signature surprise isn't just "why did this happen" but "would our process catch this the next time?" If the answer is "probably not," the surprise has revealed a gap in your review checklist or your playbook that needs to be closed before the next similar contract goes through.
Sign 5: No One Can Tell You How Long the Typical MSA Takes to Close
This is a workflow visibility problem, and it's more common than most legal teams want to admit. If you can't answer, with reasonable accuracy, what the median time from intake to signed MSA is for your team — broken down by contract type, counterparty size, and complexity tier — you don't have visibility into where your process is slow.
Lack of visibility makes improvement impossible. If you don't know that SaaS vendor MSAs over $200K consistently take three weeks longer than those under $200K, you can't investigate why. If you don't know that the average internal review time is 4.5 days but the average wait time for business-side response to redlines is 11 days, you don't know whether your bottleneck is internal or external. You're guessing at improvements to a process you can't see.
The instrumentation doesn't need to be elaborate — a simple intake log with timestamps for key milestones (received, first review complete, redlines sent, counterparty response received, signed) will give you enough data to identify where time accumulates. Legal teams that run this for 60 days almost universally find their bottleneck is somewhere they weren't expecting.
Each of these signs points to a process architecture problem, not a competence problem. The attorneys on your team are capable. The review process may not be giving them the structure, clarity, and information they need to perform at the level their competence would otherwise allow. That's the gap worth closing.
