Competition Day Guide · Guide 01 · Night Before

Night-Before Preparation

Competition day starts the night before. The goal is not to squeeze in one more major technical session. It is to remove preventable setup problems and arrive rested, organized, and ready to make good decisions.

A stable device, accessible references, known logistics, and a rested team are more valuable than risky last-minute changes.

Night-Before Goal

EquipmentReady
ReferencesAccessible
LogisticsConfirmed
TeamRested

Night-before rule

Do not create a new problem while trying to prepare for tomorrow

If a competition device, account, or reference setup already works, avoid unnecessary changes that cannot be fully tested before the team goes to sleep.

Six preparation areas

Finish the night organized instead of rushed

Equipment

Confirm competition laptops or desktops are available and physically ready.
Pack chargers, power adapters, Ethernet cables, approved peripherals, and any required accessories.
Avoid unnecessary hardware swaps or last-minute upgrades on systems that already work.
Label shared equipment so the team can identify ownership quickly.

Accounts & Access

Confirm every teammate knows which approved accounts they are expected to use.
Verify access to required collaboration tools, local references, and team documentation.
Do not wait until competition morning to discover an expired password or inaccessible shared resource.
Avoid changing credentials unless there is a real reason and time to verify the result.

References

Organize approved local notes, command references, checklists, and platform guides.
Keep frequently used references easy to reach instead of buried in large folders.
Make sure references are readable offline when internet access may be restricted.
Remove duplicate or outdated copies that could confuse the team.

Logistics

Confirm arrival time, location, transportation, parking, and school or venue entry requirements.
Know who is bringing shared equipment and who has backup items.
Plan enough extra travel time so a small delay does not become a rushed arrival.
Confirm food, water, and break expectations if the event allows them.

Team Readiness

Confirm each teammate's likely platform or responsibility.
Review the communication plan and how the team will record status.
Identify any weak area that needs a short review, not a major late-night cram session.
Agree that high-risk technical experiments stop the night before.

Personal Readiness

Protect sleep instead of extending preparation deep into the night.
Pack clothes, identification, school materials, water, and any allowed personal items.
Set alarms and confirm wake-up time.
Leave enough mental energy for the competition itself.

Avoid tonight

High-risk changes that can wait

01

Major operating-system updates

02

Driver changes

03

BIOS or firmware updates

04

New virtualization platforms

05

Large tool installations

06

Unfamiliar security software

07

Bulk cleanup of team reference folders

08

Last-minute account migrations

09

Unverified network changes

10

Practice sessions that continue until teammates are exhausted

Readiness check

Confirm the basics before anyone goes to sleep

01

Competition device powers on normally.

02

Required charger is packed.

03

Ethernet cable is packed if needed.

04

Approved accounts are known.

05

Shared notes are accessible.

06

Offline references are available.

07

Arrival time and location are confirmed.

08

Transportation plan is confirmed.

09

Platform responsibilities are roughly assigned.

10

Team status method is chosen.

11

No risky technical change is still in progress.

12

Everyone has a realistic sleep plan.

Morning bag

Pack the items that are easy to forget

01

Competition device

02

Power adapter

03

Ethernet cable

04

Mouse or approved peripherals

05

Notebook and pen

06

Approved local reference material

07

Water

08

Identification if required

09

Any school or venue materials

10

Backup charger or cable if available

Weak habit vs better habit

Replace last-minute pressure with readiness

Weak habit

Stay up late and review everything one more time.

Better habit

Do one short targeted review, then protect sleep so the team can think clearly during the round.

Weak habit

Update the laptop tonight so it is fully current.

Better habit

If the working environment is already approved and stable, avoid unnecessary late changes that could create a new problem.

Weak habit

We will figure out roles when we arrive.

Better habit

Have a rough ownership plan before arrival so the first minutes are not spent deciding who handles what.

Weak habit

All our references are somewhere in the shared folder.

Better habit

Place the most useful competition references in a simple, predictable structure that works offline.

Weak habit

We can reset any passwords tomorrow if needed.

Better habit

Confirm expected account access before competition morning whenever possible.

Weak habit

One more long practice round will help.

Better habit

Use the final evening for confidence, organization, and rest rather than exhausting the team.

Final questions

Ask these before ending preparation

Q01

Can every teammate arrive with the equipment they are responsible for?

Q02

Can everyone access the approved references they need?

Q03

Are there any account or password problems still unresolved?

Q04

Is anyone planning a risky technical change tonight?

Q05

Does the team know its expected arrival time and location?

Q06

Does everyone know the rough platform ownership plan?

Q07

Is the team relying on any single cable, charger, or device with no backup?

Q08

Will everyone get enough sleep to make good decisions tomorrow?

Night-Before final checklist

End preparation with everything ready and nothing risky in progress

01

Competition equipment is packed and labeled.

02

Chargers and required cables are packed.

03

Approved accounts and shared resources are accessible.

04

Local and offline references are organized.

05

Arrival time, venue, and transportation are confirmed.

06

Shared equipment responsibility is clear.

07

Platform ownership is roughly assigned.

08

The team status method is chosen.

09

No unnecessary high-risk technical changes remain.

10

Morning alarms are set.

11

Personal items are packed.

12

The team stops preparation early enough to protect sleep.