Skip to content

Codeforces Upsolve Worksheet

Use when: one Codeforces round or one short-round drill just ended, and you want the next actions to be precise instead of emotional.

Inputs:

  • one round problem list
  • your live solve order and submission history
  • one honest memory of what you believed during the round

Output artifact:

  • one queue of finish now / review later / reinforce topic
  • one exact repo door per meaningful miss
  • one system patch to carry into the next round

Done when:

  • you know what to upsolve first
  • you know what failure actually happened first
  • and you have one concrete workflow or retrieval change for the next short round

Fill In This Order

  1. write the real live category of each problem:
  2. ship
  3. close
  4. park
  5. log the first real leak, not the final embarrassment
  6. decide the exact next repo door
  7. choose one fresh follow-up rep only after the nearest miss is handled
  8. end with one system patch

Round Summary

Item Your answer
round name / link
format shape Div. 2 / Div. 3 / Educational / special
hacks or no hacks?
first shipped problem
first avoidable leak
did you misread the announcement? yes / no

Main Worksheet

Problem live category final status first leak minute you knew the idea next repo door follow-up rep system patch if repeated
A ship / close / park solved / unsolved / partial reading / model / implementation / anti-hack / proof / pacing
B ship / close / park solved / unsolved / partial reading / model / implementation / anti-hack / proof / pacing
C ship / close / park solved / unsolved / partial reading / model / implementation / anti-hack / proof / pacing
D ship / close / park solved / unsolved / partial reading / model / implementation / anti-hack / proof / pacing
E+ ship / close / park solved / unsolved / partial reading / model / implementation / anti-hack / proof / pacing

Upsolve Order Board

Use this default order unless you have a better reason:

  1. finish the best close miss first
  2. repair one repeated implementation or anti-hack leak next
  3. only then editorial-reconstruct the hardest parked problem
  4. finish with one fresh follow-up rep through Problem Finder

Failure To Repo Door

First leak Reopen
reading / statement compression Codeforces Playbook
implementation Codeforces Implementation Clinic 01, Stress Testing Workflow
anti-hack / rejudge fear Anti-Hack Workflow
constructive / many-valid-answers Codeforces Constructive / Validator-First Clinic 01 and Special Judge / Output Protocol Workflow
topic depth the corresponding ladder in Ladders
pacing / solve order Codeforces Short Round 01

One-Change Rule

Do not end the worksheet with five vague ambitions.

End with exactly one durable change:

  • one new edge-family check
  • one new note in your notebook
  • one rule about when to park a problem
  • one change to your short-round warmup
  • one exact ladder or topic revisit

Pair This With