What this template actually does
A Weeklies Tracker is a shared document where communities log individual boss kill times so everyone can see the leaderboard for that week's competitive runs. The Template For Elden Ring Boss Weekly is basically a spreadsheet that standardizes how those entries are recorded — columns for player name, timestamp, specific build notes, and the actual boss clock time. I've been maintaining one for roughly two years across three different Discord servers. The original creator just used Google Sheets with basic conditional formatting, and it still works fine for most groups. The reason people keep recreating it is that the first versions never account for split-brain issues when two players claim the same time.
Getting the Template For Elden Ring Boss Weekly set up
The easiest path is using a Google Sheets base. Here is what you need: After that, you set up a pivot table or a simple SORT formula ranked by time ascending per boss. The SORT function in modern Sheets makes this take maybe thirty seconds to configure. I usually add a second sheet for historical records because weekly resets erase context and people always come back later asking why someone's three-month-old PB was disqualified. Keeping everything in one workbook prevents that problem entirely.
Common mistakes people make
The biggest issue I see is letting anyone edit the time column directly. Without locked cells and restricted edit permissions, you get typos, intentional inflation, and the usual confusion. I switched to a submission form approach where players fill out a Google Form and the responses auto-populate the sheet. It slows down the entry process by maybe twenty seconds but eliminates like ninety percent of the problems. Another thing: people don't always realize that Elden Ring bosses have multiple phases that count toward the final time differently. Malenia's second phase doesn't reset your timer in official leaderboards, but casual trackers sometimes count it wrong. I learned this the hard way when a player submitted a 1:42 run on Malenia that looked suspiciously fast, and I caught it because the split times in their stream clip didn't match the claimed total. The workaround was requiring a timestamped clip link in Column F and manually verifying runs under a certain threshold — anything faster than the current top three times for that boss gets a manual review before it posts to the leaderboard.
Get the Full Details
How it performs in practice
For a small community of twenty to fifty regular runners, a single-sheet tracker handles the load without issues. The SORT formula recalculates instantly even with a few hundred rows. Once you push past about eight hundred entries per boss, you will start seeing minor lag on open, and the conditional formatting slows things down. At that point switching to a database or at least splitting the data into separate monthly sheets helps. The main limitation of any template like this is proof verification. The spreadsheet itself cannot validate that the time is legitimate. It only displays whatever gets entered. I have seen entire leaderboards compromised because one person figured out they could share a friend's clip and submit it under their own name. The template does nothing to prevent that. You need a separate moderation system — usually just one person assigned to review borderline entries. If your group is large or competitive enough to need strict validation, you might be better off using something like Speedrun.com's tooling or a dedicated leaderboard platform instead of a spreadsheet template. Those platforms handle proof uploads, dispute resolution, and version history natively.
Download options
The base template for most communities lives on Google Sheets. Search for "Elden Ring Boss Weeklies" and you will find several forks. The most reliable ones include built-in data validation on the time column so you cannot accidentally type text instead of a number, and a pre-configured SORT formula that you just copy into a new sheet each week. My current version is a shared Google Sheet with a forms submission layer and a read-only leaderboard view. I do not publish the public link here since these things tend to get forked and abandoned within a few months, but the structure is straightforward enough that rebuilding it takes about ten minutes if you already know what columns you need.
