Skip to content

Build Blog Post — Template

One post per build session. Written before anyone leaves the shop. Rotating student author — not a mentor.

Purpose: an absent student can read this and know what happened. A sponsor can read this and see the season. Next year's team can read this and learn.

Rules:

  • One screen tall. If it grew past a screen, cut.
  • One paragraph per subteam, one photo per subteam.
  • Blockers are called out explicitly. Don't hide bad nights.
  • Post it in the team blog / channel / repo before shop close.

Template

# Build Blog — YYYY-MM-DD (Session #N, Week W)

**Attendance:** N students, M mentors.
**Author tonight:** <student name>.
**Session goal (from stand-up):** <one line>.

---

## Subteam 1 — Drivetrain & Chassis
<one paragraph. What moved. Cards touched. Test results. Photo below.>

![](path/to/photo.jpg)

## Subteam 2 — Game Mechanism
<one paragraph.>

![](path/to/photo.jpg)

## Subteam 3 — Software & Controls
<one paragraph. Include PR numbers merged and any sim/log results.>

![](path/to/screenshot_or_photo.jpg)

## Subteam 4 — Electrical & Integration
<one paragraph.>

![](path/to/photo.jpg)

---

## Blockers Going Into Next Session

- <blocker 1 — who is waiting, on what, since when>
- <blocker 2>

## Decisions Made Tonight

- <decision 1 — one line. Echo any chat-only decisions here so they exist on the record.>

## Tomorrow's Priority

- <one line per subteam>

---

*Cards touched:* #123, #145, #150, #151
*Failure log entries added:* #14, #15
*ECRs opened:* ECR-08

What Goes In, What Stays Out

In:

  • Concrete progress ("intake pivot machined, installed, first spin test passed").
  • Failed tests with the failure logged.
  • Decisions made — especially anything decided in chat that would otherwise vanish.
  • Photos of the work, not the team posing.
  • Card / PR / ECR numbers so the record links back to the board.

Out:

  • "Everyone worked hard tonight."
  • "We made great progress." (What progress?)
  • Blame. Failure entries name the failure, not the person.
  • Long meeting minutes. Decisions only — one line each.
  • Marketing tone. This is an engineering log, not a press release.

When A Subteam Did Nothing

Say so. One line: "Subteam 4 held for parts on the PDH order; no work tonight." Silence looks like a missed post.

Post-Event Variant

Event nights replace subteam paragraphs with:

  • Match record (W-L, ranking).
  • Notable failures and pit repairs.
  • Scouting takeaways for the next day.
  • Driver adjustments planned.
  • One photo from the field.

Same rules: one screen, real content, blockers named.

Comments