How to run a weekly scrim ladder that survives month two

Week one is exciting. You build the listing, you post it everywhere, people turn up, it runs well. Week two is nearly as good. Somewhere around week five or six the novelty has worn off for you and not yet compounded for anyone else, and you are still doing every piece of admin by hand.

The players did not leave. You did. Attendance was fine and you stopped, because a two-hour event was costing you five hours and you had already answered the same forty questions five times.

So the whole design goal of a weekly series is to make week ten cost less than week one. Everything below serves that.

Every variable you re-decide weekly is a tax you pay weekly. Decide these once, publicly, and stop revisiting them:

• The day and the time. Same slot, every week, permanently.
• The slot count. Not "however many turn up".
• The format. Changing it weekly means re-explaining it weekly.
• The rules. One document, reused verbatim.
• The entry fee and prize structure, if any.
• The reveal offset and check-in window.

Pick one time in one timezone and publish it in UTC

With a global player base there is no time that suits everyone, and trying to rotate to be fair means nobody can build a habit. One fixed UTC slot lets a player decide once whether the series works for them. Fragnet renders times in each viewer’s own zone, so nobody has to do the conversion.

Weeknight or weekend

Weeknights favour shorter formats and consistent regulars. Weekends allow longer formats and draw more casual entrants, but compete with everything else. For a series, weeknights compound better — habit is worth more than reach.

Match the format to the slot, not the reverse

A three-hour window is a 16-team single-elimination best-of-one, or a four-match points series. It is not a double-elimination bracket, and finding that out live in week one damages a series before it starts.

• Formats and how long each takes

Rebuilding a listing weekly is the largest single chunk of avoidable work in a series. Clone last week’s event, change the date, publish.

• Changes each week: the date, the title if you number them, and the room credentials.
• Never changes: format, slots, device, region, skill tier, rules, fee, prize structure, reveal offset, check-in window.

Once that is true, publishing week ten is about ninety seconds of work. That is the difference between a series that survives and one that quietly stops.

Approving every request by hand is fine at 16 slots and miserable at 64. Decide which problem you have.

• Instant join for open, free events. First come, first served, no queue to work through. The right default for a ladder that wants volume.
• Manual approval when there is an entry fee, or when you need to check rosters.
• A skill tier on the event, so a stacked roster is discouraged from a beginner ladder rather than declined afterwards.
• The experienced-organizers filter is for players choosing events — but knowing it exists is a reason to build your own track record early.

Bulk approve exists precisely for the weekly case: forty requests, thirty-eight of them fine.

A weekly series has predictable attrition: some proportion of people who registered on Monday will not be there on Thursday. Fighting that is pointless; absorbing it automatically is not.

1. 1.Let the event fill and let the waitlist grow. A waitlist is not a problem to solve — it is the buffer.
2. 2.When a confirmed player withdraws, the next person is promoted automatically and notified. You do not have to be watching, which matters because the drop-outs happen while you are setting up.
3. 3.Use the check-in window to convert no-shows into promotions before the lobby opens rather than after.

• Approval queue and waitlist

Run the same sequence every week until it stops requiring thought. Each row maps to a field you configure once.

Regulars need less warning than a one-off audience. Once your series has an established core, a shorter offset — five to ten minutes — is safe and reduces the leak window, because everyone is already waiting.

Keep it longer while you are still growing and half the lobby is new each week.

The season table is what turns ten separate events into a series worth returning to. Fragnet has no leaderboards and no skill progression, so this part is yours.

1. 1.One public spreadsheet, one row per player or team, one column per week.
2. 2.Link it from every listing, in the links field, so it is never more than one click away.
3. 3.Update it within an hour of finishing. A table updated three days later stops being a reason to come back.
4. 4.Decide the season length up front — eight or ten weeks — so there is a finish line rather than an indefinite grind.

• Post results fast. Nothing signals "this is run properly" more cheaply.
• Ask participants to review the event. Ratings appear on every future listing and are what convince week-twelve newcomers.
• Let teams keep rosters between weeks rather than re-registering individuals.
• Name the regulars in your results post. Recognition is the entire prize pool for most amateur series.
• Never move the slot. One reschedule costs more regulars than a bad night does.

Three weeks of falling attendance in the same slot with the same format is information, not failure. Either the slot is wrong, the format is wrong, or the audience is not there — and running week eleven out of obligation will not tell you which.

Announce a final week, finish the season properly, and publish the standings. A series that ended cleanly is a track record. One that faded out is a page of dead listings.

• Organizer guide
• Rules template