Direct answer

Signing theirs is normal. Check every clause against what the job record will have to prove later.

Most larger clients will not sign a freelancer's contract. They have their own paperwork, their own procurement process, and a legal team that wrote it, and being asked to sign the client's contract instead of using yours is the ordinary shape of serious work, not a warning sign by itself. The risk is not whose document it is. The risk is signing a document whose promises you have not translated into the facts your work will have to produce. Every contract clause eventually becomes a question about a record: what counts as delivered, who accepted it, when the payment clock started, what a change cost and who approved it. If the clause names a proof you cannot produce, or leaves the decisive fact to someone's memory, the clause is where your dispute will live later, whatever the fee line says. This page gives you the clause by clause check, run in the order the job will test it, the small set of clauses worth proposing back, and the reply that raises them as a professional rather than an obstacle.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated November 21, 2026. First published November 21, 2026. The records quoted below are real and public, read back from the live service on November 21, 2026.

Step 1. Read for proof, not just for money: every clause becomes a record question

Read the contract once through with a single question in hand: for each promise, what fact would settle it, and where will that fact live? The fee clause settles on the invoice and the payment record. The delivery clause settles on whatever proves the work was handed over, complete, on a date. The acceptance clause settles on a decision, by a named person, by a stated time, or it settles on silence, which settles nothing. The changes clause settles on the trail of who asked for what, when, and at what agreed price. Reading this way reorganises the document quickly: most clauses in a standard client contract are harmless boilerplate that will never be tested, and a small number, usually delivery, acceptance, payment, changes, ownership, and exit, carry the whole practical risk of the job. Those are the clauses this check works through, in the order the job will meet them. Anything you cannot map to a fact you can produce is a flag, not necessarily a refusal, but a point to clarify in writing before you sign, while clarifying is still cheap and friendly.

Step 2. Check delivery and acceptance first: what counts as delivered, who decides, by when

Delivery first. Find the words that say what delivery consists of: the files, the access, the report, the handover. The clause you want names a concrete event, the work handed over in a stated form, ideally a delivery record or link both sides can open, rather than a vague standard like satisfactory completion, which makes delivery a feeling the client reports later. Then acceptance, the clause that decides whether delivery counted. Check four facts: who accepts, a named role rather than the client in the abstract; how they accept, in writing or through a stated system, not verbally on a call; by when, a stated number of days after delivery, because an open ended review period is an open ended payment delay; and what silence means, where the fair standard is that work not flagged within the window counts as accepted, so a busy client cannot pause your payment by never getting round to review. Also check what a flag must contain: a specific list of what falls short of the brief, against which you fix and redeliver, rather than a general right to reject and restart. Each missing fact is a sentence to propose in step 5, and each is a sentence reasonable clients accept readily, because a clear acceptance clause protects their side too.

Step 3. Check the payment trigger and the change pricing: what starts the clock, what a change costs

Payment next. Find the exact event that starts the payment clock: it should be acceptance, or delivery where no acceptance step exists, tied to a stated number of days, and it should not depend on events outside your sight, like the client's own invoicing run, their client's payment to them, or an internal approval chain with no outer date. Where a trigger like that appears, the fix to propose is an outer limit: payable within a stated number of days of acceptance at the latest, whatever the internal steps. Check also what the contract does with a disputed invoice: the fair shape is that the undisputed part is paid on time and only the disputed line waits, rather than the whole payment pausing over one questioned item. Then changes, the clause most likely to be used on a real job. It should say how a change is requested, that its effect on price and delivery date is stated and agreed before work on it begins, and that instructions from anyone other than the named contact are not changes until that contact confirms them. A contract silent on changes defaults you to the worst process: do the extra work first, argue about its price at the end, with the record of the request scattered across threads. Finally scan ownership and exit quickly: rights in the work should transfer on payment, not on delivery, and either side should be able to end the job with work done to date settled from the record, rather than a clause that strands finished work unpaid.

Step 4. See acceptance as a record state, the thing the clauses are describing

The acceptance and payment clauses are not abstractions: on a recorded job they describe visible states, and seeing the states makes the clause check concrete. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the states a delivery moves through:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

Read the accepted record against the clauses you just checked: status accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release state ok_to_release, 4 steps checked. A named decider, a decision, a date, and a release state that tells the payment side the trigger event has happened: that is an acceptance clause working exactly as written. The pending record shows why the by when and silence facts matter: 5 steps checked, release state hold, delivered work sitting in a state that only a decision can move. A contract that names no decider and no window leaves work in that hold indefinitely, with the fee behind it. When you propose the clarifying sentences in step 5, this is the picture to describe, briefly and without drama: the clause should produce a decider, a date, and a state, because that is what releases payment fairly for both sides.

Step 5. Propose the few sentences back, in one short professional reply

