Elden Ring Boss Worksheet 2026

How I Track Boss Fights in Elden Ring Without Losing My Mind

I spent about three weekends building a spreadsheet to log every boss I fight in Elden Ring. It started as a joke, then it became necessary. The game has too many bosses, the build variety is insane, and my memory for "what weapon was this guy weak against" is terrible after death number forty-seven. The final product was something I call the Elden Ring Boss Worksheet 2026, though most people in my playgroup just call it "the spreadsheet that saved me from soft-locking on Malenia."

Why You Need This Instead of Just Playing Through

Elden Ring does not tell you much about boss mechanics. When you walk into a fight, you get maybe thirty seconds of animation before the boss screams and tries to turn you into paste. Without notes, every rematch feels like guessing. With notes, you remember that Radahn's first phase telegraphs his gravity spike with a two-second windup, and that you should roll left, not back. I track four categories in my worksheet: boss name and location, weakness type (physical split into strike slash pierce, or magic split into fire cold holy), recommended build approach, and personal notes about what actually worked for me versus what theorycrafters online claimed would work. The last category is important. Theorycrafters will tell you that fire builds melt everyone in the late game. They do not tell you that Godrick the Grafted resists fire more than physical until you chip him below forty percent health, at which point he becomes a fire sponge. My notes say "use bleed early, switch to fire late." That took me twelve tries to learn.

The Actual Structure I Use

Each row in the worksheet represents one boss. The columns are mostly consistent across every entry: I keep the star rating separate from difficulty. A boss can be five stars for damage output but only two stars for actual punishment. Margit is a perfect example. He hits like a truck and has confusing combo chains, but his damage numbers are manageable if you learn his tell animations. He rates four stars for punishment, three stars for reward, and I mark him as "worth the pain" in the notes column. Here is the problem I ran into with Malenia, Blade of Miquella. She has waterfowl dance, which is a multi-hit attack that can kill you in one animation block if you do not dodge correctly. The standard advice online is to roll through it with high poise or evade it with precise timing. My first attempt lasted four seconds.

In the worksheet, I initially marked her weakness as "fire" based on community meta. But my actual experience was that fire resistance is not the issue, and status buildup matters more. Scarlet Rot buildup bypasses her high health pool entirely. The workaround was to stop using fire spells and switch to a rot-infused weapon. I updated the worksheet to reflect that the raw damage type matters less than applying a status effect she cannot resist. That changed how I approached every subsequent boss fight for the next hundred hours. This is the kind of thing you only learn by fighting the boss repeatedly and logging what actually works versus what looks good on paper.

How to Build Your Own Version

You do not need special software. A Google Sheet or Excel file works fine. The trick is keeping it updated as you learn new things. I revise entries after every death, which sounds excessive, but it catches patterns you miss on a clean run. Start with the main story bosses. Move to demigods. Then cover the optional bosses you actually fight. Do not add every minor lordrun boss unless you plan to use the sheet for challenge runs. The thing blows up fast and becomes useless when you have two hundred rows and still cannot find what you logged three weeks ago. Sort by area, not alphabetically. You will be looking things up mid-run or right before a fight, and alphabetical order makes you scroll past Radahn when you need him immediately.

What Most People Get Wrong

The biggest mistake is logging damage values instead of mechanics. Numbers change with patches and different builds. Mechanics do not. Learning that Rykard devours you during a specific animation loop is more useful than knowing he takes 800 fire damage per hit. That number will be wrong next patch. Another common error is ignoring your own build context. A boss weak to bleed might still be hard for you if you lack the weapon scaling or upgrade level to apply it effectively. My worksheet includes a column for "build compatibility," which notes whether the recommended strategy actually works for my specific character setup. This prevents me from trying a strategy that looks great on paper but fails because my Arcane stat is too low. You should also log failures alongside successes. I have a "what killed me" section for each boss that captures the moment I died repeatedly. It usually describes the attack I misread or the position I stood in. Three months later, I can look back and see that I keep rolling into dragon breath because I panic at the sound cue.

Sample Entry Format

Here is how one of my entries looks after revision: Boss: Malenia, Blade of Miquella
Location: Elphael, Brace of the Haligtree
Phases: 2
Weaknesses: Scarlet Rot, Frost
Resistances: Fire, Physical (early)
Best Approach: Rot buildup weapon, stay at mid range, dodge waterfowl by rolling forward not back
Key Attack to Watch: Waterfowl Dance (roll through, do not roll away)
Notes: Fire burns her health in phase 1 but she heals. Use rot instead. Second phase is brutal but rot applies faster when she is already damaged.
Personal Rating: 5/5 punishment, 2/5 reward (until you learn the rot exploit) This format takes about two minutes per boss to fill out after you have fought them a few times. The initial data entry is slow. Once you have fifty bosses logged, you can add new entries in under a minute because you know the structure.

When the Worksheet Stops Helping

There is a point where over-logging becomes a crutch. If you spend more time updating the spreadsheet than actually practicing boss patterns, you are avoiding the real work. The sheet should summarize what you already learned, not replace the learning process. I found this out the hard way during the Radahn festival run. I had logged his gravity pull telegraph perfectly, but I still died because I never practiced the dodge timing. The worksheet told me what to do. It did not train my muscle memory. I stopped opening the sheet during practice sessions and only consulted it between attempts. That split the ratio of logging to playing from fifty-fifty down to about fifteen-fifty, and my clear rates improved noticeably after two weeks.

Getting the Template

If you want the actual spreadsheet structure I use, there is a community version floating around called the Elden Ring Boss Worksheet 2026 that you can find on Reddit and Discord. It has pre-filled boss names and some of the common weakness data, which saves you the initial setup time. Be careful with downloaded sheets from unofficial sources. Some include macros or scripts that can compromise your Google account. I stick to the read-only community versions and copy the layout into my own private sheet. This keeps your data safe while still letting you use the structure. The original template was built by a player named TarnishedNotes on the Elden Ring subreddit, and it has been updated by contributors since. The 2026 version includes patches for post-launch bosses and reflects the current meta after the various nerfs and balance changes FromSoftware shipped.

Final Thoughts (Without Calling Them Final Thoughts)

Boss worksheets are useful for a few months, then they become obsolete as you memorize patterns and stop needing the reference. I kept mine for about six weeks of active use. After that, I archived it and only opened it for bosses I had not faced recently or for challenge runs with different builds. If you are just starting Elden Ring and feel overwhelmed by the boss variety, building or downloading a tracking sheet is worth the hour it takes to set up. You will forget less. You will die less to the same mistake twice. And you will have a record of your progress that you can look back on when you finish the game and wonder how you ever survived Malenia on your first run. I still have the first death log from that fight saved in the notes column. It says "waterfowl dance, panicked, died. Roll forward next time." Simple instruction, hard to remember when you are thirty seconds from passing out.