Before paying for contract review: decide what you need reviewed

Two people can ask for “contract review” and mean very different work. One wants a plain-language conversation before signing. Another wants revised language, negotiation support and a final comparison after the other party responds. A third is already in a disagreement under a signed agreement. Comparing a price before comparing the work can leave all three with the wrong expectation.

This guide helps a prospective client prepare for a scope conversation. It does not interpret an agreement, recommend a negotiating position, quote a fee or establish McAdoo Legal's availability. The right engagement depends on the documents, parties, jurisdiction, timing, business objective and requested result. A planning description or fee, if one is ever published, should not be treated as a promise that every version of a problem is included.

The useful question is not simply, “How much does a contract review cost?” It is, “What decision am I trying to make, what material must be examined and what deliverable would help me make that decision?” A clear answer gives counsel a better basis for assessing scope and gives the client a better basis for understanding the service.

Start with the decision, not the page count

Before counting pages, write one sentence describing the decision in front of you. Examples might include deciding whether to sign, identifying points to negotiate, documenting an agreed business arrangement, comparing a revised draft or understanding obligations in an agreement that is already in effect. These are not interchangeable requests.

Then describe what happens if no decision is made. Is a vendor waiting to start work? Is a lease proposal tied to a location plan? Is a customer asking for a response? Is an internal team unable to proceed? This operational context does not determine the legal answer, but it helps explain why the review matters and which issues need attention first.

Page count still belongs in the intake. It is a practical indicator of volume, not a measure of legal importance. A short agreement can incorporate lengthy online policies, specifications or prior documents. A long agreement may contain repeated exhibits. One sentence can carry a major business consequence, while several pages may be administrative detail. Record the page count, but do not let it stand in for a document inventory or a description of the transaction.

Identify the complete document set

Begin with the main agreement and every item it refers to: schedules, statements of work, exhibits, specifications, order forms, policies, amendments, guarantees and prior versions that remain relevant. Note whether each item is a proposal, an unsigned draft, an executed agreement or a later amendment. If terms appear at a website address, preserve the version you received and the date you accessed it. Do not assume a lawyer can reconstruct the package from a single attachment.

Create a simple index with five columns: document name, date or version, status, source and why it matters. “Source” might identify who sent it or where it was downloaded. “Why it matters” can be a short note such as pricing schedule, service description, data terms or prior amendment. The index is an organizational aid; it is not a conclusion about which document controls.

Avoid renaming files so aggressively that their origin becomes unclear. A folder full of files named “final,” “final2” and “really-final” creates avoidable uncertainty. Preserve original files where possible, make working copies if needed and record which file the other party currently treats as the active draft.

Prepare a transaction snapshot

The document does not always explain the real transaction. Prepare a one-page snapshot with the parties' full names, the proposed exchange, the expected start and end, the people responsible for performance, the locations involved and the major dependencies. If a signing party uses a trade name, subsidiary or parent company, record the names as they appear in the documents without guessing which entity should sign.

Include the economic structure in neutral terms: fixed amount, recurring charge, usage-based amount, deposit, reimbursement or other arrangement. List important non-cash commitments, such as exclusivity, access to systems, use of a brand, staffing, reporting or delivery of data. This is not a substitute for reviewing the payment provisions. It helps counsel compare the written document with the business's understanding.

Also identify what is still undecided. A client who has not chosen a service level, delivery date or termination approach should say so. Legal drafting cannot reliably fill an unresolved business choice. Separating decided points from open points prevents a draft from becoming an accidental substitute for the business's own decision-making.

Name the requested output

“Please review this” does not describe a deliverable. Consider whether you want an issue-spotting conversation, written comments, a clause-by-clause explanation, a prioritized risk list, a redline, replacement language, a revised agreement, help preparing for negotiation or a comparison of the final draft against an earlier version. Ask which output is included and how it will be delivered.

An explanation of existing language is different work from proposing language that fits the transaction. A redline is different from participating in calls with the other party. Reviewing one draft is different from following the document through several negotiation rounds. A written summary may be useful for an internal team, while a live discussion may be enough for a narrow decision. The engagement should identify the output that matches the actual need.

Describe whether the other party expects changes. An agreement presented as standard or nonnegotiable may still require careful assessment, but the practical objective can differ from a document being negotiated collaboratively. If the business has bargaining constraints—such as a required launch date or a vendor that will not change certain terms—state those constraints. Counsel can then distinguish issues that call for proposed language from issues that call for a business decision or another safeguard.

Separate business priorities from legal analysis

