Evaluation identity
Connect each scorecard to the right pitch.
Identify the startup, division, round, and evaluator. Controlled lists keep one team's responses together.
- Startup name or team ID.
- Judge name and assigned panel.
- Division and round.
Describe your competition and rubric. Makeform turns the brief into a startup pitch evaluation form with shared criteria, conflict disclosure, evidence notes, and recommendations.
Route judging responses to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a scenario, revise its rubric, or send the editable example into the Makeform builder.
Audience
Mentors and investors evaluating an accelerator cohort
Format
Weighted 1–5 scorecard with recommendation
Prompt size
351 chars
Example judging structure
Weighted 1–5 scorecard with recommendation
Judge, startup, and conflict disclosure
Problem, solution, market, and model
Team, traction, and pitch delivery
Evidence behind your scores
Final recommendation
Suggested routing tags
Finalist
Discuss
Not advancing
Define what 1, 3, and 5 mean so judges interpret the scale consistently.
Step 1
Identify
judge, startup, round, and conflict
Step 2
Score
shared criteria with clear anchors
Step 3
Explain
evidence, strengths, and concerns
Step 4
Decide
recommendation ready for panel review
A fairer scorecard
Separate pitch dimensions, ask judges what they observed, and keep a useful record for deliberation.
Use the same criteria, ranges, and anchors for every startup so teams are assessed against shared priorities.
Weight customer validation or impact above presentation polish, and show each point maximum.
Collect evidence, a concern, and a diligence question so judges can explain their totals.
Designed around the round
Edit the criteria, terminology, scale, and decision options for your competition.
Balance discovery, traction, market, team, and delivery.
Separate divisions, confirm eligibility, and use a points rubric.
Add conflicts, mission fit, feasibility, budget, impact, and conditions.
Keep mobile scoring brief while retaining strengths, concerns, and ranking bands.
Judging workflow
Build and test the rubric, then route evaluations into one review workflow.
Name the round, judges, criteria, weights, anchors, required comments, and recommendation options.
Review labels, require conflict disclosure, confirm maximums, and test the form for unclear criteria.
Send one judging link, use startup-specific links, or embed the form in the competition portal.
Route evaluations to the organizer and review totals, score spread, conflicts, and evidence.
Rubric vs notes vs applause
Consistent scores and context help the panel understand disagreement.
Field guide
Use these six sections to capture each score and its rationale.
Evaluation identity
Identify the startup, division, round, and evaluator. Controlled lists keep one team's responses together.
Conflict handling
Ask about financial, advisory, employment, or other relationships before scoring, then follow your conflict policy.
Criteria & anchors
Separate problem, validation, differentiation, market, model, traction, team, and delivery. Add evidence-based scale anchors.
Weights & totals
Give priority evidence larger maximums. Specify any total formula, automatic ranking, and tie treatment during setup.
Evidence & diligence
Require an observation for exceptional ratings and the question a judge would pursue next.
Recommendation
Use decision labels such as advance, discuss, reserve, or decline. Keep recommendations separate from totals.
Related tools
Collect entries, structure scoring, and gather post-event feedback.
FAQ
Practical answers for competition organizers designing a consistent and useful judging process.
It is a scorecard for each startup pitch. It identifies the startup and judge, presents shared criteria and anchors, collects evidence and conflicts, and ends with a recommendation for panel review.
Common criteria include problem clarity, customer evidence, differentiation, market, business model, traction, team, feasibility, and delivery. Choose what matters to the round: an idea contest may emphasize insight and feasibility, while a demo day may weight traction more heavily.
Use one narrow rubric with anchors for low, middle, and high scores. Calibrate judges with a sample pitch, require comments for exceptional scores, and review score spread instead of treating the average as the whole decision.
Yes. Set a point maximum or weight for each criterion and show it beside the question. Specify any calculated total, ranking, and tie-break formula in the prompt, then test the workflow before live judging.
Independent scoring before discussion limits early influence. Organizers can then compare criterion totals, rationale, spread, and conflicts. Decide who may access individual responses and explain that process before judging.
Ask about financial, advisory, employment, family, or other relevant relationships. Provide yes, no, and unsure options plus a private explanation. State whether disclosure means recusal, limited participation, or organizer review.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and reuse the scorecard across judges and competition rounds. The paid tier removes the Makeform badge.
Standardize startup and judge names, then route responses into one table. Compare criterion totals, evidence, recommendations, conflicts, and score spread. Use outliers and ties as discussion prompts rather than relying only on an aggregate.
Give every pitch the same clear standard.