Freelance Client Communication Exercises

A strong proposal uses confident, specific language: "Based on your brief, I propose the following scope of work...", "The deliverables will include...", "I estimate this project will take approximately X weeks, subject to timely feedback and approvals.", "My rate for this engagement is £X per day / £X per project." Avoid vague phrases like "I'll try to" or "I think I can" — use definitive language that signals professional reliability. Close with a clear call to action: "Please review the attached statement of work and let me know if you'd like to schedule a kick-off call."

Use a calm, factual tone that acknowledges the request before explaining the boundary: "That's a great addition — I want to flag that this falls outside the scope we agreed in the original brief. I'm happy to include it as a change request. Based on the additional work involved, I'd estimate an additional £X and approximately 3 extra days. Shall I update the statement of work and invoice accordingly?" Avoid the word "no" in isolation — frame every scope boundary as a solvable problem with a price attached.

Key terms: invoice date (the date the invoice is issued), due date (the date payment is expected), payment terms (e.g., "Net 30" means payment is due 30 days after the invoice date), purchase order number (PO number, often required by larger clients before processing payment), late payment interest (a charge applied to overdue invoices, required by law in the UK under the Late Payment of Commercial Debts Act), and remittance advice (a document a client sends to confirm which invoices a payment covers).

Scope creep refers to the gradual expansion of a project beyond the originally agreed boundaries, often without a corresponding increase in budget or timeline. Address it early and in writing: "I've noticed we've taken on a few additions since the original brief — the extra API integration and the revised onboarding flow. These fall outside our agreed scope, so I'll be raising a change request to cover the additional time. I wanted to flag this proactively so there are no surprises on the final invoice." Document everything via email or project management tool.

Structure: current status (overall RAG — Red/Amber/Green), progress this week, planned work next week, blockers or decisions needed. Example: "Project status: Green. This week I completed the user authentication module and began integration testing. Next week I'll deliver the dashboard component and begin UAT. I need your sign-off on the colour palette by Wednesday to stay on schedule — I've attached the options for review." Keep updates concise and action-focused; every update should make clear what you need from the client, if anything.

Be direct and treat payment terms as a standard business discussion: "My standard payment terms are 50% upfront and 50% on delivery, with invoices due within 14 days of issue. For larger engagements I'm also open to milestone-based billing." If a client pushes back: "I understand Net 60 is standard for your procurement process — I can accommodate that for invoice settlement, though I'd still need the upfront deposit to reserve the project slot." Know your minimum acceptable terms before entering the conversation.

First follow-up (1–3 days after due date, polite): "I wanted to follow up on invoice #INV-042 for £2,400, which was due on [date]. Please let me know if you need any additional information to process the payment." Second follow-up (7+ days overdue, firmer): "Invoice #INV-042 is now 10 days overdue. I'd appreciate your urgent attention to this — please confirm the expected payment date." Third follow-up (formal): "As this invoice remains unpaid after [X] days, I am writing to notify you that late payment interest will begin accruing from [date] in accordance with the Late Payment of Commercial Debts Act 1998."

A handover document typically includes: a summary of all deliverables and where they are stored, credentials and access details (handed over securely, not in email), documentation of any known issues or technical decisions, and a maintenance guide if relevant. Cover email language: "Please find attached the project handover documentation for [Project Name]. All deliverables are uploaded to [location]. I've included login credentials in the separate encrypted file. Please review and confirm receipt by [date] — this will mark the formal close of the project and release the final invoice."

Be brief, respectful, and leave the door open: "Thank you for thinking of me for this project. After reviewing the brief, I don't think I'm the best fit for this particular engagement — [brief reason if appropriate, e.g., the timeline doesn't work for my current schedule / the domain is outside my current focus area]. I'd be happy to recommend a colleague who specialises in this area." Avoid lengthy explanations or apologies — a short, professional decline preserves the relationship better than a hesitant one.

Key terms: UAT (User Acceptance Testing — when the client tests the deliverable against their requirements), sign-off or formal acceptance (the client's written confirmation that the deliverable meets the agreed specification), snagging list (a list of minor issues the client wants resolved before final sign-off, common in creative and development projects), and final invoice (the invoice raised upon acceptance, sometimes called the completion invoice). Phrase to use: "Please review the deliverable and send me your written acceptance or a snagging list by [date]. Final invoice will be raised upon sign-off."