Write down the result the business needs, the limits it cannot exceed and the risks it is prepared to accept. Common business dimensions include price, performance, time, quality, exit options, implementation effort, customer commitments and dependence on a particular supplier. This inventory does not answer a legal question; it gives the legal review a usable frame.

Rank priorities rather than labeling everything “critical.” A short list might use three categories: must resolve before signing, should improve if practical and acceptable only with an understood operational plan. The attorney may identify different legal concerns after review. The client's ranking still helps expose where a theoretically favorable clause would conflict with the business's actual operations.

Do not ask a lawyer to infer the company's capacity from the document alone. If the agreement promises twenty-four-hour support, a specific delivery window, particular insurance or a technical control, identify who can confirm whether the business can perform it. Legal review and operational validation support each other, but they are not the same task.

Map money, performance, time and exit

A useful preparation pass follows four practical paths through the agreement.

First, trace the money: what is paid, when, based on which event, with which adjustments and with what supporting records. Second, trace performance: who does what, what counts as completion and who accepts the result. Third, trace time: start dates, milestones, renewal mechanics and notice events. Fourth, trace exit: what happens when the relationship ends, including unfinished work, data, property, access, transition help and outstanding payments.

This is not a method for deciding the meaning or enforceability of the provisions. It is a way to identify questions and missing business facts before the legal conversation. When an item is unclear, quote or point to the relevant section and describe the practical question. Avoid rewriting the agreement in your own words as if your summary were authoritative.

Add a data and technology inventory when relevant

If the arrangement involves customer information, employee information, credentials, business records, software access or system integrations, include a short data map. List what information will be shared, who can access it, where the parties expect it to move and what should happen to it when the relationship ends.

The Federal Trade Commission's business guide recommends taking stock of personal information and understanding where it is kept and who has access. [2] That general inventory principle can improve contract-review preparation. It does not establish that a particular agreement complies with any privacy or security requirement, and it does not replace advice about the laws or standards that may apply.

Record known technical dependencies as facts. For example: the vendor will connect to a named system, administrators will receive accounts, files will be exported in a specified format or a subcontractor will perform part of the service. Do not label a system secure or compliant without an appropriate assessment. The point is to make the information flow visible enough for counsel and technical reviewers to ask better questions.

Confirm names, roles and signing authority

Prepare the legal names exactly as they appear in the draft and in the business's organizational records. Identify trade names separately. Note which person has been negotiating, which person will manage performance and which person is expected to sign. If authority is uncertain, flag it for internal confirmation and legal review rather than guessing.

Names matter beyond the signature block. A proposal may name one company while the agreement names an affiliate. An order form may use an abbreviated name. A guarantee may involve an individual. Collect the evidence and identify the mismatch; do not silently “fix” it in a working draft.

The same discipline applies to the other party. Record what the documents say, what invoices or proposals say and any discrepancy you have noticed. The attorney can determine what additional verification is appropriate within the engagement.

Explain the negotiation posture

Counsel needs to know where the conversation stands. Has anyone accepted terms by email? Has work started? Has a deposit been paid? Has the other party sent a deadline or described certain language as nonnegotiable? Has the client already proposed edits? Preserve the communications that answer these questions.

Avoid overstating urgency. Give the actual requested response date, the source of that date and any operational consequences. Do not promise the other party a lawyer's turnaround before availability and scope have been confirmed. If a matter is time-sensitive, say so at first contact and ask what work is realistically possible.

Negotiation support can also have multiple boundaries. The client may want talking points but intend to lead the discussion, or may want counsel to communicate directly after an engagement is established. Those approaches require different preparation and may involve different scope, timing and cost. Make the expectation explicit.

Build an included-and-excluded scope matrix

A scope conversation becomes clearer when it names both what is included and what is not. A simple matrix can list the document set, issues, deliverables, communication and number of anticipated revisions. For each row, mark included, excluded or to be determined. This is a discussion tool, not the engagement agreement itself.

Possible exclusions might include tax advice, insurance adequacy, accounting treatment, technical specifications, employment classification, title review, litigation, regulatory approvals or advice about another jurisdiction. Whether any of these matters is relevant depends on the transaction. Some questions may require another professional or a separate engagement.

Ask how newly discovered issues will be handled. A review may reveal that an incorporated policy was missing, that another entity is involved or that a specialized question falls outside the planned work. A clear process for pausing, expanding or referring the issue is more useful than assuming every concern belongs inside the original price.

Organize the supporting business records

The IRS recordkeeping page explains in general terms that a business should keep records that support items shown on its tax returns. [1] This guide cites that page only for the broad value of organized business records, not as a contract-review rule, retention instruction or source of transaction-specific tax advice.

