💰 Budget & Funding · Notebook · Intermediate
Budget Section of Your Engineering Notebook
🗺️ Flowchart — Budget tracking workflow
Every expense gets a notebook entry. Receipts + categorization + running total. At season end, this becomes the budget audit.
flowchart TD
Start([Expense incurred]) --> Receipt[Keep the receipt
or screenshot of order]
Receipt --> Log[Log to budget sheet:
date, vendor, item,
amount, category]
Log --> Total[Update running total
vs season budget]
Total --> Q1{Over budget?}
Q1 -->|"Yes"| Alert[Flag in notebook
discuss with mentor]
Q1 -->|"No"| Done([Logged])
Alert --> Decide[Decide:
cut other expense?
seek more sponsorship?]
Decide --> Done
style Start fill:#1e293b,stroke:#22d3ee,stroke-width:2px,color:#e2e8f0
style Done fill:#1e293b,stroke:#22c55e,stroke-width:2px,color:#e2e8f0
style Q1 fill:#fbbf24,color:#0f172a,stroke:#fbbf24
style Alert fill:#7c2d12,color:#fef3c7,stroke:#fbbf24
Four coaching prompts for recording the budget constraints and decisions your team actually encountered. They are not required entries or a promise of a rubric score.
Spartan coaching: These examples and prompts teach a method; they are not entries to copy or a required notebook format. Record your team's actual work, including uncertainty and failed tests, in students' own words. Never invent earlier decisions or results. See our student-centered policy guidance and current notebook rubric reference. The official GRSF rubric controls if this guide conflicts with it.
Budget work can provide evidence in several current rubric areas when it explains real engineering decisions:
| Current area | Example evidence to consider |
|---|
| Define | Actual funding limits, their sources, and implications for feasible designs. |
| Develop Solutions | Alternatives considered, cost estimates, evidence, and reasons for a decision. |
| Reflection & Iteration | What actual costs changed in subsequent engineering or planning. |
Record the timing honestly. State when a constraint became known and which decision it affected. A later BOM is still useful evidence; do not pretend it existed before the build.
📅 Four Suggested Budget Topics
Illustrative calculation, not team data: If a build allocation is $680 and drivetrain spending is $250, $430 remains for other systems. If a $40 replacement allowance becomes $120 in actual spending, the variance is $80 over budget. Use your own verified figures and explain the decision they affected.
Season budget: questions your entry should answer
What funding was actually available, when, and from which sources?
Which items were supplied separately? Record verified amounts and sources, not sample prices.
Which design constraints followed from those limits? Who made the decisions?
What remains uncertain, including travel or future fundraising?
Component cost constraints: questions your entry should answer
What subsystem allocation was known at the time? What remained for other systems?
Which feasible alternatives did your team consider, and what evidence supported each cost estimate?
Which option did you choose, why, and what did you give up?
If you used a matrix, link your actual comparison. If this is later analysis, label and date it as such.
Existing technical example: For Override, 6 × 11W = 66W exceeds the 55W drivetrain cap cited in R11a. Check feasibility as well as cost when comparing configurations; this example is not your team's recorded decision.
Bill of materials: questions your entry should answer
Which actual robot version does the BOM describe? When and how were prices checked?
What are the subsystem subtotals and total? Separate supplied items from team spending.
Which figures are estimates? What remains available for replacements?
Link your own BOM and any actual comparisons; do not copy another team's alternatives.
Budget reflection: questions your entry should answer
What did you plan to spend and what did you actually spend? Calculate the difference.
What caused the differences, and what records support that explanation?
Which engineering decisions changed as a result?
What would your team change next time, and why?
Mistake 1 — Unclear timing. Link the BOM to the robot version and date it represents. Distinguish original constraints from later cost analysis.
Mistake 2 — No alternatives considered. "Here is our parts list" is accounting. Explain the alternatives your team actually evaluated and why you rejected them. Without alternatives, you have no evidence the constraint changed any decision.
Mistake 3 — Vague numbers. Record the actual allocation and spending with sources. Explain what the figures meant for your choices; numbers alone do not establish a score.
Mistake 4 — District items not separated. Include the Brain and Controller at their real cost, but clearly label them "district-provided — not from team budget." This shows awareness of the full program cost and builds credibility with judges who know what things cost.
Budget notebook entries apply cost engineering — the systematic documentation of cost decisions as engineering decisions. In professional engineering, every significant procurement is documented with rationale: what was purchased, at what cost, and why this option was selected over alternatives. This traceability allows budget audits and demonstrates that cost was a conscious design input.
🎤 Interview line: “Every significant parts order generates a budget notebook entry: item, supplier, cost, and one sentence explaining the engineering rationale. "Chose 11W motor cartridge over 5.5W to reduce stall risk on the intake mechanism, accepting an $8 cost increase" is a cost engineering entry. Judges can trace every dollar to a documented design decision.”
Which budget entry best demonstrates engineering judgment to a judge?
⬛ "Spent $45 on polycarbonate sheets."
⬛ "Ordered 3 sheets of 1/8" polycarbonate ($45, Robosource) for custom intake guards. Chose poly over aluminum: absorbs impact without cracking and saves 60g — accepted higher material cost for weight reduction."
⬛ "Parts ordered this week: poly sheets, screws, bearing flats."
📝Notebook entry tip: Appendix — Grey slide — Every parts order should generate a notebook entry: item, quantity, source, cost, and one sentence explaining the engineering reason for the choice. Teams that justify purchases — not just list them — demonstrate cost-conscious design thinking. Over a season this becomes a complete procurement record that judges can trace to specific design decisions.