A realistic multi-day trip planned against a fixed budget, using real transport and accommodation prices, is one of the most transferable maths projects a KS3 student can do — the ratio, percentage and comparison skills it exercises are exactly the ones used in every household budgeting decision for the rest of their life. Unlike most school maths, the numbers here come from real searches, not a textbook, which is what makes the final comparison genuinely uncertain until it's done.
Why this project works as maths practice
A single spreadsheet, built properly, forces a student through percentage, ratio, unit pricing and data comparison in one connected task rather than four separate worksheet exercises. It sits alongside ratio and proportion at Year 8 as a way to see those skills used for something with a real, checkable answer — did the trip actually come in under budget, or not.
Step 1: Pick the trip and set the budget first
Choose a trip before anything else gets decided — a family weekend away, or a hypothetical school trip to a European city, both work equally well. Then set a fixed total budget before researching a single price. This ordering matters: deciding the budget first means every later choice (which hotel, which transport) is genuinely constrained, rather than the budget being reverse-engineered to fit whatever looked nice.
A realistic budget for a 3-4 day trip for a family of three or four, or a small school group, is a sensible constraint to work within — pick a number and hold to it.
Step 2: Research real costs
This is where the project stops being hypothetical. Look up actual current prices for:
- Transport — train, coach, flight or ferry fares for the real or chosen dates, including the return leg.
- Accommodation — a real per-night rate for a specific hotel, hostel or Airbnb-style listing, for the number of nights planned.
- Food — a realistic daily estimate per person, based on a quick search of typical meal costs at the destination.
- Activities/entrance fees — for anywhere specific the itinerary includes.
Record the source and date for each price — prices change, and noting where a figure came from is good practice, not just tidiness.
Step 3: Handle currency conversion, if travelling abroad
If the destination uses a currency other than GBP, convert every foreign-currency price using a current exchange rate, and state that rate explicitly in the workings. This is a clean, real application of ratio: "£1 = €1.15" is a ratio, and converting a €90 hotel room into pounds is applying it directly.
Step 4: Build the day-by-day budget
A spreadsheet (or a clearly ruled table, if working by hand) with one row per day and columns for each cost category is the clearest way to present this. For each day, total:
| Day | Transport | Accommodation | Food | Activities | Daily total |
|---|---|---|---|---|---|
| 1 | ... | ... | ... | ... | ... |
| 2 | ... | ... | ... | ... | ... |
Sum the daily totals for a running total, and check it against the budget from Step 1 continuously as the itinerary is built — not just at the end.
Step 5: Calculate cost-per-person
This is where ratio does real work. Total cost divided by the number of travellers gives cost-per-person — but it's worth going one level further and comparing cost-per-person across two or three different accommodation or transport options, since the cheapest total isn't always the cheapest per person once group size and shared costs (like a hotel room split three ways versus two) are accounted for properly.
Step 6: Compare value between options using unit pricing
A genuinely useful maths habit: when two options aren't directly comparable (a 3-night hotel stay versus a 4-night hostel stay, say), convert both to a common unit — cost per night, or cost per person per night — before deciding which is better value. This is unit pricing, the same skill used when comparing supermarket products by cost-per-100g, applied somewhere it actually has stakes.
Step 7: Build in a contingency
No real budget is exact. Add a contingency line of 10-15% of the total to cover price changes, an extra meal out, or an unplanned cost — and state that percentage explicitly in the final document rather than quietly rounding numbers up. Calculating "15% of £480" and adding it as its own labelled line is itself a clean, gradeable percentage exercise.
Step 8: Present the final itinerary
The finished output should include:
- A day-by-day cost table (from Step 4).
- The total cost, cost-per-person, and contingency, clearly labelled.
- A short written summary explaining any trade-offs made (e.g. "chose the hostel over the hotel because the saved £120 covered two extra activity days").
This kind of structured, dated presentation is exactly what's covered in presenting your project to an audience, and if the project is being assessed formally, it's worth checking it against typical project-based learning assessment rubrics before calling it finished.
FAQ
Does the trip need to be real, or can it be hypothetical?
Either works, and hypothetical is often easier to control. A real family trip gives a genuine budget constraint and a real audience for the final pitch; a hypothetical school-trip-to-a-European-city version lets a student pick any destination and still use entirely real prices for transport and accommodation.
What maths skills does this project actually cover?
Percentage (contingency budgeting, discounts, currency conversion), ratio and unit pricing (comparing cost-per-person or cost-per-night between options), and structured data handling in a spreadsheet — genuinely more applied maths practice than most single-topic worksheets cover in one go.
How much contingency should be built into the budget?
10-15% of the total is a standard, defensible figure for a short domestic or European trip, and it's worth stating explicitly in the final itinerary rather than just quietly padding the numbers — showing the reasoning is part of the maths.