For contract-review preparation, supporting records may include the proposal, pricing worksheet, specification, implementation plan, insurance information, earlier agreement, invoice assumptions and communications that show what the parties discussed. Keep originals intact and identify which records reflect tentative ideas rather than agreed terms.

Do not flood an unsecured channel with every record the business has. Start with an index and follow the firm's instructions for secure transmission. Remove unrelated personal or confidential information only when doing so will not damage the relevant record; if uncertain, ask how the material should be handled. Do not send credentials or access keys in a contract-review request.

Distinguish review, drafting, negotiation and dispute work

Four requests that sound similar can require materially different work.

A review examines an existing document for a defined decision. Drafting creates or substantially restructures language for a transaction. Negotiation support addresses proposals and responses between parties. Dispute work concerns a disagreement, threatened claim or alleged breach under an existing relationship. A matter can move from one category to another, but the shift should be recognized rather than hidden inside the phrase “one more quick question.”

If the agreement has already been signed or performance has begun, say so at the start. If a demand, complaint or court paper exists, identify it without relying on this guide to calculate a deadline. Those circumstances can change priority, conflicts analysis, preservation needs and the appropriate type of representation.

Control versions through the final decision

Contract work is vulnerable to version confusion. Maintain one folder or controlled workspace, preserve incoming files and record when a working copy is sent. When a revised draft arrives, compare it with the last reviewed version before relying on prior comments. Do not assume tracked changes reveal every difference.

Ask whether the planned engagement includes review of a later draft and, if so, how many rounds or what kind of comparison. A marked-up old draft is not necessarily a review of the document ultimately signed. Before signature, confirm that the execution copy is the version the decision-makers intended to approve and identify any attachments that must accompany it.

After signing, preserve the completed agreement and its exhibits in a location the responsible team can access. Record operational dates and ownership separately, but do not reduce the agreement to a calendar entry. A renewal reminder is useful only if the underlying document and responsible decision-maker can be found.

Ask fee questions that expose scope

A useful fee conversation connects the proposed charge to the work. Ask which documents and versions are included, which deliverable will be produced, whether a meeting is included, how revisions are treated and what happens if the scope changes. Ask who will perform the work and what information must arrive before the review can begin.

Do not compare a fixed amount, estimate or hourly arrangement without comparing assumptions. One proposal may cover only an initial review; another may include a redline and follow-up. A lower number tied to the wrong deliverable is not necessarily a better fit. Conversely, a broad engagement may be unnecessary when the client has a narrow, well-defined question.

This guide does not state that McAdoo Legal offers any particular fee structure. Any actual service, fee, timing and payment terms must be confirmed through the firm's approved process and engagement documentation.

Create a one-page scope brief

Before contacting counsel, assemble a one-page brief with these headings:

• Decision: what must be decided or accomplished.
• Parties: full names and roles, including known affiliates or guarantors.
• Document set: main draft, attachments, incorporated terms and relevant earlier agreements.
• Status: proposed, under negotiation, signed, amended or disputed.
• Timing: actual requested response date and its source.
• Business priorities: the few outcomes that matter most.
• Requested output: conversation, written issue list, redline, drafting, negotiation support or final comparison.
• Open facts: decisions or records still missing.
• Special subjects: data, property, licensing, regulated work or other areas that may require additional review.
• Secure handoff: which materials are ready and how they will be transmitted after instructions are received.

Keep the brief factual. It should help the attorney identify scope, not argue the outcome or conceal inconvenient information.

A fictional preparation example

Imagine a small business considering a vendor agreement for a new customer-management system. Its first request says only, “Can you review this twenty-page contract?” That leaves unanswered whether the work includes an online privacy policy, an order form, implementation services, data migration or several rounds of edits.

A better request identifies the current draft and attachments, the target start date, the signing entities, the data expected to move, the business's three priorities and the requested output: an issue list and one redline, followed by a comparison if the vendor returns a revised version. It also notes that the business has not decided how long it needs post-termination access to exported data.

The improved request does not predetermine the legal advice. It exposes the real decision, the missing business choice and the boundaries that need to be confirmed. Counsel can then assess whether that proposed scope is appropriate and whether any specialized issue or additional document changes the plan.

End with ownership of the next step

A useful scope agreement identifies what counsel will examine, what counsel will provide, what the client must supply, who owns each follow-up and how additional work will be addressed. It should also identify the communication channel and the conditions that must be satisfied before work begins.

The goal is not simply a document covered in colored edits. The goal is a better-informed decision supported by the right records, the right reviewers and a clearly defined professional task. When the decision, document set, output, exclusions and next step are explicit, the fee becomes easier to understand because the service itself is easier to understand.