How to review a vendor agreement before it reaches outside counsel

Start with the deal, not the boilerplate

Before reading clause by clause, write down what the business believes it is buying: the service, the price, the start date, the renewal model, the implementation promise, and the internal owner. That short commercial brief gives the later review a reference point.

This first step also exposes a common handoff problem. The agreement may describe a three-year commitment while the internal approval assumes one year, or the order form may promise a launch date that the main agreement never mentions. Recording the expected deal makes those mismatches visible without pretending to decide their legal effect.

• Name the business owner and the operational owner.
• Record the expected price, term, renewal, and implementation date.
• List the systems, data, or customer workflows the vendor will touch.
• Note the deadline and the reason it matters.

Build a clause map with source references

Next, organize the agreement into the clauses your team routinely needs to find: payment, term and renewal, termination, service levels, data handling, confidentiality, indemnity, liability, insurance, assignment, publicity, and governing terms. The useful artifact is not just a label. It is the label plus the exact span in the source document.

Source references change the quality of the conversation. A note that says “liability looks low” forces the next reviewer to search the document again. A note that identifies the limitation-of-liability clause, quotes the relevant sentence, and points to its location lets counsel verify the issue immediately.

• Keep quoted language short enough to verify in context.
• Capture section labels and exact source locations.
• Mark clauses that are missing instead of silently treating them as acceptable.
• Keep related order forms, exhibits, and policies in the same review set.

Compare the agreement to an approved playbook

A company playbook turns institutional preferences into a repeatable review checklist. It can identify the language your team normally accepts, the issues that require escalation, and the fallback language counsel has already approved. The comparison should remain explicit: show the agreement language, the playbook expectation, and the reason the item was flagged.

The playbook is a routing tool, not a substitute for judgment. A deviation may be commercially acceptable in one deal and unacceptable in another. The value is that the decision is made consciously and by the right person, rather than disappearing inside a long document.

• Separate high-impact exceptions from routine cleanup.
• Identify the internal decision owner for each open issue.
• Use approved fallback language only when its source and status are clear.
• Preserve uncertainty instead of forcing every clause into a confident answer.

Turn findings into questions counsel can answer

The strongest handoff converts observations into bounded questions. Instead of “please review the contract,” ask whether a specific clause covers the business scenario, whether a proposed fallback fits this deal, or what risk remains if the business accepts the counterparty position.

Each question should travel with its source excerpt, the relevant playbook rule, the business context, and the person who can make the commercial decision. Counsel can then spend time on judgment rather than reconstructing the deal from email.

• What decision does the business need to make?
• Which source language created the question?
• What position does the playbook normally take?
• Who has authority to accept the remaining risk?

Close the loop with a review packet

A useful review packet is compact enough to act on and complete enough to audit later. It should include the commercial brief, the document version, the prioritized findings, source-linked excerpts, open questions, decisions, and the final owner of each follow-up.

CounselOS is built around this handoff. Clause extracts remain linked to the contract, playbook deviations stay visible, questions are captured beside the issue that raised them, and the review can be exported as an attorney-ready packet. The software organizes the evidence; people keep control of the legal and business decisions.