# How challenges work

> A challenge on Ewance is a short, project-shaped brief modelled on real professional work. Here is the anatomy of one.

A **challenge** is the unit of work on Ewance. Everything else (the certificate, the recruiter view, the catalogue) sits around it.

If you have used a course platform before, the easiest way to understand a challenge is to contrast it with what you are used to.

## A challenge is not a course

| Course platform | Ewance challenge |
| --- | --- |
| Watch a video, answer a quiz | Read a brief, produce a deliverable |
| Pass or fail based on multiple choice | Reviewed against a stated rubric |
| Certificate confirms you watched | Certificate confirms you shipped |
| Generic curriculum | Project-shaped, discipline-specific |

A challenge starts as a **brief** that lays out:

- The scenario: who you are working for in the fiction, and what they need.
- The deliverable: what "done" looks like, such as a deck, a report, a circuit or a campaign concept.
- The constraints: time, budget, technical limits, audience.
- The rubric: what reviewers will look for when they evaluate your submission.

You see most of this on the challenge page before you commit. There is no surprise after you start.

## The three layers of a challenge

Every brief is composed of three layers. They appear in the same order on the catalogue page.

### 1. Title

The line that hooks you. A title like *"Design a low-power sensor cluster for a glacier-monitoring station"* tells you the field, the constraint and the deliverable in under fifteen words. If the title does not grab you, skip the challenge. There are plenty more.

### 2. Executive summary

One paragraph. The brief in miniature: the scenario, the deliverable, the constraint. If you cannot picture the work from the summary, the challenge is probably not right for you. Move on.

### 3. Full description

The full brief: scenario, deliverable, constraints, rubric. Read this carefully before you commit. The clearer the brief, the cleaner your final submission will be.

## What makes a good challenge for you?

A good rule of thumb: **pick a challenge you would want to talk about in an interview.** If the work would make you proud to walk a recruiter through it, the credential will be worth earning. If it feels like an exercise that looks identical to everyone else's, pick a different one.

The catalogue covers areas such as:

- **Engineering**: mechanical, electrical, structural, aerospace, biomedical.
- **Computer science and data**: back-end, machine learning, security, data engineering, distributed systems.
- **Business and strategy**: market entry, operations, finance, go-to-market, M&A.
- **Life sciences**: clinical reasoning, public health, biotech commercialisation, lab design.
- **Design and creative**: product, brand, campaign, UX research.
- **Social sciences and policy**: research design, programme evaluation, policy briefs.

Filters let you narrow by discipline, time commitment and team format.

## Where do the briefs come from?

Briefs come from two sources:

- **Ewance's editorial team** writes most of the catalogue. Briefs are designed in-house, modelled on real professional work without being transcripts of any specific company's project.
- **Industry partners** are companies that sponsor a brief directly. You work on a problem shaped like a real company's priorities, and the sponsor reads your submission. Sponsored briefs are flagged on the challenge page.

## What you produce, you keep

A challenge is your work. You keep the intellectual property in everything you submit. This is covered in [Who owns your work?](/docs/students/who-owns-your-work.md). The short answer is "you".

## The journey

A challenge runs through four milestones. Each gets its own page:

1. [Scoping and pitching](/docs/students/scoping-and-pitching.md): what you do before you start producing the deliverable.
2. [Teams and collaboration](/docs/students/teams-and-collaboration.md): solo, classmate pair or mixed-discipline squad.
3. [Final submission](/docs/students/final-submission.md): what done looks like and how review works.
4. [Certificates](/docs/students/certificates.md): what is issued when your submission is accepted.

Next: [Scoping and pitching](/docs/students/scoping-and-pitching.md).
