Run freelance jobs from enquiry to payment

Freelance document trouble usually starts before the invoice. A vague estimate becomes a vague contract, the contract says little about revisions, the invoice uses a number you already used, and by year end the signed copy is buried in a mail thread. None of that requires a large system to fix. It needs a small routine that you repeat for every job.

This is a practical document workflow, not legal or tax advice. Contract terms, invoice rules, tax treatment, and late-payment rights vary by country and by the type of client you serve. Use a professional to confirm the wording and tax requirements that apply to you.

Start every job with scope, not optimism

The proposal or estimate should say what you will deliver, what the client must provide, how many rounds of revision are included, when the work will happen, and what is outside the price. Exclusions are not unfriendly. They prevent the later argument where one person thought copywriting included brand strategy, or a simple landing page included analytics, hosting setup, and three months of support.

Write the scope in plain language and give each deliverable a measurable edge: one 1,200-word article, three logo concepts, two edited podcast episodes, or one five-page website build. If timing depends on client feedback, say so. If an estimate expires after 14 days, put the date on the document.

For small jobs, you can create a clean estimate directly with create PDF. For larger work, keep the source document editable until the client accepts, then export the accepted version to PDF and store it in the job folder.

This post follows the job from acceptance onwards. If the quotation itself is where you lose work — pricing presentation, validity windows, options, and the follow-up that converts — that ground is covered separately in sending a quotation that turns into work.

Turn acceptance into a contract

An accepted estimate is useful evidence, but the contract is where the practical rules should live. The clauses that matter most in day-to-day freelance work are often the unglamorous ones:

• Scope and deliverables, matching the accepted estimate.
• Revision limits and how extra revisions are charged.
• Payment terms, deposit, milestone dates, and final due date.
• Late fees or interest, where allowed and properly drafted.
• Kill fee or cancellation terms if the client stops the job part-way through.
• IP transfer only on final payment, if that is the arrangement you intend.
• Confidentiality, especially where client material or launch plans are shared.

Do not sign wording you do not understand, and be cautious with unlimited edits, uncapped liability, broad non-competes, or immediate IP transfer before payment. Those are points to clarify before work starts, not after the client has the files.

Sign, flatten, and store the agreed copy

A signing routine should not require either party to create an account just to place a signature. Use sign PDF to add signatures to the final PDF agreement in the browser tab, then save a copy with both names and the date in the filename. If the document contains form fields or signature annotations, use flatten PDF for the retained copy so the visible record is stable when opened in different PDF readers.

Flattening is not the same as legal validation, and it is not a cryptographic certificate. It is a practical way to make the signed appearance part of the page, reducing the chance that a field prints blank or an annotation is moved by mistake. Keep the unflattened working copy only if your process requires it; the folder should make clear which PDF is the signed record.

Number invoices so there are no duplicates

Invoice numbers should be sequential within your chosen system. The exact format is up to you and local requirements, but it must not produce duplicates. Many freelancers use a year prefix plus a running number, such as 2026-001, 2026-002, and 2026-003. Others use a single lifetime sequence. Pick one and write it down.

Gaps and duplicates cause problems because they make the sales record harder to trust. A duplicate number can delay payment when the client's accounts team has already processed an earlier invoice. An unexplained gap can create questions at tax time. If you void an invoice, keep a note rather than reusing the number.

A prompt invoice should show the invoice number, issue date, supply or project period, client reference or purchase order if they gave one, itemised work, tax treatment, payment details, payment due date, and your contact details. Where GST-style invoicing applies, GST invoice can help produce a structured PDF invoice, but tax labels and required fields still need to match your jurisdiction.

Use a written follow-up ladder

Late-payment follow-up is easier when you decide the ladder before you are annoyed. For example: a polite reminder two days before the due date, a factual notice on the due date, a firmer reminder seven days late with the invoice attached again, then a final notice that states the next step under your contract or local process. Keep the tone calm and the references precise.

Every follow-up should include the invoice number, amount, due date, payment link or bank details, and a copy of the invoice. Do not rewrite the commercial terms in the reminder. Refer back to the signed agreement and invoice.

Keep one folder per job

A consistent folder makes year-end review take minutes. Use a pattern such as 2026-client-project and subfolders for 01-enquiry, 02-estimate, 03-contract, 04-delivery, 05-invoices, and 06-payment. Store the accepted estimate, signed and flattened contract, issued invoices, credit notes if any, and proof of payment in that folder.

At year end, you should be able to open each job and answer four questions: what was agreed, what was delivered, what was invoiced, and whether it was paid. That is the standard the routine is trying to meet.

Freelance paperwork checklist

• The estimate describes deliverables, assumptions, exclusions, price, and expiry date.
• The contract covers scope, revisions, payment, cancellation, IP, and confidentiality.
• The signed PDF is flattened and stored as the record copy.
• Invoice numbers are sequential, unique, and never reused after voiding.
• Each invoice has dates, references, itemisation, tax treatment, payment details, and a due date.
• The whole job lives in one consistently named folder.