A project proposal that gets approved on the first read is almost always exactly one page long and answers six specific questions — not a paragraph of enthusiasm about the topic. Teachers approving a stack of proposals aren't looking for excitement; they're looking for evidence that the project is answerable in the time given, has a clear output, and can actually be assessed. Get those six things onto the page and approval is close to automatic.

Why most first drafts get sent back

The most common reason a proposal bounces isn't a bad idea — it's an idea with no edges. "I want to do something about climate change" or "I'm interested in the Romans" describes a subject, not a project. A teacher reading that can't tell what you'll actually produce, how you'll know if it went well, or whether three weeks is enough time. The fix is always the same: turn the topic into a question specific enough that someone could genuinely disagree with your answer before you've found it.

The six things every approved proposal answers

  1. The question or problem — one sentence, specific enough to be wrong about. Not "food waste" but "how much edible food does our school canteen throw away in a typical week, and what's the single biggest cause?"
  2. Why it matters — two or three sentences on who cares about the answer and why now. This doesn't need to be dramatic; "our year group generates the school's biggest lunchtime queue" is a perfectly good reason.
  3. The final output — the exact thing you'll hand in or present: a report with data, a working model, a short film, a poster and a five-minute talk. Naming it early stops the project drifting.
  4. The rough plan — a short list of stages with approximate dates. It doesn't need to be exact; it needs to show you've thought about the order things happen in.
  5. What you need — access, materials, someone to interview, a piece of software, permission to survey other students. Anything that could block you should be named now, not discovered in week two.
  6. How it'll be judged — what a good version of this project looks like versus a weak one. If you don't know, ask; most schools use a rubric similar to the one covered in how project-based learning gets marked.

A simple one-page template

Project title:
Question I'm answering:
Why this matters:
What I'll produce:
Plan (rough dates):
  Week 1 —
  Week 2 —
  Week 3 —
What I need:
How success will be judged:

Fill every line before you show it to anyone. A blank line is usually the exact spot a teacher will ask a question you haven't thought about yet.

Weak vs strong: the same idea, two ways

Weak version. "For my project I want to look at plastic pollution because it's a big problem and I care about the environment. I'll do some research and make a poster."

This fails on almost every count. The question isn't a question. There's no plan, no sense of scale, and "some research" could mean anything from an afternoon to a term.

Strong version. "Question: does switching our school's canteen from plastic cutlery to wooden cutlery for one week actually reduce bin weight, or does it just move the problem to a different bin? I'll weigh canteen waste for a normal week, then for a trial week with wooden cutlery, and compare. Output: a one-page data report with a recommendation to the site manager. Plan: week 1 baseline weighing, week 2 trial + weighing, week 3 analysis and write-up. I need: permission to weigh canteen bins, and 10 minutes of the site manager's time for one interview. Success: a clear comparison with real numbers, not just an opinion."

Same underlying interest — waste and the environment — but the second version is answerable, has a method, and produces something a teacher can actually evaluate.

Common mistakes that sink an otherwise good idea

  • Choosing a question you already know the answer to. If there's nothing to find out, there's no project — see choosing a project topic for how to test whether a topic is genuinely open.
  • Making the output too big for the timeframe. A three-week project that promises a working app and a 20-page report and a public exhibition is promising more than it can deliver. Pick one primary output.
  • Skipping the "what I need" line. Needing a teacher's help to arrange an interview, or access to equipment, is exactly the kind of thing that stalls a project in week two if it isn't flagged in week zero.
  • Writing to impress rather than to inform. A proposal isn't the place for flourish — a teacher scanning twenty of these wants clarity, not persuasion. If your writing tends to wander, it's worth reading PEEZL paragraphs for a structure that keeps each point tight and evidenced.

What to do after it's approved

Once a proposal is signed off, the plan section becomes the seed of your actual project timeline — see planning a project timeline for how to turn three rough weeks into milestones that hold up under pressure. Keep the original proposal somewhere you can find it; it's the cleanest answer when someone (a teacher, a parent, your own future self in week three) asks "wait, what was this project actually meant to prove?"

FAQ

How long should a KS3 project proposal be? One page. A teacher deciding whether to approve twenty-plus proposals needs to see the whole thing in under a minute — anything longer usually means the question itself isn't sharp enough yet.

What's the single biggest reason proposals get rejected? The question is too broad to answer in the time available. "I want to research pollution" is not answerable in three weeks. "Which of three cleaning products removes the most oil from a fabric sample" is.

Do I need to know the answer before I propose the project? No — if you already know the answer, it isn't really a project. A strong proposal names a genuine question, not a conclusion you're planning to illustrate.