Project 2026: Forests & Climate

Theme: Forests, Climate Change, and Biodiversity.
Deadline: Thursday, 19 March 2026.

View Official Brief (PDF)Get Full Project Support

Project 26 How to Submit

Watch this video for a complete walkthrough of how to submit your project to your teacher.

Submission Package

Submit a single zipped file named 2026-219-3-EV-EXAMNUMBER.zip containing two primary folders:artefact and report.

Directory Structure

2026-219-3-EV-EXAMNUMBER.zip
├─ artefact/
│  ├─ code/
│  │  ├─ model.py
│  │  └─ microbit.py
│  ├─ microbit/
│  │  ├─ program.hex
│  │  └─ extra.hex
│  ├─ data/
│  │  ├─ readings.csv
│  │  └─ calibration.csv
│  └─ docs/
│     └─ README.txt
└─ report/
   ├─ index.html
   ├─ video.mp4
   ├─ video/
   │  └─ demo.mp4
   ├─ images/
   │  └─ figure1.png
   └─ extras/
      └─ appendix.html
      └─ style.css

Important: Keep index.html at the root of the report folder. Include all micro:bit .hex files, Python scripts, datasets, and any README/instructions inside the artefact folder.

The Task

"Develop a functional embedded system that collects environmental data and simulates a real-world process related to the theme of forests... You will also develop a computer-based model... to test 'what-if' scenarios... Finally, you will incorporate a feedback mechanism to make the system adaptive."

The project combines Embedded Systems (ALT 4) and Modelling/Simulation (ALT 3).

Project Requirements

Basic requirements

Embedded system design
- Build a functional embedded system that uses at least one digital input and at least one analogue input.
- The system must generate at least one primary output which can be either digital or analogue.
- The system can be started or calibrated manually but should operate automatically once started.
Data collection
- Use your embedded system to collect and store environmental data that relates to your chosen theme.
- The stored data will be used as part of your model in the advanced requirements.
Process simulation
- Configure your embedded system to simulate a real-world process related to the theme (for example: canopy cover, drought cycles, biodiversity changes, population growth/decline, wildfire risk).
- Run tests to show how the system responds using different inputs or changing environmental data.

Advanced requirements (HL only)

Disaster risk modelling
- Using Python, develop a computer model of a chosen disaster risk scenario related to forests (for example: wildfire, drought, pest outbreak, air quality, landslides, flooding).
- Your model must use some data collected from your embedded system and can be combined with open-source data or simulated data.
What-if simulations
- Explore how your forest disaster risk model behaves under different conditions by creating and testing two "what-if" scenario simulations. Each scenario should involve changing one or more key variables and observing the resulting changes in system behaviour or predicted risk.
- What if temperature increases (drought conditions)?
- What if rainfall decreases (drought conditions)?
- What if tree density increases (afforestation)?
- What if the forest canopy is reduced (deforestation)?
- What if a species population grows too large or too small (for example: too many predators or too few pollinators)?
- What if high temperatures and low soil moisture increase wildfire risk?
Adaptive system
- Extend your system to include a feedback mechanism that enables it to adapt automatically to changing conditions (for example: triggering an alert when fire risk is high, watering a plant when soil moisture is too low, or adjusting predictions based on the most recent data).
- Note that the adaptive response can be either physical (extending the embedded system) or virtual (changing the model so that it adjusts automatically).

Report breakdown and marking (90 marks total)

The report is submitted as an HTML website (maximum 2500 words). Structure your submission so the Artefact and Report folders are separate and easy to navigate. The table below shows the marking breakdown and the key content expected for each section.

Section	Marks	Key content expected
The report (quality & layout)	5	Clear website structure and readable layout. Evidence of adherence to principles of good user interface design. Adherence to the word/video limits (penalties may apply).
1. Meeting the brief	27	Demonstrate how the artefact meets the basic requirements (OL & HL). Demonstrate how the artefact meets the advanced requirements (HL) where applicable. Include evidence: screenshots, logs, sensor data and demo video showing each requirement satisfied.
2. Investigation	10	Research on the brief, including existing solutions, systems or ideas aligned to the brief. Explain how your research informed design and implementation decisions.
3. Plan and design	18	Clear, detailed design objectives and justification of design choices. Consideration of stakeholders and end-user needs. Technologies to be used and a high-level system architecture/flowchart showing components and data flow.
4. Create	20	Describe key development milestones and testing performed. Explain one key problem encountered and how it was solved. Provide a full description of the model or embedded-system algorithm implemented as part of the project.
5. Evaluation	10	Evaluation of the final artefact: strengths and limitations. Validation of results and suggested improvements or further iterations with justification.
References & summary word count	0	Complete references / bibliography. Summary showing the report word count (include total).

Practical tips

Include a short demo video (max 5 minutes) linked from the Meeting the brief section.
Keep the report focused — show evidence for each requirement rather than long narrative prose.
Use clear figures, captions and labelled screenshots for the Create and Plan sections.

Submission checklist

Artefact folder (code, micro:bit files, datasets, instructions to run).
Report website with sections in the table above and the demo video embedded or linked.
References and word-count summary.

What We Offer

Guide Coming Soon

We are preparing a complete suite of resources for the 2026 project. Planned release ahead of the assessment period.

What we will provide

Complete Breakdown: Detailed analysis of the brief and marking criteria.
Step‑by‑step Guidance: Instructions for every Basic Requirement (OL & HL).
Advanced Walkthroughs: In‑depth guides for HL Advanced Requirements.
Video Guides: Short videos demonstrating implementation, Micro:bit coding, and simulation.
Sample Code: Python templates and Micro:bit debugging tips.
AI Tools (Gold): Idea generation, code debugging, and report writing assistance.

Report Support

We will provide a full report template and a walkthrough covering:

Introduction and context
Methodology and data collection
Design, implementation and testing
Evaluation, limitations and future improvements
References and appendices

Gold Member Benefits

Gold members will get exclusive access to:

AI tools to generate project ideas, sample code and debugging hints.
Assistance with Micro:bit Python code and simulation troubleshooting.
Help drafting and polishing report sections (methodology, evaluation, testing).
Priority support and sample solutions.