Practical Application and Project Work
What this domain tests
Practical Application and Project Work tests whether you can plan, make, test and evaluate a real product or performance. It rewards evidence of a design process, safe working, teamwork and honest reflection, not just a pretty final object.
Core rules and concepts
- Use a project cycle: identify a need → research → write a design brief and specification → plan materials, tools, time and budget → make → test → evaluate → communicate.
- A specification lists measurable requirements: size, strength, cost, safety, appearance, user and purpose.
- Plan a risk assessment: identify hazards, decide controls, keep first aid nearby, and supervise sharp or hot tools.
- Keep records: sketches, material lists, changes, test results and photographs. Evidence earns marks even when the product is imperfect.
- Teamwork needs roles, a shared plan, clear communication and fair work. A project where one person does everything is not a team project.
- Evaluation asks: Does it meet the brief? What failed? What would you change? Use test evidence, not opinion alone.
Worked example
Task: make a pencil holder from a clean plastic bottle, fabric scraps and glue. Reasoning: the brief is a holder that stands safely, holds at least five pencils and costs little. Specification: height 10 cm, stable base, no sharp edges, washable cover. Plan: cut the bottle with teacher supervision, cover the cut edge with tape, glue fabric, test stability with pencils, record a photo. Evaluation: it holds pencils but tips when pushed; add a wider base or sand for weight. That evidence improves the next version.
Traps that cost marks
- Starting to make before planning materials and safety.
- Writing a vague brief such as 'make something nice.'
- Ignoring sharp edges, fumes or unsupervised tools.
- Presenting a product without tests or evaluation.
- Letting one learner do all the work and calling it teamwork.