Q&A Oficial: Judging

Could you clarify exactly what teams are expected to submit for the three summaries from a student/team perspective?

Specifically, are the Season Summary, Code Summary, and Credit Summary separate documents or forms, similar to the Innovate Form used in the past?

How and when should teams submit them to judges? For example, if they're separate documents should they be included at the front of the Engineering Notebook.

Yes, they are three separate one-page documents, not a combined form like the old Innovate Form — a Season Summary, a Code Summary, and a Credit Summary, each its own page (Credit Summary can run longer if the source list is long).

At the event: Print each summary as a loose page and place all of them at the front of the engineering notebook — not bound in, not paper-clipped to the back, and not tucked in a pocket folder buried in the middle. This lets a Judge Advisor open the notebook and find them immediately to sort and route notebooks, without flipping through the whole thing.

After the event: The loose pages have done their job for that tournament. Rather than discarding them, transcribe or paste them into the notebook as a dated entry — an event recap marking what the team knew, built, and could do at that point in the season. Do this after every event.

During the season: Keep an appendix in the notebook collecting every summary submitted at past competitions this season, in competition order. The recap entries tell the season's story inside the main notebook narrative; the appendix keeps the original documents together for quick reference. By the last event of the season, the appendix should hold every summary submitted so far.

None of this changes what goes in a summary or how it's scored (see the Season, Code, and Credit Summaries for Judging article for that) — it's only a filing practice for where copies live before, during, and after an event.