Strong words with no proof read as wishful thinking. These documentation failures rarely show up in a quick read-through but reliably weaken a submission.
Failure 1 — The dead or locked link. For 2026 the documentation form and video are entered through the submission portal. The classic mistake: any linked Google Doc/Drive folder is set to 'restricted,' so judges hit a login wall.
Fix & test: set sharing to 'Anyone with the link — Viewer,' then open it in a private/incognito window with no account. If it opens cleanly, you're safe. Do this for any documentation link AND any video link.
Failure 2 — Missing or mismatched Doc IDs. The form requires you to 'Label each piece of documentation with a "documentation ID"' and attach the pieces 'in order of Documentation ID.' Submissions where the chart says ID-014 but no such file exists make the packet untrustworthy.
Fix: run a reconciliation — list chart IDs in one column, file IDs in another, and confirm a 1:1 match with no gaps. Page 1 is the chart; pages follow in ID order.
Failure 3 — Only self-generated evidence. A folder of your own Instagram screenshots proves you posted, not that you mattered. The form explicitly invites stronger types: 'letter, screenshot, photo, thank you card.'
Fix: aim for a majority of third-party, unsolicited proof — partner thank-you letters, grant award letters (5985 cites a '$125k government grant' and a '$512k STEM project'), press coverage, school or government letters. Ask partners for a short letter while the event is fresh; chasing it in January is too late.
Failure 4 — Unverifiable or inconsistent numbers. If your essay says you mentor 14 teams but your documentation lists 9, judges notice. The official Definitions warn teams not to 'embellish or exaggerate these numbers' and to 'estimate on the low end' when in doubt.
Fix: every headline number traces to a source — a tracker row, a TBA query, a sign-in sheet. Keep numbers consistent across executive summaries, essay, presentation, and documentation. When unsure, round down; a defensible 'mentored 9 teams' beats an indefensible '15'.
Failure 5 — Documenting everything except the small wins. Teams capture big events and forget the recurring small ones that prove sustained commitment.
Fix: the A-I-E tracker habit from the worked-examples module — log immediately after each activity. The best evidence is a quote captured the same day, not reconstructed months later.
Pre-submission documentation audit (run this once):
- Open every submitted/linked item incognito — all load without login?
- Chart IDs and file IDs reconcile 1:1 with no gaps?
- Majority of evidence is third-party?
- Every essay number has a source and matches the documentation?
- All evidence dated within the last 3 years?
Five yeses, or you keep fixing.
the part worth keeping
Key takeaways
- Open every submitted/linked item (documentation, video) in an incognito window — a login-locked or dead link is a wasted, score-killing artifact.
- Reconcile chart Doc IDs to evidence files 1:1 with no gaps, and keep every number consistent across summaries, essay, presentation, and docs.
- Prioritize third-party unsolicited evidence (partner letters, grant awards, press) and capture quotes the same day — the Definitions warn against exaggeration.
The Impact AwardCommon Mistakes & Troubleshootinglesson 3 of 4
Keep going
Take the quiz+10 XP with an accountMore in Common Mistakes & Troubleshooting
where this came from
Sources and corrections
This lesson is AI-assisted: drafted from primary sources, then reviewed and edited by hand. Errors still get through. When one is reported we fix it and write down what changed, in public, in the corrections log.
sources and further reading
- firstinspires.orgFIRST Impact Award Documentation Form (Doc ID rules)
- firstinspires.orgFIRST Impact Award Definitions (no embellishment / estimate low)
- community.firstinspires.org2026 Season Award Updates — FIRST Community Blog
clipped to this lesson
Articles that go further on this
The lesson gets you through the topic. These go wider on it, and they read in one sitting.
- 6 min readFRC Scouting Sheet Template: Printable Paper Sheet + Google Form to Sheets SetupA ready-to-print FRC scouting sheet plus a Google Form to Sheets setup that auto-averages one row per scout into per-team stats, with a 2026 REBUILT note./blogread it
- 13 min readWPILib Won't Deploy: Every Cause and How to Fix ItYour WPILib deploy is failing? Work the decision tree: wrong folder in VS Code, team number, roboRIO image, JDK version, macOS network privacy. Fixes for each./blogread it
- 8 min readFRC CAN Bus Explained (and How to Fix Common Problems)How the FRC CAN bus works, the daisy-chain wiring with 120-ohm termination, avoiding device ID conflicts, and fixing the most common CAN failures./blogread it
answer sheet
Lesson quiz
All 3 right completes the lesson. Miss one and only that question comes back, anything you already answered correctly stays banked.
0 of 3 answered
01How can you confirm that a shared documentation or video link will not hit judges with a login wall?
02What reconciliation step helps prevent a mismatched-Doc-ID packet?
03What makes a documentation packet's evidence strongest?
Answer every question to submit.
All 30 lessons in The Impact Awardopenclose
01 / prerequisites
02 / understanding-the-impact-award
03 / building-the-written-submission
04 / presentation-interview-and-video
05 / building-a-program-worth-recognizing
06 / worked-examples-and-mini-projects
- Not read yet:Build a Living Impact Tracker (Spreadsheet Mini-Project)
- Not read yet:Automate Outreach Data with The Blue Alliance API
- Not read yet:Worked Example: Rewriting a 500-Character Executive Summary
- Not read yet:Mini-Project: An Outreach Event Playbook You Can Reuse
- Not read yet:Mini-Project: Assemble a Bulletproof Documentation Form
07 / common-mistakes-and-troubleshooting
08 / advanced-techniques-and-case-studies