Give Clear Feedback as a Mentor or Judge
What you will leave with
A mentor or judge leaves able to read an entry fast, compare it fairly with the rest, and give feedback the founder can act on.
Reviewing founder work should not start with a file hunt.
On IdeaToVenture, founders share work in the same shape. You get oriented fast: the work, the proof, and the gaps sit in one place. Entries are easier to compare because each one shows the same kinds of items.
Your part is the judgment. Good feedback is clear and kind. It points at the work in front of you. It tells the founder what to test next.
A first-time founder does not need a long lecture. They need to know which claim needs proof, what seems unclear, and what next step would help.
Start With the Stage
Stage tells you what feedback will land. Before you comment, ask where the founder is:
- learning about a problem;
- testing demand;
- drafting early work;
- getting ready for a contest;
- sending work for program review;
- preparing for a funding talk.
A founder who is still checking the problem may not need a full money model.
Match feedback to the stage. Early ideas need sharper questions. Contest entries need to fit the score sheet and show clear proof.
Use the Work in Front of You
Each entry shows the same kinds of items: saved work, proof, and open gaps. That makes entries easier to compare. It also makes your comments easier to place.
Tie comments to the package you see. Try:
- "The problem is clear, but I do not see proof that the customer feels pain."
- "The talks show a problem, but I do not see who buys."
- "This market claim needs a reason, not just a big number."
- "The shared package has enough context, but the proof needs clearer labels."
This helps the founder know what to fix, test, or explain.
If the package is missing context, ask for the smallest missing piece. Do not ask the founder to rebuild everything.
Keep Safe Bounds
Do not state your view as a sure fact. Do not give legal, tax, finance, or investment advice unless you are hired to do that work outside the app.
Use:
- "The proof I would look for next is..."
- "A judge may ask..."
- "This guess looks risky because..."
- "Try testing..."
Avoid:
- "This will get funded."
- "This cannot work."
- "You should raise now."
- "This is legally safe."
Also avoid private data you were not allowed to see. If you received secure review access, stay within that package.
What to Review
For early work, look at:
- customer clarity;
- problem urgency;
- proof quality;
- value proposition;
- business model assumptions;
- go-to-market logic;
- founder next steps.
For a contest package, also check the score sheet, missing parts, story clarity, and proof.
For official judging, follow the program score sheet and conflict rules. Every judge scores the same locked review copy, so each entry is judged on the same basis. Secure review comments are not the same as official scores.
The Feedback Loop
When founders share clear work, you spend your time on judgment, not file sorting. Your notes help founders improve. Stronger packages make the next review round easier for everyone.
That loop is the point.
A Template Founders Can Act On
Use this structure:
- What is clear.
- What claim needs more proof.
- What risk matters most now.
- What next test would help.
- What the founder should update after the test.
Short, specific feedback is easy to act on. The founder can turn it into a next step and updated work.
Next Step
Point your feedback at the work, the proof, and the next test. Founders can act on that in the next version of their work.