Describe your divisions, awards, and rubric. Makeform turns them into a science fair judging form with shared criteria, student feedback, and one record per project.
Send judging responses to Google Sheets, Slack, and Zapier.
Sample prompts for your judging rubric
Choose a prompt, adapt the criteria to your fair, or send it into the Makeform builder. Each example is a practical starting structure, not a completed judging decision.
Audience
Volunteer judges rating grades 3–5 projects
Format
Friendly five-point rubric with comments
Prompt size
285 chars
Example judging structure
Friendly five-point rubric with comments
Judge and project details
Scientific question and investigation
Display and student explanation
One strength and one next step
Conflict-of-interest confirmation
Suggested routing tags
Elementary division
Middle school division
Special awards
Define what each score means before judging starts. A five-point scale is only consistent when judges can distinguish a 3 from a 4.
Step 1
Identify
judge, project code, division, and category
Step 2
Score
the same anchored criteria for every project
Step 3
Explain
evidence notes, strengths, and next steps
Step 4
Review
totals, flags, ties, and award nominations
Consistent judging
A clear rubric guides judges through project identification, score anchors, evidence, and a complete record.
Sequence the question, method, data, conclusion, presentation, and interview criteria identically for every booth.
Pair numbers with observable guidance so judges share a definition of quality.
Capture the observation behind each score and feedback more useful than a number.
Fair-ready structure
Use project codes and conditional sections to organize criteria by category, age group, round, or award.
Use controlled choices for grade band, category, and round.
Show design criteria for engineering entries and investigation criteria for experiments.
Capture judge, assigned group, and project code without student contact details.
Collect nominations, tie-break notes, and follow-up flags as filterable fields.
Build your rubric
Define the decisions judges make, then test the rubric with a sample project.
Name the divisions, criteria, points, awards, and required questions.
Verify weights and define adjacent scores with observable evidence.
Submit strong and developing samples; confirm required fields catch omissions.
Review responses by project code, division, total, nomination, and follow-up flag.
Scoring method
The best judging method makes criteria visible at the moment of scoring and preserves the reasoning needed to review close results.
Field guide
Six focused sections give organizers enough structure to compare projects while leaving judges room to explain what they observed.
Project record
Use a stable project code, then capture title, division, category, round, and judge. Dropdowns keep category labels consistent.
Research question
Ask whether the question is focused, testable, and supported by relevant background. Score reasoning rather than topic complexity.
Methods
Score repeatability, controls, measurement, iteration, and whether the method addresses the stated question or design need.
Evidence
Ask whether observations support the analysis, limitations are recognized, and the conclusion follows from the evidence.
Presentation
Score whether the display communicates the work and students explain choices, results, and next steps. Note team participation when relevant.
Feedback and awards
Require a strength and next step. Add nominations, tie-break notes, conflict confirmation, and a separate organizer flag.
Related tools
Use separate forms for registration, entries, judge preparation, student feedback, and event follow-up while project codes connect the records.
Collect student, project, category, and participation details before judging assignments are made.
Open toolAdapt another criteria-based judging pattern for poster or visual presentation awards.
Open toolAccept entries, category choices, descriptions, and supporting materials in a structured intake form.
Open toolCollect image-based entries and entrant details for a photography category or companion contest.
Open toolAsk students about preparation, judging day, and what they learned after the fair ends.
Open toolCreate a separate observation or evaluation workflow for educators and program facilitators.
Open toolFAQ
Practical answers for organizers designing rubrics, coordinating judges, and reviewing results.
Include judge and project IDs, division, category, scoring criteria, point scales, evidence comments, feedback, conflict confirmation, and award recommendations. Keep organizer flags separate from the score.
Give each criterion a description and anchored scale. Train judges with one sample project, compare their reasoning, and revise language they interpret differently.
Use weights when some dimensions matter more. Show each section's maximum, verify the intended total, and avoid distinctions judges cannot apply reliably.
Yes. Show relevant sections after category selection. Experimental entries may need controls; engineering entries may need constraints and iteration. Retain shared criteria for fair-wide awards.
Require one observed strength and one constructive next step. Keep comments respectful, age-appropriate, and focused on the project and explanation.
Require a reason with each nomination. For close results, review criterion scores and evidence notes. Set the tie-break process before judging and record the panel decision separately.
Yes. Makeform offers unlimited free forms and responses. You can generate, edit, share, and collect judging submissions on the free plan; the paid tier removes the Makeform badge.
A published form opens from a shared link. Keep labels concise, group criteria, avoid long grids, and test the devices and venue network before judging.
Make every score easier to explain.
