LeetCode Tracker: Spreadsheet vs Notion vs App (Free Template)

LeetCode already tracks one thing for you: a green checkmark and a solved count. That tells you what you did. It doesn't tell you what you can still do three weeks later, in an interview, with someone watching. That gap is why people start keeping their own LeetCode tracker.

This guide covers what's actually worth recording, the three common ways to track (spreadsheet, Notion, dedicated app), a free spreadsheet template with spaced repetition built in, and what a tracker built for interview readiness does differently.

What a LeetCode tracker should record

Most trackers stop at "problem, difficulty, date." That's a log, not a tool. The columns that change how you prepare are the ones that capture how well you solved it and when to come back:

Field	Why it matters
Problem, link, difficulty	The basics — so you can reopen it fast
Pattern (two pointers, sliding window, BFS…)	Interviews test pattern recognition, not individual problems. Tagging patterns shows your weak spots
Solved without help?	A problem you solved after reading the editorial isn't solved yet. Be honest here
Confidence (1–5)	"Could I re-solve this cold, in an interview?" This drives your review schedule
Key insight (the why)	One sentence on why the approach works. This is what you actually need to recall
What tripped me up	Your personal mistake log — the highest-value thing to read before an interview
Next review date	Solved problems fade within days unless you revisit them on a schedule

The last one is the difference between a tracker and a diary. Without a next review date, you'll re-solve random old problems — or, more likely, none. (Why this matters: why you forget LeetCode solutions.)

Option 1: A spreadsheet (Google Sheets / Excel)

The most popular choice, and a good one to start with.

Pros

Free, flexible, and you own the data.
Formulas can compute your next review date and flag what's due.
Easy to sort and filter by pattern or difficulty to find weak areas.

Cons

Everything is manual: copying the title, link, tags, and your code.
You have to remember to open it. A due date nobody looks at does nothing.
Updating review streaks by hand gets tedious, which is usually when people stop.

Best for: anyone who wants a simple, free system and is disciplined about opening it daily.

Free template: LeetCode tracker with spaced repetition

We made the spreadsheet we'd want to use:

All the columns above, with dropdowns for difficulty and "solved without help."
Next review is calculated for you from your confidence rating: confidence 1–4 → review in 2 days; confidence 5 → 2 days, then 1 week, 2 weeks, and monthly as you keep nailing it.
Rows due for review turn red and show DUE, so "what do I review today?" is one filter away.
A "How to use" tab with the daily routine.

Download the LeetCode tracker template (.xlsx)

It opens in Excel or Numbers. For Google Sheets: create a blank sheet, then File → Import → Upload and choose the file — formulas and formatting carry over.

Option 2: Notion

Notion trackers look great and are popular as templates.

Pros

Pretty, flexible databases; easy to add long notes and code blocks.
Views by pattern, difficulty, or status in a click.

Cons

Same manual entry as a spreadsheet.
Date math for spaced repetition is clunkier than in a spreadsheet.
It's easy to spend more time designing the tracker than using it.

Best for: people who already live in Notion and want rich notes per problem.

Option 3: A dedicated tracker app or Chrome extension

Tools built specifically for LeetCode remove the bookkeeping.

Pros

Import problems from LeetCode instead of copying them by hand.
Review scheduling happens automatically.
Progress stats come for free.

Cons

You adopt someone else's structure.
Quality varies a lot — many only log submissions and don't help you review.

What to look for: automatic review scheduling (not just a log), a way to record how you solved it, not just that you did, and low friction getting problems in.

What CodingPartner does that a log can't

Every option above answers "what did I solve?" CodingPartner is a free LeetCode tracker built to answer a different question: "could I solve it in an interview?" Four things make that possible.

1. Every attempt is scored on what interviews actually test

LeetCode only tells you "Accepted." Interviewers grade much more than that. After each attempt, CodingPartner walks you through a structured reflection that checks the same things an interviewer watches for:

Algorithm recognition — did you identify the right pattern yourself?
Pseudo code — did you plan before coding?
Complexity analysis — could you state and justify time and space?
Bug-free — did it pass without trial-and-error submissions?
Test case design — did you come up with the edge cases?
Self test — did you dry-run your code before running it?

You also rate your confidence (1–5) and record your mistakes, common traps, and takeaways. Over time that becomes a personal, interview-ready mistake log attached to each problem, instead of notes scattered across apps.

2. A review schedule based on how memory actually works

Memory research on the forgetting curve is clear: information fades fast unless you actively recall it at growing intervals. CodingPartner turns that into a schedule you don't have to manage:

Your confidence rating sets the next review. 1–4 comes back in 2 days; 5 stretches to 2 days, 1 week, 2 weeks, then monthly.
A daily review list shows what's due. It stays short, so you actually finish it; you can pick more when you have extra time.
Reviews mean re-solving — active recall from a blank editor, not re-reading an old solution. (Why that matters.)

3. Progress you can see, not a solved count

A number that only goes up can't tell you if you're ready. CodingPartner's dashboard and stats track the signals that do:

Mastered ratio — how many problems you'd now rate a 5.
Trends over time — mastery and average solve time by difficulty.
Weak topics — which patterns still have low confidence, relative to how often you've practiced them.

That's how you know where to spend next week, and when you're ready.

4. One click from LeetCode, including your submission

The free Chrome extension adds a CodingPartner button to every LeetCode problem. One click imports the problem statement, topic tags, top companies, and your latest Accepted code, then opens a prefilled attempt. No copying titles and links into a spreadsheet.

And because consistency is the other half of the problem, you can team up with a friend on a weekly challenge and see each other's progress (why that works).

CodingPartner doesn't come with a fixed problem list. Practice from NeetCode, Blind 75, or anything else, and use CodingPartner to make what you solve stick.

Comparison

	Spreadsheet	Notion	Typical tracker app	CodingPartner
Cost	Free	Free	Varies	Free
Adding a problem	Manual	Manual	Often one click	One click, incl. your Accepted code
Scores the attempt on interview skills	No	No	Rarely	Yes (6 checks + confidence)
Next review date	Formula (template above)	Possible, clunky	Often automatic	Automatic, confidence-based
Daily "what to review" list	Filter	View	Varies	Built in
Progress & weak spots	Manual charts	Manual	Solved counts	Mastery, trends, weak topics
Staying consistent	On you	On you	On you	Weekly challenge with a friend

The best LeetCode tracker is the one you'll still be using in week six. If you like doing it by hand, start with the template. If you want the tracker to do the bookkeeping and tell you how interview-ready you are, use CodingPartner.

How to use any tracker so it actually works

Log right after solving, while the insight is fresh. Thirty seconds.
Rate confidence honestly. A generous 5 you can't reproduce just means you'll forget it again.
Review what's due before starting new problems. Re-solve from a blank editor; don't re-read your old code. (More on this: spaced repetition for LeetCode.)
Read your "what tripped me up" column before interviews. It's the most concentrated prep material you have.
Judge progress by confidence, not count. A solved count going up while confidence stays flat is the classic how many problems is enough trap.

Try it

Start using CodingPartner free — Google sign-in, no credit card. Import your next LeetCode problem in one click and let the review schedule take it from there.

Related: Spaced repetition for LeetCode · Why you forget LeetCode solutions · LeetCode with friends