Handling Freelance Projects
Plan a larger project with a written scope, expected extra hours from risks, a buffer, milestone payments, change requests and a rush rate agreed in advance, on sample numbers.
In this lesson you will
- Write a scope and stage plan
- Count risks and size a buffer
- Set milestone payments
- Handle change requests and rush work
About 25 minutes
A big job, and a long list of things that could go wrong
A small agency hires Dev for a 40-hour project priced at 1,000. It is Dev’s biggest job so far. Dev lies awake wondering what could go wrong. The client might be slow with feedback, ask for another round, add a new page or give an unclear brief. Handling a project well is not about hoping those things will not happen. It is about expecting some of them, planning for them in the price and the schedule and agreeing in advance how to handle changes. This lesson gives you tools for all three.
Write the scope and the plan
As lesson 5 and lesson 6 said, start with a written scope: what is included, what is not, how many rounds of changes and what you need from the client by when. Then break the work into stages with a date for each. Lesson 29 of the Blogging course and the earlier courses show a way to find the critical path, the chain of tasks that decides the end date. The same idea works here. For this lesson, the focus is on risk and money.
Count the risks
A risk is something that might go wrong. For each one, estimate how likely it is and how many extra hours it would cost. Multiply the chance by the hours and add up the results to get the expected extra time. The program below does this for four made-up risks on the 40-hour job, and compares the total with a buffer of 20 per cent. It then sets milestone payment dates and works out a rush rate for urgent changes.
from datetime import date, timedelta
# MADE-UP risks on a 40-hour project: (risk, chance, extra hours if it happens)
risks = [("client late with feedback", 0.50, 3), ("extra round of changes", 0.40, 5),
("new page requested", 0.30, 6), ("unclear brief", 0.20, 4)]
expected = sum(p * h for _, p, h in risks)
worst = sum(h for _, _, h in risks)
print("planned hours:", 40)
print("expected extra hours:", round(expected, 1))
print("all risks at once:", worst)
buffer = 40 * 0.20
print("buffer at 20%:", buffer)
print("buffer covers the expected extra:", buffer >= expected)
print("buffer covers every risk:", buffer >= worst)
start, price = date(2026, 11, 30), 1000
for pct, offset in ((30, 0), (40, 14), (30, 28)):
print(f"{pct}% = {price * pct // 100} due {(start + timedelta(days=offset)).strftime('%a %d %b')}")
rush = 24.55 * 1.4
print("rush rate an hour:", round(rush, 2))
print("3 rush hours cost:", round(3 * rush, 2))
planned hours: 40
expected extra hours: 6.1
all risks at once: 18
buffer at 20%: 8.0
buffer covers the expected extra: True
buffer covers every risk: False
30% = 300 due Mon 30 Nov
40% = 400 due Mon 14 Dec
30% = 300 due Mon 28 Dec
rush rate an hour: 34.37
3 rush hours cost: 103.11
The expected extra comes to 6.1 hours. If every risk happened at once, the extra would be 18 hours. A 20 per cent buffer gives 8.0 hours. Does the buffer cover the expected extra? Yes. Does it cover every risk at once? No. That is the right way to think about a buffer: it should cover what usually happens, not the worst imaginable case. If the worst case would ruin the job, you need other protection, such as the clauses and insurance of lessons 25 and 27, or a clear change process, which is the next part.
Milestone payments
Large jobs should not be paid only at the end. The program splits the 1,000 fee into three payments: 30 per cent at the start on Mon 30 Nov, 40 per cent on Mon 14 Dec and 30 per cent on Mon 28 Dec. Payment in stages protects both sides. The client sees progress before paying more, and Dev is not waiting for the whole fee while working for weeks. Link each payment to a stage that can be checked, such as ‘first draft delivered’, and put the dates and amounts in the agreement.
Change requests and a rush rate
When a client asks for something outside the scope, treat it as a change request: say what it adds in hours and money, and ask for a yes before doing it. For urgent work you might agree a higher rush rate in advance. In the program, a rush rate 40 per cent above the floor comes to 34.37 an hour, so three rush hours cost 103.11. Say this before the job starts. A rush rate quoted for the first time in the middle of a crisis feels like a trick.
- Write the scope and the stage dates.
- List the main risks, with a chance and extra hours for each.
- Add a buffer that covers the expected extra, and say what the schedule assumes.
- Agree milestone payments and a change process in the contract.
- Review the plan every week, and update it when something changes.
Keep the client informed
- Send a short update at each stage, even when nothing has gone wrong.
- Tell the client early if a date is at risk, with the options.
- Keep decisions and changes in writing, in one place.
- At the end, hand over clearly, check that the client has what they need and ask for feedback.
- Note what you learned, for your next estimate.
Close the project well
A good ending is part of the job. Send a final summary of what was done, remind the client of anything outside the scope that they might want later and send the last invoice promptly. Ask for a short quote and permission for a case study, as lesson 23 explained. Then update your time log and estimates, and keep the files safe for as long as your agreement or the law requires.
Planning for the best case and calling it the plan. If you assume that nothing will go wrong, the first surprise breaks the schedule. Plan for what usually happens, and say what your dates assume.
The project, risks, chances, hours, dates and rates are made up in sample money. Real projects surprise everyone, and nothing here guarantees a result. Contracts, payment terms and rush fees differ by situation and country. This lesson is an outline and not legal or financial advice.
Practice for this lesson
Check what you learned
Five quick questions. Pick an answer and you will see straight away whether it is right and why.
What is the expected extra time?
- The longest delay only
- The price of the job
- The client’s guess
- Chance times extra hours, added up over the risks
It is a probability-weighted total.
What did the 20 per cent buffer cover?
- Every possible risk
- The expected extra, not every risk at once
- Nothing
- Only the worst case
Eight hours covered 6.1 expected but not 18 worst-case hours.
Why use milestone payments?
- They avoid contracts
- They hide fees
- They protect both sides and spread the risk
- They raise taxes
Progress is visible before more money moves.
When should you quote a rush rate?
- Before the job starts
- In the middle of a crisis
- After delivery
- Never
A rush rate agreed in advance feels fair.
What should you do with a change request?
- Do it free
- Refuse it rudely
- Say what it adds and get a yes first
- Ignore it
Changes need their own agreement.
Summary
- Plan for what usually happens, with a buffer for expected extra hours.
- Pay in stages linked to checkable milestones.
- Treat extra requests as change requests with a quote.
- Agree a rush rate before the job starts.
Questions
How big should a buffer be?
There is no fixed answer. The lesson uses 20 per cent, made up. Check it against your own past overruns, as lesson 16 showed.
Can I ask for payment before starting?
Many freelancers ask for a first payment, especially on larger jobs. Put it in your agreement and quote, and check the rules where you live.
Are the risks and chances real?
No. They are made-up numbers to show the method. Use your own history.
