๐ฐ Budget & Funding ยท Engineer ยท Intermediate
Cost as a Design Constraint
Cost isn't accounting โ it's an engineering input. A budget limit is a hard constraint that eliminates design options before you start. This guide shows how to integrate cost into your decision matrix and how to document it so judges see the constraint was real.
The constraint test: If your budget constraint didn't eliminate or change any design decision, judges won't believe it was a real constraint. You need decisions where the cheaper option was chosen specifically because of cost, documented before you built it.
โ Integrating Cost into Your Decision Matrix
Most teams score their decision matrix on performance criteria only โ speed, reliability, game-piece capacity. Adding a Cost row changes outcomes in realistic ways and directly satisfies the rubric.
The cost criterion should be weighted to match its actual importance. If your budget is tight, weight cost at 25โ30%. If the district has funded everything generously, weight it lower (10โ15%) but still include it. The weight signals to judges how binding the constraint was.
Scoring cost: Use an inverse scale โ lower cost scores higher. Rate the cheapest viable option as 9โ10 and the most expensive as 1โ3. This makes cost compete directly with performance on the same scale.
๐ฎ Interactive Decision Matrix
Drivetrain Configuration โ Weighted Decision Matrix
Adjust criterion weights to see how cost changes the outcome. Weight total = 100.
Remaining 15% goes to Build Complexity
| Configuration |
Performance
ร30 |
Reliability
ร30 |
Cost
ร25 |
Build Complexity
ร15 |
Weighted Score |
| 4-Motor (current budget) |
7 | 8 | 9 | 9 |
โ |
| 6-Motor (over budget) |
10 | 9 | 3 | 6 |
โ |
| 4-Motor + Pneumatics |
8 | 6 | 5 | 5 |
โ |
๐ฐ Common VRC Cost Tradeoffs to Document
These are the decisions where cost realistically changes the outcome. Document the ones that applied to your build.
| Decision | Cheaper Option | More Expensive | Cost ฮ | When to Choose Cheap |
|---|
| Drivetrain motor count |
4-motor $160 |
6-motor $240 |
+$80 |
When other subsystems need the motor budget; when game doesn't heavily reward defense |
| Sensor package |
IMU only $30 |
IMU + GPS $110 |
+$80 |
When field tiles are consistent; when auton paths are simple and repeatable |
| Actuation type |
Motor actuated $40โ80 |
Pneumatics $80โ150 |
+$40โ70 |
When you have motor allocation available; when multiple actuations per match are needed |
| Frame material |
Steel C-channel ~$3โ5/piece |
Aluminum ~$6โ8/piece |
+~$2โ3/pc |
When weight limit is not a constraint; low-stress structure (base plates, shields) |
| Motor cartridges |
Reuse existing (free) |
New green/red/blue $15 ea |
+$15/motor |
When existing cartridges are in good condition โ test RPM before assuming they're degraded |
| Rubber/flex wheels |
Flex wheel ~$5 ea |
3D printed tread custom |
Flex cheaper |
Almost always โ custom tread costs 3D print filament and time, rarely outperforms Flex |
๐ Writing the Constraint Statement
The constraint statement should appear in the notebook at Kickoff, before any design decisions. Template:
"The team's available parts budget for the 2025โ26 season is $[X] for build components. The district covers Brain, Controller, and batteries (combined value ~$500). This budget constraint eliminates [specific options] and requires that drivetrain motor count stay at or below [X] to preserve budget for [subsystem]. Any design decision costing more than $[threshold] per component requires team approval before purchase."
Fill in real numbers. "$700 for build components" is a real constraint. "We had a limited budget" is not. Judges have seen hundreds of notebooks. Vague language reads as post-hoc justification. Specific numbers read as real planning.
Bill of materials cost trade-offs apply constrained optimization: maximize robot performance subject to a fixed budget constraint. Each part represents a trade-off point on the performance-cost curve. The Pareto frontier — the set of choices where you cannot improve performance without increasing cost, or reduce cost without reducing performance — is the target. Parts below the Pareto frontier are dominated choices: another option delivers more performance per dollar.
🎤 Interview line: “We analyze every major parts decision as a constrained optimization: maximum robot capability within our $400 budget. We map each option on a performance-per-dollar axis and select from the Pareto frontier. This framework prevented us from defaulting to the most expensive or most familiar option.”
You need aluminum c-channel. VEX sells it for $18; a local supplier sells equivalent stock for $7. What determines the correct choice?
⬛ Always use VEX parts — only VEX parts are legal
⬛ Always buy cheaper — maximize your parts budget
⬛ Verify the local stock meets VEX material rules, check lead time, and factor shipping — then document the decision with rationale
📝Notebook entry tip: Appendix — Grey slide — Build a cost comparison table for every major purchase decision: VEX price vs alternative, legal status, delivery time, and your choice with one-sentence rationale. A table that shows your team actively sourced parts demonstrates cost engineering — judges notice the difference between teams that manage a budget and teams that just spend one.