THE SHORT ANSWER
Compare the revised contract with both the previous version and your list of requests. Mark each issue resolved, partial or missing using the actual wording. Then inspect other changes and confirm that the signing copy contains the agreed text and attachments.
The reply says, “All updated—please sign.” That is a useful starting point, but it does not tell you which requests were accepted or whether the new wording does what you meant.
You are checking two things: what changed between the documents, and whether those changes solve your problem. A document comparison helps with the first. Your original requests and a few realistic scenarios help with the second.
Keep three things beside you
Save the version you reviewed, the revised version and your email or notes listing the changes you requested. Give the files distinct names with dates. Keep the originals intact, including schedules and attachments.
If you only received a clean copy, ask for a version showing changes as well. You can also compare the two files yourself. Microsoft documents Word's comparison feature for supported desktop versions on Windows: it can show differences in a third document. Select the option to put changes in a new document so you preserve both source files.
With PDFs, check that your comparison covers tables, footnotes and attachments. If text is scanned or extracts badly, look at the pages themselves. A missing highlight is not evidence that wording stayed the same.
Build a request-to-wording table
Use one row per request. Copy the relevant wording or record its section and page; do not rely on “looks fine.” Here is a fictional example for a freelance project:
| What I requested | What the revision does | Status and next step |
|---|---|---|
| Payment within 14 days of invoice receipt | Says 14 days, but only after client acceptance | Partial: acceptance still controls the clock |
| Two rounds of revisions | Specifies two rounds in the scope | Resolved if no other clause adds unlimited changes |
| Ownership transfers after full payment | Ownership still transfers on delivery | Missing: ask for the ownership clause to change |
Add a fourth status, new issue, for a change you did not request. It may be sensible, but you still need to understand it. Keep “they agreed in an email” separate from “the signing document contains it.”
Test the apparent fix with an ordinary bad day
Consider this fictional revision:
Original: Payment is due within 30 days after acceptance of the deliverables.
Revised: Payment is due within 14 days after acceptance of the deliverables.
The number changed. Your actual concern, however, was waiting indefinitely for payment. If the agreement does not explain acceptance or put a limit on review time, the revision may leave that concern unresolved.
Ask: “If I deliver on Monday and nobody responds for three weeks, when does payment become due?” That question reveals more than checking whether “30” became “14.”
Try the same method elsewhere. If you requested remote work, can you tell what happens when a manager changes? If you requested a cancellation right, can you tell what you would owe after using it? These are reading exercises, not conclusions about enforceability.
Read around the edited sentence
Follow definitions and cross-references. A shorter payment period may depend on a newly defined “approved invoice.” A cancellation right may be offset by a fee elsewhere. An exception for your side project may omit the separate outside-work permission requirement.
Also inspect changes outside your request list: parties, dates, prices, renewal, notice methods, liability, schedules and signature pages. Some will be harmless formatting. Others can change the deal. Do not reject an edit simply because it is new; record its consequence.
Send one precise follow-up
Adapt this fictional email:
Thanks for the revision. The two-round limit now matches my request. The payment change is only partly resolved: clause 6 still starts the clock at acceptance, and I cannot find an acceptance deadline. Could we agree when acceptance occurs and when payment is due if no feedback arrives? The ownership change also appears missing from clause 9. Please send the updated clean copy and a version showing changes.
This acknowledges what was fixed and names what remains open. If the other side intentionally declined a request, you can decide whether that tradeoff is acceptable instead of treating it as an editing mistake.
Review the final document in context
Contracts.money reviews one PDF or DOCX and emails AI analysis. It does not automatically compare two versions. You can submit the revised document with context such as:
I am the freelancer. This is the revised agreement.
My requested outcomes were: [list outcomes].
Read this document for wording that supports or conflicts with them.
Quote relevant passages. Identify anything you cannot establish.
The previous version is not included; do not infer what changed.
Use the result alongside your comparison, not as proof that every edit was found. Before signing, open the actual signing copy and confirm the wording, schedules and version match what you reviewed. Keep the executed copy afterwards.
For the earlier stage, see checking a freelance contract before starting work. If a remaining issue needs a focused professional opinion, use the short lawyer-call brief.
Put your own contract in context.
PDF or DOCX. Your priorities. An AI review delivered by email.
Review my contract · $1