# Scoping and pitching

> The two early milestones, scoping and pitching, are where most strong submissions are won. What each is for, what reviewers look for and the mistakes to avoid.

Every challenge has a final deliverable: a deck, a report, a piece of code, a design. Before you produce it, you move through two milestones that mirror how real professionals scope a project: **scoping** and **pitching**.

These two milestones are where most strong submissions are won. Skipping them shows. Reviewers can spot a submission that jumped straight to "doing the work" without first thinking about which work.

## Scoping: define the problem before solving it

When you accept a challenge, your first task is to write a short **scoping document**, usually one to two pages. It answers four questions.

### 1. What is the real problem?

A brief gives you the surface, the symptom. Scoping makes you read past it. A market-entry brief might say "evaluate whether to enter Spain" but actually be asking "do we have the operational capacity to enter Spain right now?" Naming the real question changes the answer.

### 2. What is in scope, and what is out?

Real projects are bounded. Scope creep is the biggest reason challenge submissions fail to land. Write down what you will not address, and why. Reviewers reward clarity here, not coverage.

### 3. What is your approach?

Not the answer, the approach. The decomposition. "I will start by mapping the three competitors operating in the target market, sizing each, then layering on regulatory cost." That is enough at this stage.

### 4. What might go wrong?

Flag the risks in your approach. The strongest scoping documents name the assumption that, if wrong, would change the whole conclusion. Reviewers know this and look for it.

A good scoping document is short. It is not the final report. It is the contract you make with yourself, and with reviewers, about what you are actually doing.

## Pitching: get feedback early

Once the scoping document is accepted, you produce a **pitch**, a short walkthrough of your direction. Some challenges run live pitch sessions. Others ask for a recorded video or a slide deck with speaker notes.

The pitch is **not the final submission**. It is an early solution direction. The goal is to let reviewers flag dead ends before you sink time into them.

A good pitch covers:

1. **The question**: what you understood the challenge to be asking.
2. **Your direction**: the shape of your answer, not the answer itself.
3. **The evidence you will need**: what data, research or experiments are still ahead of you.
4. **The risks**: what would change your answer.

> **Tip:** A pitch that says "here is my approach, here is what I am uncertain about" almost always lands better than one that says "here is my answer, here is why I am right". Working professionals do not pitch certainty too early.

## Common mistakes

These are the patterns we see most often, roughly in order of how much they hurt your submission:

- **Skipping scoping entirely.** Going straight to the deliverable is the fastest way to produce a thin submission.
- **Treating scoping as administrative.** It is not paperwork. It is where you do most of the thinking. A few hours of scoping can save many hours of redoing work.
- **Pitching the final answer.** The pitch is for direction, not conclusions. Save the conclusions for the final submission.
- **Ignoring reviewer feedback on the pitch.** If reviewers flag a dead end, change direction. Pitches that ignore the feedback tend not to be accepted at the final submission stage.
- **Confusing thoroughness with quality.** A tight, well-bounded scope produces a better deliverable than a sprawling one. Reviewers prefer focused over comprehensive.

## What is next

After scoping and pitching you are into production, the work that becomes your final deliverable. If you are on the challenge with others, read [Teams and collaboration](/docs/students/teams-and-collaboration.md).

Otherwise, jump to [Final submission](/docs/students/final-submission.md) for what done looks like.
