Checklist
MIT study checklist A workflow for MIT students to survive the weekly pset grind, hit lab deadlines, and use collaboration the way MIT actually intends it.
Built for MIT · STEM students working through intensive problem sets and labs.
Progress 0 of 12 tasks complete
Copy remaining Lay out the firehose Every class drops a pset, and labs run on their own clock. Get the whole term on one page before the second week buries you.
Stack all pset release and due dates side by side Most courses post psets weekly on a fixed day. Line up release-to-due windows across classes so you can see which Thursdays turn into double-pset nights. ~40 min Mark lab checkpoints on a separate track Lab reports and checkoffs do not follow the pset rhythm. Give them their own lane so a writeup deadline never hides behind a problem set. ~25 min Budget the true hours each pset took last time A six-problem set rarely fits one sitting. Use the hours you actually spent before, then add slack for the one problem that breaks you. ~20 min
Open every pset solo first MIT collaboration only works if you arrive with your own attempts. The first pass belongs to you alone.
Read all problems the day they drop Skim the full set early so your brain chews on the hardest problem in the background before you ever sit down to write. ~25 min Push each problem to your personal wall Solve alone until you genuinely stall, then write down exactly where the logic broke. That note is what you carry into the group. ~120 min Pre-derive the model the lab will assume Labs expect you to walk in knowing the underlying theory. Re-derive it the night before so bench time goes to data, not setup. ~35 min
Collaborate, then rebuild it yourself Group sessions exist to compare approaches and break blocks, not to copy. Reconstruct every solution in your own hand.
Trade sticking points with your pset group Bring your specific wall to a standing group block and explain your attempt out loud; teaching the stuck step often unsticks it. ~90 min Re-solve each problem from a blank page After the group, close the notes and rebuild it. If you cannot reproduce it cold, you understood the room, not the problem. ~50 min Hit office hours with a written attempt TA queues run long. Arrive with your derivation already on paper so help lands on the real gap instead of the setup. ~30 min
Close the loop before the next drop Psets recycle into exams. A short weekly debrief keeps the firehose from erasing what you just earned.
Tag every miss by the idea it tested Sort errors into a concept log so you re-learn the principle, not the specific numbers, before midterms cluster. ~25 min Redo the two problems that beat you Pick the hardest two from the returned set and solve them again from scratch days later to confirm the idea stuck. ~45 min Reserve next week's worst collision now Look ahead, find the day two psets and a lab collide, and block a long session for it before it becomes a 2 a.m. surprise. ~15 min
Common mistakes Showing up to a pset group with a blank page, so the session turns into copying instead of comparing Letting lab writeups pile up behind psets until two reports come due on one night Joining the office-hours queue with no attempt and losing the slot to basic setup questions Reading the pset for the first time the evening it is due, after the hard problem needed days to marinate Treating a returned pset as finished instead of mining it for the exact concepts the exam will reuse Pro tips Skim the whole pset the hour it drops so your subconscious works the hard problem all week Rebuild group solutions from a blank page before you trust that you understand them Keep labs on a separate calendar track so a writeup never collides with a pset due date Carry a written derivation into office hours so scarce TA minutes hit your actual wall Re-solve the two problems that beat you a few days later to lock the idea before exams FAQ How should I start the MIT study checklist? Start with the first phase, then run one timed Study Spaces sprint before adding more tasks. The goal is execution, not a perfect plan.
What should I do if I fall behind? Copy the remaining tasks, pick the highest-score or highest-deadline item, and restart with one focused block.
How often should I review progress? Review after each sprint and once at the end of the week so the next session starts with a clear first task.
Use it now
Turn this page into a live sprint Start the matching room for MIT, then use the sprint plan as the first task and recap script.
MIT study checklist
Focus target: MIT
Block 1 (25 min): closed-book recall or one timed practice set.
Break (5 min): mark confusing items without opening a new task.
Block 2 (25 min): correct misses and write the next first step.
Done: one score/error note plus one queued task for tomorrow.