How to Create and Sign Freelance Contracts with PayShield

Handshake deals do not hold up. Neither does "we agreed over email" when a client disputes a scope change at invoice time, stalls on payment, or disappears after you've delivered the work. A signed contract is not bureaucracy — it's the document that determines whether you have legal standing to charge interest, send a demand letter, or walk into small claims court with a winnable case.

More practically: a contract sets expectations so clearly that most disputes never happen in the first place. When a client knows from day one that revisions beyond two rounds cost extra, that IP does not transfer until final payment clears, and that late invoices accrue a 1.5% monthly fee — they pay differently. Not because they feared you, but because you ran a professional operation and they could see it.

This walkthrough covers everything inside PayShield's contract module: creating a contract from scratch, working with the built-in clauses, getting an AI plain-language summary before sending, collecting e-signatures through DocuSign, and tracking the full lifecycle. For the clause-by-clause legal deep dive — what each clause actually says and why — see the freelance contract template guide.

Creating a contract

Go to Contracts in the left navigation and click New. The contract builder opens with three required decisions before you write a single clause: contract type, linked client, and basic commercial terms.

Contract type

PayShield supports three contract structures:

Fixed-price is the right choice when scope is well-defined up front and you can quote a single number. You deliver a specified output, the client pays that number. Simple. The risk is scope creep — which is exactly why a scope lock clause matters more in fixed-price contracts than anywhere else.

Milestone-based breaks a larger project into stages, each with its own deliverable and payment trigger. Use it when a project runs longer than four to six weeks, when the client needs visible checkpoints, or when you want to reduce your exposure to non-payment by keeping outstanding balances smaller at any given time. Each milestone gets its own payment terms, and the escalation engine can treat each one independently.

Retainer is a recurring engagement — a monthly fee for an ongoing scope or a reserved block of hours. PayShield handles the invoice cadence automatically once you set the billing cycle, rate, and start date.

Linking to a client and defining commercial terms

Once you pick the type, link the contract to an existing client record. If the client does not exist yet, create them from this screen.

Then define:

• Scope description — what you will deliver, stated as specifically as possible
• Payment terms — enter your terms as free text (e.g. Net 7, Net 14, Net 30)
• Late fee terms — the percentage or flat fee applied to overdue invoices
• Currency — set once at the contract level; all invoices under this contract inherit it

The payment terms and late fee you set here are not just record-keeping. They are what PayShield's payment escalation engine reads when it decides when to send reminders, when to escalate tone, and what amounts to reference in demand letters. If you leave these blank, the engine has nothing to enforce. Fill them in.

Starting from a proposal

If you already accepted a proposal in PayShield, the contract is created automatically with scope and payment terms pre-populated from the proposal. You only need to add clauses and send it for signature. See the full proposals walkthrough if you have not yet set up that part of your workflow.

Built-in contract clauses (Pro)

After you save the basic contract structure, you land in the clause editor. This is where the contract goes from a payment record to an actual legal document. PayShield Pro includes contract templates with five standard clauses that cover the most common protection points in a freelance engagement.

Kill fee

A kill fee is what happens when a client cancels mid-project. Without one, you have delivered work, blocked time, turned down other projects, and your only option is to argue for the value of work completed — a fight you will often lose.

With a kill fee clause, the contract specifies a percentage of the remaining scope owed if the client terminates. A common structure is 25% of the total contract value if cancelled before midpoint, 50% if cancelled after. PayShield's pre-built kill fee clause includes these percentages as editable defaults, plus the notice period required before termination takes effect.

Revision cap

Every fixed-scope project should have a defined number of revision rounds. Open-ended revisions are how projects that were supposed to take six weeks take four months. The clause states how many rounds are included (typically two), what constitutes a "round" versus a minor correction, and what the charge is for additional rounds.

Once you have a revision cap in the contract, scope creep conversations become easy. When the client asks for their fifth round of changes, you are not pushing back on a preference — you are enforcing a written term they signed.

Scope lock

Scope lock is the companion to the revision cap. Where the revision cap governs iterations on agreed work, scope lock governs new work that falls outside the original brief. The clause defines what is explicitly in scope, what is explicitly out of scope, and the change-order process for anything that emerges mid-project.

A signed change order is a mini-contract. PayShield lets you create change orders linked to the parent contract so everything stays in one place.

IP transfer

This clause makes IP transfer conditional on full payment. Until the final invoice is paid, the client holds a limited, non-exclusive license to use the deliverables — but you retain ownership. Once final payment clears, ownership transfers.

