Experiments, Demonstrations, and Engineering Projects: What’s the Difference?

When a child wants to enter a science fair, the first decision is often: experiment, demonstration, or engineering project? The answer determines the research plan, the kind of data you collect, and which fair rules apply. This article explains the three categories, shows how to pick the best fit for a 6‑14‑year‑old, and offers a concrete example that can be built with everyday household items.

What Is an Experiment?

An experiment follows the scientific method. You start with a question, formulate a testable hypothesis, and then manipulate one or more independent variables while measuring the effect on a dependent variable. Repeated trials and controls are essential for reliable conclusions. The ISEF‑affiliated rules require a research plan that includes hypothesis, variables, and data analysis for any project classified as a “Science Project”^[1].

What Is a Demonstration?

A demonstration simply shows how something works. It does not involve a hypothesis or variable manipulation. As the BYU‑EF guidance notes, “Demonstration projects are not permitted” as fair entries because they lack the experimental structure that distinguishes a true experiment^[2]. Demonstrations are still valuable learning tools—think of a baking‑soda volcano that illustrates gas release—but they belong to classroom show‑and‑tell, not to a competition entry.

What Is an Engineering Project?

Engineering projects address a specific need or problem. Instead of testing a hypothesis, you define a design goal, generate and evaluate alternative solutions, build a prototype, and iterate based on testing results. The engineering design process mirrors the steps shown in the JAX guide: define the problem, specify requirements, create alternatives, build, test, and redesign as needed^[3]. Winning fair entries in the “Engineering Project” category must include an engineering plan that describes the need, target user, and functional goal^[4].

How to Choose the Right Project Type

Use the decision criteria below to match a child’s interest, resources, and grade level with the appropriate category.

• Goal of the activity: Do you want to discover a cause‑and‑effect relationship (experiment), illustrate a principle (demonstration), or create a functional solution (engineering)?
• Presence of a hypothesis: If you can write a statement like “If I increase the amount of sugar, the solution’s boiling point will rise,” you’re set for an experiment.
• Need for a design requirement: If the project begins with “I need a device that can filter muddy water for a garden,” it’s an engineering project.
• Fair rules: Most fairs, including ISEF‑affiliated events, reject pure demonstrations^[2]. Check the Minimum Quality Requirements to ensure your plan meets the chosen category^[1].

Worked Example: Building a Simple Water Filter

This example shows how the same everyday idea can become an experiment, a demonstration, or an engineering project.

Step 1 – Choose the Goal

1. Experiment: Test how the amount of sand affects water clarity.
2. Demonstration: Show how layered materials can slow the flow of water.
3. Engineering: Design a filter that clears at least 90 % of visible particles from garden runoff.

Step 2 – Plan the Procedure

• Experiment:
  • Hypothesis: Adding more sand will increase turbidity reduction.
  • Independent variable: grams of sand (0 g, 10 g, 20 g).
  • Dependent variable: percent of particles removed, measured with a simple light‑through‑water test.
  • Control: identical filter without sand.
• Demonstration:
  • Layer cotton, charcoal, and sand in a bottle.
  • Pour muddy water and watch the flow slow.
  • No data collection needed; the visual effect is the result.
• Engineering:
  • Define need: a portable filter for a small garden.
  • Specify requirements: fits in a 1‑liter bottle, removes ≥90 % of visible particles, costs <$5.
  • Generate alternatives: charcoal‑sand combo, coffee‑filter‑paper, commercial filter.
  • Build prototype, test with the same muddy water, record % removal, and iterate.

Step 3 – Record and Analyze

For the experiment and engineering versions, use a simple table to log grams of sand, trial number, and measured clarity (e.g., % light transmitted). Graph the results to see trends. The engineering version adds a design‑evaluation matrix comparing cost, weight, and performance of each prototype.

Comparison Table

Common Mistakes to Avoid

• Turning a demo into an experiment without variables. Simply adding a “look” at the result does not create an independent variable. Define a measurable change (e.g., amount of material) before starting.
• Writing a hypothesis for an engineering project. Engineering focuses on meeting design criteria, not proving a cause‑and‑effect relationship.
• Skipping controls. Even in engineering tests, a baseline (unchanged design) helps evaluate improvement.
• Ignoring fair rules. Submitting a pure demonstration to a competition that requires a research plan will lead to disqualification^[1][2].

Next Steps for Parents and Teachers

1. Review the fair’s Minimum Quality Requirements to confirm the chosen category is allowed.
2. Help the child write a brief project statement that matches the appropriate template (research plan for experiments, engineering plan for design projects).
3. Use the simple water‑filter example as a template: decide on a goal, list required materials (bottle, sand, charcoal, cotton), and set up a data table before the first trial.
4. Encourage reflection after each trial: what worked, what didn’t, and how the design could be improved.

By clarifying the difference between experiments, demonstrations, and engineering projects early, families can choose a project that meets fair standards, aligns with the child’s interests, and provides a rewarding learning experience.