Before you send a freelance proposal, check that it states the client’s goal, a countable list of deliverables, what is excluded, a timeline with client responsibilities, the price and payment schedule, revision limits, how changes are handled, who approves, who owns the work, your assumptions, and an expiry date. A gap in any of these is how a good proposal turns into a bad project.
This is a pre-send checklist, not a writing guide. If you are still drafting, how to write a freelance proposal without overcomplicating it covers structure and length. Each item below has a reason and sample wording to adapt.
The work itself
1. Goal and situation
Open with a sentence or two on what the client wants and why, in their words. Sample: “You want to cut the time your team spends answering repeat customer questions by building a help section that covers your ten most common issues.” It gives you something to point back to if a request does not serve the stated goal.
Check: could the client read it and say “yes, that is what we need”?
2. Deliverables
List what the client receives, with quantities, formats, and limits: how many pages, articles, or designs; which file types; word counts or durations. Sample: “Five help articles of 400 to 600 words each, delivered as editable documents, with a suggested heading structure.” If you cannot count it, a client can always want more of it.
Check: could a stranger tell from the list whether everything was delivered?
3. What is not included
A short exclusions list covers what clients tend to assume: “Not included: photography, translation, software licenses, publishing to your site, and updates after delivery.” If past projects have surprised you the same way twice, add that item. Setting a project scope that does not drift goes further on exclusions.
4. Timeline and client responsibilities
Give a start date, milestones, and a delivery date, plus what you need from the client and when. Sample: “Kickoff June 3, first draft June 14, feedback due June 19, final delivery June 26, assuming I receive the listed materials by June 5.” Timelines depend on client behavior, so say so in the document.
Money and process
5. Price and payment terms
| Item | Example wording |
|---|---|
| Fee | “Total project fee: $X” |
| Deposit | “50 percent due before work begins” |
| Balance | “Remaining 50 percent due on delivery” |
| Due date | “Invoices due within 14 days” |
| Late payment | “Work may pause if an invoice is more than [X] days overdue” |
| Expenses | “Third-party costs billed at cost” |
These are illustrative; use figures from your own estimate (see how to price freelance work without undercharging). Payment terms vary by field and client, and whether pauses or late fees can be enforced depends on your contract and location, so have a qualified professional review them for larger projects.
6. Revision limits
Say how many rounds are included, what a round is, and what happens after. Sample: “Two rounds of revisions are included. A round is one consolidated set of feedback from [client] on a delivered draft. Further rounds are billed at $X per hour.” The proposal should also separate a revision from new work. Handling freelance revisions without projects dragging has more wording.
7. Change requests
State how outside-scope work is handled: “Requests outside the deliverables above will be quoted separately and approved in writing before work begins.” One line like this keeps extra requests friendly and priced.
8. Approvals and decision makers
Name who gives final approval and how feedback is collected: “[Name] gives final approval. Feedback from other team members is consolidated into one message.” Late-appearing stakeholders are a common cause of reversals, so it helps to know the decider in advance.
Rights, assumptions, and closing
9. Ownership and usage
Say who owns the finished work and when ownership transfers. A common arrangement is transfer on full payment, with a note on portfolio use. Sample: “Ownership of the final deliverables transfers to [client] on receipt of full payment. I may show the finished work in my portfolio unless you tell me otherwise.” Intellectual property rules vary by country and state, and details such as work-for-hire matter, so treat this as a prompt to get professional advice, not a legal conclusion.
10. Assumptions and dependencies
List the conditions your estimate relies on: the client supplies text, images, and access by a stated date; the brief stays as described; one person consolidates feedback; third-party tools work as expected. Sample: “This estimate assumes the final text is provided by the client. If it needs writing, a separate quote applies.”
11. Expiry date and next step
A quote should not stay open forever. Sample: “This proposal is valid for 14 days. To start, reply to confirm and I will send the agreement and deposit invoice.” State only deadlines that are real. If the lead goes quiet, see following up without sounding desperate.
Final read-through
Before sending, confirm:
- The summary reflects the client’s goal in their words
- Deliverables are specific and countable, and exclusions are listed
- Dates and client responsibilities are clear
- The price is tied to the scope, with payment terms
- Revision limits, change requests, and the decision maker are defined
- Ownership, assumptions, and the expiry date are addressed
- Names, dates, and totals are correct, with no leftover text from an earlier proposal
- It reads well on a phone
Scale the checklist to the project
Not every item needs a paragraph. For a small, low-risk task, a few lines may cover deliverables, price, deadline, and revisions, with the rest handled by a short agreement. For a larger engagement, especially one with several stakeholders, a long timeline, or work that will be published or resold, the ownership, approvals, and change-request items deserve full sentences. The test is consequence: the more it would cost you or the client if a point were misunderstood, the more precisely it should be written down.
It also helps to decide, once, which items live where. Many freelancers keep the proposal to the commercial points (goal, deliverables, price, timeline) and move payment-failure, cancellation, and ownership language into a separate agreement. Either arrangement works as long as nothing falls between the two documents and the proposal points to the agreement.
Gaps that cause the most trouble
Some omissions turn up again and again in freelance disputes:
- A deliverable described by topic (“a brand refresh”) instead of by count and format
- No definition of when the work counts as finished
- A deposit mentioned but no date for the balance
- Feedback expected from “the team,” with no single person responsible
- Materials the client promised but the proposal never listed as a dependency
If one of these has already cost you time, put it at the top of your own checklist and keep a personal version of this list that grows with experience.
To go through it item by item, use the proposal checklist.
Where this comes from
This checklist is based on commonly published freelance proposal guidance, which lists an overview, scope of work, deliverables, timeline, and price as the core elements, and on general contract and project-scoping practice for the added items. No regulator sets a standard format. Sample wording and figures are invented and are not legal drafting. Contract and intellectual property rules differ by place and change over time, so have a qualified professional, such as a lawyer, review ownership and payment terms.
General information, not legal, tax, or financial advice.