Tracking Boss Defeats Without Losing Your Mind

Most players I know eventually stop caring about which bosses they have and haven't killed. The game doesn't really push you toward completion anyway, and your spreadsheet of defeats just sits there doing nothing. But a handful of people actually want that checklist, and I'm one of them. The Elden Ring Boss Worksheet Daily is essentially a community-built tracker that maps every major boss encounter onto a single sheet. You mark it off when you win, note how many times you died, and sometimes add something about your build or strategy. The sheet breaks down into three sections: main story bosses, optional overworld bosses, and demigod-level encounters. Each entry has columns for date attempted, attempts needed, level at the time, and a notes field. That's it. No fancy graphics, no automated checks, just a plain grid you fill in manually. The layout forces you to confront how many attempts each fight took, which is either motivating or depressing depending on your patience threshold. One thing people miss when they first look at it: the sheet includes placeholder rows for bosses that aren't strictly mandatory but still count toward the 14-16 demigods most players need to face. Margit, Godrick, Rennala, Radahn, Morgott, Rykard, Mohg, Malenia, and Maliketh form the core path, but the sheet also tracks things like Fire Giant, Hoarah Loux, and Godfrey as separate line items even though they're technically optional in most runs.

How to Use It Without Getting Overwhelmed

Open the sheet and sort by the area they appear in rather than following the natural story order. The default listing goes chronologically by when bosses show up in your journey, but if you follow that blindly you will spend six hours fighting Margit repeatedly while your level barely moves. Instead, grab a printout or keep it open on a second screen, then route yourself through Limgrave first, hit Godrick, move to Stormveil, and keep pushing until you naturally hit the next cluster. The worksheet updates in real time as you fill it, so you can see gaps in your coverage without constantly cross-referencing a second source. The attempts column is the most useful field. Write the number down honestly. I spent four nights trying Margit with a pure strength build because I refused to switch tactics, and the worksheet recorded 17 attempts before I finally just rolled into a different approach and beat him in three tries. That data point alone saved me more time than I care to admit because it forced me to admit I was being stubborn about my build. There is a practical problem though. The sheet doesn't auto-detect whether you defeated a boss through standard combat, summons, or a specific glitch strat. I encountered this directly when I used a fire monolith exploit against Godrick that technically counts as defeating him but doesn't give you the usual satisfaction or upgrade runes. The worksheet has no way to flag that distinction, so other players looking at my sheet would assume I did it the normal way. The workaround is simple: use the notes field to write something like "exploit" or "summon heavy" next to the attempt count. It's manual but it keeps the record honest.

Common Mistakes People Make With This Tracker

Don't pre-fill bosses you haven't actually defeated yet. I saw multiple threads where people marked themselves complete on Mohg because they watched a video of it and thought they understood the mechanics. You haven't defeated him. He will melt you for twenty minutes straight the first time. Wait until you actually kill him, then update the sheet. Another issue is the level column. Some people skip it because they don't want to track their progress, but that column is where patterns emerge. If you consistently fail a boss around level 50 and then pass it at level 55, you now know that boss scales harder than others in that range. If you ignore the level data entirely, the worksheet becomes just a decorative checklist and loses most of its practical value. The demigod section tends to get people into trouble because not every listed demigod is required to trigger the ending. The sheet counts all eight, but you technically only need to beat four to progress the main story. I learned this the hard way after spending two full days hunting Radahn and Mohg when I already had enough runes and upgrades to move forward. The worksheet didn't prevent that mistake, obviously, but it did make the wasted time visibly obvious once I went back to review the filled columns.

Get the Full Details

Elden Ring Boss List (v5) - Checklist | PDF
Elden Ring Boss List (v5) - Checklist | PDF

Where the Worksheet Falls Short

It doesn't track spirit ashes used, weapon upgrades, or any build-specific data beyond what you write in notes. If you want that level of detail, you're better off maintaining a separate document or using a game guide site with build tracking. The Elden Ring Boss Worksheet Daily is narrow by design, and that's both its strength and its limitation. It keeps things simple, which means it also leaves out a lot of information that could matter depending on what you're trying to achieve. There's also the issue of death counter accuracy. The sheet asks for total attempts, but it doesn't distinguish between full retries and deaths within a single run. I once counted 42 attempts against Malenia only to realize halfway through that I had been recording individual deaths instead of full boss attempts. That's a forty-two death count, not a forty-two attempt count. You can adjust by dividing or just re-doing the math, but it's easy to mess up if you're not careful from the start. Decide early whether "attempts" means full resets or individual lives and stick to that definition across the entire sheet. You can find the current version hosted on shared drive folders within the community Discord and on Reddit threads dedicated to speedrunning and completion tracking. Look for the most recent version with a 2025 date stamp, since the sheet gets updated whenever FromSoftware releases patches that alter boss behavior or add new encounters.