Freelancer payment template

Payment Before Work Template

Creator, ScopeDueUpdated

Use this template when a client has approved extra work, but your rule is payment before work starts. Send a calm message that confirms the request, explains the payment condition, and gives the client a clear next step. Then track the payment request in a payment ledger so “client marked paid” and “freelancer confirmed received” stay separate.

Create payment request Track payment status

Last reviewed: · Template for U.S. freelancers and solo studios

Best use: send this after the client approves an extra request, revision, source-file release, rush change, or add-on that requires payment before work begins. The goal is not to sound harsh. The goal is to create a clear business record: what was approved, what is due, when work can start, and who confirms payment received.

Who should use this

Use it when “approved” is not the same as “ready to start”

This payment before work template is for freelancers, solo studios, and small service providers who accept client changes but do not want to begin the extra work until the required payment is actually received. It fits common situations like an added website page, extra design revision, source file request, rush delivery, new video export, additional copy page, or work outside the original scope.

Approved but unpaid

The client says yes to the change, but payment is still required before the work enters your queue.

Client says they paid

The client can mark paid or upload proof, but you still need to confirm the money arrived on your side.

Work should pause

The message gives a professional reason for waiting without turning the conversation into a confrontation.

Copy/paste version

Payment before work starts template

Use this version when you already have the client’s approval and need to request payment before starting the work.

Standard client message

Tone: calm, clear, professional

  • Payment requested
  • Before work starts
  • Freelancer confirmation
Subject: Payment needed before I start [Approved Change] Hi [Client Name], Thanks for approving [Approved Change]. This item is ready to move forward, and as noted in the request, payment is required before work begins. You can review the payment details here: [Payment Link] Once the payment is received and confirmed on my side, I’ll move this into the work queue and begin the approved work. Thanks, [Your Name]

Important wording: say “received and confirmed on my side,” not just “when you mark it paid.” This keeps the payment status history accurate and avoids the common gap between a client saying they paid and the freelancer actually receiving funds.

Message variations

Choose the version that matches the relationship

Different clients need different levels of detail. Keep the rule consistent, but adjust the tone.

Firm-but-friendly version

Hi [Client Name], I’m happy to take care of [Approved Change]. Since this is outside the original approved scope, this item requires payment before I begin. Here’s the payment request: [Payment Link] Once I confirm the payment has been received, I’ll start the work and keep the timeline updated from there. Thanks, [Your Name]

Short version

Hi [Client Name], Thanks for approving [Approved Change]. Payment is required before work starts. You can review the payment request here: [Payment Link] Once payment is confirmed on my side, I’ll begin the work.

More formal version

Hi [Client Name], Thank you for approving the additional work for [Project Name]. This approved change is separate from the original scope and requires payment before work begins. Payment details are available here: [Payment Link] After payment has been received and confirmed, I will schedule the work and proceed according to the approved change request. Regards, [Your Name]

After client marks paid

Hi [Client Name], Thanks for marking the payment as sent. I’ll confirm once the payment appears on my side. After it is confirmed, I’ll start the approved change and keep the project status updated.

Customize before sending

What to fill in before the client sees it

A strong payment-before-work message should be specific enough that the client understands exactly what they approved and what happens next.

Field What to write Why it matters
[Approved Change] Name the specific extra item, such as “additional landing page section” or “third revision round.” Prevents the message from sounding like a generic invoice reminder.
[Payment Link] Use the link where the client can review the amount, due date, payment instructions, and status. Moves the conversation out of scattered chat messages and into a record.
Payment condition Say whether payment is required before work starts, before handoff, or before source files are released. Clarifies what is paused and what unlocks after payment is confirmed.
Confirmation language Use “once payment is received and confirmed on my side.” Keeps client-marked-paid separate from freelancer-confirmed-received.

ScopeDue workflow

Pain → ScopeDue workflow → What gets recorded

Pain

A client approves extra work in chat, but the freelancer starts too soon. Later, payment is delayed, the client says they already paid, or the approved change gets mixed into the original scope.

ScopeDue workflow

  1. Create the payment request for the approved item.
  2. Send the client link or message.
  3. Let the client mark payment sent or upload proof.
  4. Confirm receipt before work starts.
  5. Save the payment history in the record.

What gets recorded

  • Approved change and amount due
  • Payment requested status
  • Client marked paid event
  • Payment proof upload, if used
  • Freelancer confirmed received event
  • Ready-to-start status after payment
Create payment request See how the payment ledger works

Payment ledger connection

Use statuses instead of a vague “paid/unpaid” note

The template is stronger when it points to a payment record. A payment ledger shows the difference between a request being sent, a client saying payment was sent, proof being uploaded, and the freelancer confirming payment received.

Sample payment status history

  1. Payment requested: Freelancer sends payment request for the approved change.
  2. Client marked paid: Client indicates payment was sent.
  3. Proof uploaded: Receipt or payment reference is attached, if needed.
  4. Freelancer confirmed received: Freelancer checks their account and confirms receipt.
  5. Ready to start: The approved work can move into the work queue.

Common mistakes

Avoid wording that weakens your boundary

The message should stay calm and client-friendly, but it should not create confusion about when work begins.

  • Do not write: “I’ll start now and you can pay later.” Use payment-before-work language when that is the condition.
  • Do not write: “Paid once you click the button.” The client can mark paid, but only you can confirm receipt.
  • Do not hide the reason: Name the approved change so the client understands this is tied to extra work, not a random payment demand.
  • Do not over-threaten: Keep it professional. Say the work will begin after payment is confirmed, not that the client is being punished.
  • Do not rely only on chat: Link to a payment request or approval record when the work, price, or status matters.

Use this when / not when

Use the template for payment workflow clarity, not legal pressure

Use this when

  • The client approved extra work.
  • Payment is required before work starts.
  • You need a clean payment status history.
  • The client may need to upload proof or ask a question.
  • You want a calm message instead of an awkward manual follow-up.

Do not use this when

  • You are trying to replace a contract or legal notice.
  • The payment terms were never discussed or approved.
  • You need tax, accounting, debt collection, or legal advice.
  • The client has a serious dispute that requires professional help.
  • You want to imply payment is guaranteed.

Create a clear record before the work continues

Use ScopeDue to turn the approved change into a payment request, let the client mark payment sent, confirm receipt on your side, and keep the full status history in one business record.

Create payment request View sample approval link

Quick answers

Payment-before-work questions

Is it okay to ask for payment before starting extra work?

For many freelancer workflows, yes, if the payment condition is clearly communicated and tied to an approved scope change. Keep the message specific, calm, and connected to the approved item.

What if the client says they already paid?

Thank them, ask them to mark the payment as sent or upload proof if needed, then confirm receipt on your side before starting the work.

Should I mention the original scope?

Yes, if it helps explain why the item requires a separate payment. Keep it factual: “This is outside the currently approved scope.”

Does ScopeDue process payments?

This page focuses on payment request and payment status tracking. ScopeDue helps record the request, client payment claim, proof, and freelancer confirmation without presenting that record as accounting or legal advice.

Product limit: ScopeDue helps freelancers create a clear business record of approvals, payments, and handoff events. It is not a substitute for legal, tax, or accounting advice. For professional advice about contracts, taxes, collections, or disputes, contact a qualified professional. You can also read the ScopeDue product disclaimer.

Related workflow links

Use these supporting pages to move from the current topic into the next approval, payment, proof, or handoff step.