The practical effect: if a client refuses to pay the final invoice but has already deployed your work, they are now using IP they do not own. That changes the legal conversation significantly and often resolves non-payment faster than a demand letter alone.

NDA

The mutual non-disclosure clause is standard for most professional engagements. It restricts both sides from disclosing confidential information received during the project — client business data on your side, your methods and pricing on theirs. The clause includes a definition of what counts as confidential, exclusions (publicly available information, independently developed information), and the duration of the obligation.

Customising the clauses

Each built-in clause is editable — you can adjust the percentages, thresholds, and notice periods to match your standard terms. If you have unique requirements not covered by the standard set, you can add them in the free-text section of the contract editor.

AI contract summaries (Pro)

Before you send a contract to a client, PayShield Pro can generate a plain-language summary of the full document. The summary translates each clause into a short, non-legal explanation — what it means for the client, not what it says in legal language.

This is useful in two specific situations.

The first is when your client is a non-technical person who is not used to reading formal contracts. Sending them a dense legal document with no context creates friction — they feel like they are supposed to get a lawyer before signing a $3,000 project agreement, and that is not what either of you wants. A plain-language summary lets them understand what they are agreeing to and sign with confidence.

The second is when you want to catch any ambiguity before the client does. If the AI summary produces a sentence that sounds different from what you intended, that is a signal to revise the source clause before it becomes a dispute.

The AI summary is a readability layer, not legal advice. If your engagement involves significant IP, a complex licensing structure, or international jurisdiction issues, have a solicitor or attorney review the contract before you use it as a template.

E-signatures: DocuSign

PayShield integrates with DocuSign for e-signatures. DocuSign signatures are legally recognized electronic signatures under the US ESIGN Act, EU eIDAS, and equivalent laws in most jurisdictions.

Connecting DocuSign

Go to Settings → Integrations and connect your DocuSign account. You only do this once. After connecting, DocuSign is available whenever you send a contract for signature.

The signing flow

Once the contract is ready, click Send for Signature. PayShield sends the client an email with a link to the document via DocuSign. The client opens the link, reviews the contract in their browser, and signs using their mouse, trackpad, or touch. No downloads, no printing.

After the client signs, you receive a notification. If you need to countersign — and for most contracts, you should — you open the document, review the client's signature, and add yours. Both signed copies are stored in PayShield and linked to the contract record.

Contract status lifecycle

The status updates automatically as the signing provider reports back. You do not need to follow up manually to find out whether the client has signed — PayShield tells you, and you can set a reminder to escalate if it stays in "Sent" for more than a couple of days.

Version history and change tracking

Every edit to a contract in PayShield is logged. The version history panel shows what changed, when, and who made the change. This matters when a client disputes a term later and claims it was not in the original agreement — you have a timestamped record of every version they could have seen.

When to use a change order vs editing the original

The version history is not a license to keep editing a live contract. Once a contract reaches "Signed by Both," you should not edit the original document. Any change to scope, payment, or timeline after that point should go through a formal change order.

A change order is a standalone document that references the parent contract, describes specifically what is changing, and requires both parties to sign again. PayShield lets you create change orders directly from the contract view — they inherit the client, currency, and e-signature settings from the parent. The signed change order then appears alongside the original in the contract's document history.

For questions about managing the work itself — milestones, task assignments, deliverable tracking — the project management walkthrough covers how PayShield links contracts to active projects.

Tips before you send

Always include a late-fee clause. It is not aggressive — it is what gives the payment escalation engine legal teeth. Without a contractual late fee, the engine can still send reminders, but it cannot truthfully reference a charge the client is obligated to pay. With a late fee in the contract, every escalation email can quote an exact amount, and the client knows you are not bluffing. You can calculate what that adds up to using the late fee calculator.

Use revision caps even on small projects. The projects that spiral into scope creep are rarely the large ones — they are the "quick" projects where you skipped the paperwork because it felt excessive. One revision cap clause takes thirty seconds to add. The conversation it prevents takes hours you do not have.

If you started with a proposal, check that the contract inherited the right terms. PayShield copies the payment terms from the proposal automatically, but take thirty seconds to confirm that the late fee, currency, and payment schedule look right before you send.

For a complete picture of the platform, the full PayShield guide covers invoicing, escalation, projects, and client portals as one connected workflow — including how all of these pieces work together once a client is late.