Freelance Deadline Planner
| Milestone | Share of runway | Your date |
|---|---|---|
| First draft | 50% - half the runway left | – |
| Client review | 75% - their window starts | – |
| Revisions done | 90% - the scope-guard line | – |
| Delivery | 100% - the contract date | – |
Freelance deadlines fail the same way every time: the calendar shows three comfortable weeks, so the draft slips, and suddenly review, revisions and delivery are all crammed into the last four days. The fix is back-planning - treat the deadline as fixed and schedule the milestones backward from it, so the client sees dates instead of vibes.
Bottom line: the milestone percentages are the whole method - first draft at 50% of the runway, client review at 75%, revisions done at 90%, delivery at 100%. A three-week project therefore owes a draft in 10 days, not 'when it's ready', and the 90% mark is what protects you from the revision spiral that eats every unguarded freelance project.
The honest part: the plan only works if the client sees it. Send the milestone dates WITH the quote - a client who agreed in writing that the draft arrives at the halfway point cannot legitimately expect the full draft in week one, and the review window is THEIR commitment, not just yours.
How to use
- Enter the delivery deadline - the one contractual date you cannot move.
- Read the four milestone dates: first draft (50% of runway), client review (75%), revisions done (90%), delivery (100%).
- Send the plan with your quote or kickoff message so review windows are agreed, not assumed.
- Come back weekly - the date is remembered on this device, and the milestone dates stay fixed while the remaining runway shrinks.
- Protect the 90% mark: if revisions are not done by then, scope is changing - flag it then, not on delivery day.
Frequently asked questions
How much buffer should a freelance timeline have?
Built-in, not bolted on: the 50/75/90 milestone plan IS the buffer - the draft lands with half the runway left, so 'everything takes longer than expected' has somewhere to go. If the project is fixed-scope with a known client, one revision round at the 90% mark is the norm; for new clients or vague briefs, quote the deadline at 120% of your honest estimate and keep the difference as quiet buffer rather than promising optimistically and delivering late.
When should a freelancer ask for the deadline to move?
At the 90% mark, not on delivery day. The whole point of milestone dates is that slippage becomes visible while there is still runway: if revisions are not wrapping at 90%, the remaining 10% cannot absorb a rewrite. Raise it then with the facts - the agreed dates, what is blocking, the two realistic options (a short extension or a reduced scope) - and the conversation is professional planning instead of an apology.
How do I plan around client review time I cannot control?
The 75% review milestone is a TWO-sided commitment: the clock between 75% and 90% belongs to the client. State the review window when you send the draft ('revisions begin once comments land by Friday') and put it in the quote - otherwise an unresponsive client silently converts your revision week into their thinking week, and the deadline risk transfers entirely to you. For slow organizations, book the review window in their calendar at kickoff, not after the draft exists.
Does this work for short projects - a 3-day turnaround?
Yes, with compressed percentages: on a 3-day project the milestones become day 2 (draft), day 2.5 (review), day 3 morning (revisions) - the planner rounds to the day and the discipline is identical. What does NOT compress is the review window: if the client cannot turn comments around in hours, a 3-day promise is really a 5-day project wearing a 3-day costume, and it is better to negotiate the date than to miss it.