Do not redline the whole document and do not send a rival contract back. Send one short reply that accepts their contract as the base and proposes the small set of clarifying sentences your check flagged, each tied to a practical reason a procurement reader recognises. The shape: Happy to work on your contract. Four clarifications so delivery and payment run cleanly on both sides. One, delivery is the handover record at [the link or system], so both sides can see what was delivered and when. Two, acceptance by [named role] within [number] business days of delivery, with points flagged in writing against the brief, and work not flagged in the window counted as accepted. Three, payment within [number] days of acceptance, with any undisputed part of an invoice paid on time. Four, changes are priced and agreed in writing before work on them begins. Each sentence is ordinary, each protects the client as much as you, and together they convert the contract from a document you hope behaves into one whose key facts will exist on a record. A client who refuses all four has told you, before the job starts, that they want the decisive facts left unsettled, and that is the moment to price the risk, shrink the first stage, or walk away with full information.

Honest limits

This page is general information about reading a client contract, not legal advice: liability caps, indemnities, insurance duties, tax status, and industry regulation can each outweigh everything in this check, and a large, long, or regulated engagement deserves a lawyer's read for your situation before you sign. The check here covers the clauses that decide how delivery, acceptance, payment, and changes will be proven in practice; it does not certify the rest of the document as safe. Signing the client's contract is normal and often unavoidable with larger organisations, and nothing here argues for refusing it as a matter of pride. A verifiable receipt proves the saved result was not changed since it was saved; it does not interpret a contract, which is why the clauses themselves must name the decider, the window, and the trigger in words.

Step 6. Keep your own short terms ready as the source of your clarifications

The reason this check runs in an hour rather than a week is that your clarifications already exist, written once, in your own standard terms. Even when a client will never sign your document, your terms remain the checklist theirs is measured against: delivery defined, acceptance window, payment trigger with an outer date, changes priced before work, rights transferring on payment, exit settled from the record. Maintain that short document as your working standard, lift the clarifying sentences from it into the reply in step 5, and each new client contract becomes a comparison exercise instead of a fresh legal education. Over time the pattern compounds in your favour: clients who accept clear clauses self select into the jobs that run cleanly, the record proves the facts the clauses name, and the contract, whoever drafted it, ends up describing a job both sides can actually settle from evidence if they ever disagree.

Frequently asked questions

My client wants me to sign their contract instead of using mine. What should I check?

Check it clause by clause against what the job record will have to prove later. Delivery: what concrete event counts as delivered, ideally a delivery record both sides can open, not a vague satisfaction standard. Acceptance: who decides, a named role, in writing, within a stated number of days, with flagged points listed against the brief, and work not flagged in the window counted as accepted. Payment: the exact event that starts the clock, normally acceptance, a stated number of days, an outer limit where internal steps are involved, and the undisputed part of any invoice paid on time. Changes: requested in writing, priced with their effect on the delivery date, and agreed before work on them begins. Then ownership transferring on payment, and an exit that settles work done to date from the record.

Is it a red flag when a client insists on their own contract?

By itself, no. Larger organisations route all suppliers through their own paperwork, and refusing it on principle would exclude most serious clients. The flags are inside the document and in the negotiation, not in whose name is on the front page. Watch for acceptance with no named decider and no time window, a payment trigger tied to events you cannot see with no outer date, silence on how changes are priced, and rights in the work transferring before payment lands. The second flag is the response to reasonable clarifications: a client who accepts clear delivery, acceptance, and payment sentences is showing you a well run process, and a client who insists every decisive fact stay vague is showing you something else, in time to act on it.

Which clauses matter most if I only have an hour to check?

Four, in this order. Acceptance, because it decides whether delivery counted and starts everything else: decider, writing, window, and the meaning of silence. Payment trigger, because it decides when the clock starts and whether anything outside your sight can pause it. Changes, because it will certainly be used: priced and agreed before work begins, or argued about afterwards. Delivery definition, because every later question refers back to what was handed over and when. Liability, indemnity, and insurance clauses can matter more in money terms on a large engagement, and those are the ones to give a lawyer rather than a fast read, which is exactly why the four operational clauses are the right use of your own hour.

What do I do if their contract conflicts with my own terms?

Expect it, and resolve it on purpose rather than by accident. Most client contracts state that their document governs, which means your terms do not ride along silently, so anything in your terms that matters must be lifted into the signed document as a clarification or an added sentence, or it does not exist for this job. Work the conflicts in order of consequence: where their payment days are longer, price or stage the work for the longer wait, or propose your outer date; where their acceptance process is heavier, build its window into your delivery dates; where their change process is looser, propose the priced before work sentence. A conflict you have seen and priced is a business decision. A conflict you never noticed is a surprise scheduled for the end of the job.

How does a job record help when I sign a client's contract?

It produces, as the work happens, exactly the facts their clauses will ask about: what was delivered and when, which steps were checked, who accepted, on what date, and what state payment is in. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so acceptance reads as a recorded decision with a decider and a date, not a recollection. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run the job on one record, so the delivery their contract describes is provable from the first stage: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.

Related