Clarity is a kindness to your reader#
A judge reading dozens of submissions has limited energy. Every confusing sentence costs them effort, and effort spent decoding your grammar is effort not spent appreciating your impact. Clear writing isn't about sounding smart. It's about being understood the first time.
Think of it like code. In WPILib you'd never write a tangled method when a short, well-named one does the job. Bloated prose is the writing version of spaghetti code: it technically runs, but nobody wants to read it, and bugs (misunderstandings) hide inside.
Concise doesn't mean short#
Concise writing uses the strongest words, not always the fewest. You're cutting dead weight, not meaning. The highest-value moves:
- Cut filler phrases. "Due to the fact that" becomes "because." "In order to" becomes "to." "At this point in time" becomes "now."
- Use strong verbs, not verb + noun. "We made a decision to" becomes "we decided to." "We conducted an analysis of" becomes "we analyzed."
- Be specific. A specific word is usually shorter than a vague one plus its explanation. "Our outreach program" is vaguer and often longer than "our free Saturday robotics club."
- Trim redundancies. "Future plans," "end result," and "collaborate together" each repeat themselves. Drop a word.
Prefer active voice#
Active voice names who did the action, which is exactly what a judge wants to see your team doing.
- Passive: "A curriculum was developed and was used by three schools."
- Active: "We developed a curriculum, and three schools now use it."
The active version is shorter, clearer, and credits you. Passive isn't always wrong, but reach for active first.
One idea per sentence#
When a sentence tries to carry three ideas, split it.
- Hard to follow: "After we noticed that local middle schoolers had no access to robotics, which mattered to us because many of us also lacked that access growing up, we decided to start a club that we ran on Saturdays."
- Clear: "Local middle schoolers had no access to robotics, and neither did many of us growing up. So we started a free Saturday club."
A self-edit pass#
After your first draft:
- Read it aloud. If you run out of breath or stumble, the sentence is too long.
- Hunt for -ion and -ment words (implementation, development, engagement). They usually hide a stronger verb. "The implementation of the program" becomes "we launched the program."
- Delete one word from every sentence. Most survive intact.
- Count characters. The essay caps at 10,000 characters including spaces, and each executive-summary answer at 500. Here, conciseness is a hard requirement, not just style.
Every word you cut buys room for another number or vivid detail. In a 500-character answer, trimming "in order to facilitate the process of" down to "to" frees space for a real outcome. Cutting words literally lets you say more.
the part worth keeping
Key takeaways
- Clear writing reduces a judge's effort so they can focus on your impact, not on decoding your sentences.
- Concise means using the strongest words and cutting dead weight, not just writing less.
- Replace filler ('due to the fact that' to 'because') and weak verb phrases ('made a decision' to 'decided').
- Prefer active voice ('we built X') because it is shorter and credits your team.
- Self-edit by reading aloud, hunting -ion/-ment words, and deleting a word per sentence; then check against the 10,000-character essay and 500-character answer limits.
The Impact AwardFoundations: Storytelling and Clear Writinglesson 2 of 3
Keep going
Take the quiz+10 XP with an accountMore in Foundations: Storytelling and Clear Writing
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
- owl.purdue.eduConciseness (Purdue OWL)
- owl.purdue.eduActive and Passive Voice (Purdue OWL)
- owl.purdue.eduEliminating Wordiness Exercises (Purdue OWL)
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.
- 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
- 20 min readHow to Program FRC Swerve Drive with WPILibA practical guide to programming FRC swerve drive with WPILib: kinematics, SwerveModuleState, field-relative control, odometry, and where PathPlanner fits./blogread it
- 7 min readFRC "Loop Time of 0.02s Overrun" & Watchdog Not Fed: Causes and FixesWhat "Loop time of 0.02s overrun" and watchdog-not-fed warnings actually mean in FRC, how to read WPILib's epoch dump, and the usual causes./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
01What does concise writing actually do?
02Which revision best improves 'A curriculum was developed and was used by three schools'?
03Why does conciseness matter especially for the executive-summary answers?
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