A printable Everdell score sheet lives or dies on an argument almost no other game in this catalogue can produce: two players tied on points, tied even on the points their events earned, and the game decided by something nobody counted — how many events each of them achieved. Everdell scores only once, at the end, in five categories added in a fixed order, and its first tiebreak is not a points category at all. It is a count. Most Events achieved wins, and only if that is level does anyone look at leftover resources. So the table that added up its event points into one tidy number and then swept the event tiles back into the box has thrown away the exact fact the tiebreak needs, on exactly the night it needs it. Or the slower version of the same loss: a city of fifteen cards is dismantled while someone is still mid-count, a Prosperity bonus that depended on what else stood in that city can no longer be checked, the point tokens have been tipped back into the supply, and a four-point disagreement becomes a matter of memory and confidence. Every disputed Everdell finish is the same dispute in different clothes: five category totals nobody kept separate, a tiebreak count nobody recorded, and a city that no longer exists. That is the seller this vertical rewards. Not the seller with the prettiest woodland watercolour, because the board and the Evertree already come in the box and your buyer owns both. The seller whose sheet keeps the five categories in five lines, names the events behind the event line, prints the tiebreak strip in order — events achieved, then leftover resources — and is filled in before a single card leaves the table, so the argument ends at the sheet instead of starting there.
What a printable Everdell set actually contains (and why it is five lines, not one total)
An Everdell set is not a generic tally pad with a squirrel on it, and designing it as one is the first error in this niche. At minimum a serious set contains five things.
First, the category sheet itself, built for up to four players in the base game. Each player needs five separate lines — base points from the cards in their city, point tokens, Prosperity card bonuses, Journey points, and Event points — plus a total line that is plainly the sum of the five and nothing else. One box labelled "score" gives a buyer a place to write the current rumour. Five lines give them the audit trail that settles which category the rumour went wrong in.
Second, a city checklist sized to the game: fifteen spaces, three rows of five, with a reminder printed at its head that Event cards do not count against the fifteen. A player mid-count should be able to tick cards off the sheet against the city in front of them, so a card counted twice — or a sixteenth card that should never have been there — shows up on paper before it shows up in an argument.
Third, an events strip that records names and counts, not just points. Each achieved Event gets its name and its printed points written down, and the strip ends with a total count of events achieved. That count is the first tiebreak. A sheet that stores only the points has stored the less important of the two numbers.
Fourth, a tiebreak strip, printed in full, in order: most Events achieved; then most leftover resources. Two lines, each with a box per player, filled in before the board is cleared and before the resources are swept back into their piles. Almost no home-made sheet prints it, and it is needed exactly once — on the night two totals land on the same number and the room discovers that event points and event counts are different facts.
Fifth, the files themselves in the formats a download buyer actually prints: a clean US Letter version, an A4 version that does not shrink the category lines into handwriting traps, a multi-game league version for groups who play weekly and burn through sheets, and a large-print version. Everdell finishes late, under warm light, at the end of the longest scoring count in most collections. Type that was legible in your design preview at noon is not the test; the test is a tired player reading a Prosperity line correctly while three other cities wait to be counted.
The rules every buyer assumes (and the checks that enforce them)
Get any of these wrong on the sheet and the sheet is wrong, however pretty it is — so check a draft against this list before you list it.
Scoring happens once, after every player has passed, and the categories add in a fixed order: the base point values printed on the cards in your city, then all your point tokens, then the bonus points from your purple Prosperity cards, then points from your Journey workers, then points from your Basic and Special Events. The rulebook's own example is the check to design against: base points 22, point tokens 14, Prosperity bonuses 10 — three for the Wife, two for the Architect, five for the King — Journey 4, and Events 12, six for Performer in Residence and three each for Ministering to Miscreants and Grand Tour, totalling 62. If your sheet's worked example cannot reproduce 62 from those five lines, the sheet is teaching arithmetic it has not done.
The tiebreak counts events, not event points. If players tie, the player who achieved the most Events wins; if that is level too, the player with the most leftover resources wins — and the rulebook states no further tiebreak beyond that. A sheet whose tiebreak strip says "most event points" is wrong in the one line it exists to get right, and a sheet that invents a third tiebreak is making up a rule the game does not have.
Basic Events are worth three points each. Special Event points are whatever the tile prints, and they vary. A sheet that hard-codes every event at the same value will silently mis-score every special event worth more — which is to say, exactly the events players remember contesting.
A city holds a maximum of fifteen cards. Event cards do not count against that limit, and a city may hold only one copy of any Unique card, while Common cards may repeat. A checklist that counts events toward the fifteen, or that cannot flag a second Unique, fails at the physical audit it was bought to perform.
The Journey is an autumn-only decision with a printed price. In autumn, a player may send a worker on a Journey by discarding cards from hand equal to the points of the space chosen: the five-, four- and three-point spaces hold one worker each, the two-point space is shared, and the worker is worth the printed points at game end. A Journey line with no space to note which space was taken — and how many cards it cost — cannot be re-checked once hands are empty and the worker has been collected.
Passing ends a player's game, not everyone's. A player in autumn who cannot act, or chooses not to, passes and is finished; a passed player cannot be given cards or resources, and if every other player has also passed, whatever would have been given is discarded instead. Players finish at different times, so the sheet must be completable for a city whose owner passed twenty minutes ago, while the rest of the table is still playing.
Seasons do not move together either. Preparing for spring reactivates all of a player's green Production cards and gains a worker; summer gains a worker and lets the player draw two cards from the Meadow; preparing for autumn reactivates Production cards a second time and gains two workers. None of that changes the score sheet directly — it changes how much city a sheet may have to hold, and it is why a sheet built for a tidy ten-card game fails the tables whose autumn cities run to the full fifteen.
Point tokens arrive from more places than the obvious ones. A worker placed on another player's open Destination card earns that city's owner a point token from the supply. A token pile counted at the end with no way to sanity-check it against lines like that is a number the table simply has to trust — and the sheet's whole job is that the table should not have to.
And the expansions change the product, not the margins. Everdell's expansions add their own components and their own scoring concerns; the solo game against Rugwort scores by an entirely different formula as well. A base-game sheet does not record an expansion game honestly, and claiming it does is how a five-star listing earns a one-star review from the one buyer who checked.
A worked game, and the arithmetic, checked the hard way
Invent three players and count them in the open, the way your sheet will have to.
Ana's city holds cards worth 25 base points. She collected 9 point tokens, her Prosperity cards pay 10 bonus points, her Journey worker sits on the five-point space, and her three achieved Events — one special worth six and two worth three each — pay 12. Her five lines read 25, 9, 10, 5, 12, and her total is 61.
Ben's city is heavier and his lines read differently: 30 base points, 8 tokens, 7 Prosperity points, a Journey of 4, and Events worth 12 — but his 12 comes from four Basic Events at three points each. His total is also 61. Same total, same event points, and the game is not tied, because the next step is not another points column.
Cleo finishes on 58: base 22, tokens 14, Prosperity 10, Journey 3, Events 9 from three events. She also ends holding eleven leftover resources — more than Ana's six and far more than Ben's four. Her line is the second lesson the sheet teaches: resources are only the second tiebreak. They break a tie that survives the event count; they never top up a total, and the player holding the fullest storehouse can still simply finish third.
Now the tiebreak, in order, from the strip nobody clears the board before filling in. First, most Events achieved: Ben achieved four, Ana achieved three. Ben wins the game — at equal points and equal event points — because the tiebreak counts the tiles, not the points printed on them. Had the sheet recorded only event points, this game is unresolvable the moment the tiles go back in the box, and the table will re-litigate it from memory. Note also what does not happen: Cleo's eleven resources are never even consulted, because the first tiebreak already separated the leaders. Check the totals by hand before you trust them in a listing graphic: 61, 61, 58, settled four events to three. If your sheet cannot produce those lines, category by category, it is not finished.
What the channels actually take from a low-priced set
A score-sheet set is a low-priced download, which means the channel's arithmetic, not your effort, decides most of your margin — and it differs enough by channel that the same file is a good product in one shop and a bad one in another.
On a marketplace with a per-listing fee and a percentage, a cheap set pays the fixed slice on every single sale, so the percentage you think you are paying understates the real cut most at exactly the price point score sheets sell at. Bundling solves part of this honestly: a base set, an expansion set and a league pack sold as one listing pay the fixed fee once on a larger basket, which is a pricing reason to bundle quite apart from the buyer's convenience.
On a percentage-only platform, the same bundle logic runs the other way: there is no fixed per-sale sting, but a flat percentage of a small price is still small money, and the platform that handles tax as merchant of record is taking a real job off your desk along with its cut. That job comes back the moment you sell from your own site, where a flat monthly delivery cost beats a percentage only after a volume threshold most first listings have not reached yet — do the breakeven on your own numbers, at your own price, before moving anything.
Delivery is part of channel economics too, even when nobody lists it as a fee. A buyer who cannot find the file, whose link expires before the weekend game, or whose A4 print clips the tiebreak strip does not usually ask for help first — they refund or they review. Every support email a clean delivery prevents is margin, because your time is the only cost line that scales with every mistake in the file.
That is also why the honest caveats belong in the listing, not in a reply after purchase. This kind of tool — and FileFreight is the one this guide's author sells from, flat monthly, no per-sale cut — does not handle your taxes or act as your merchant of record, does not import your existing listings from another platform for you, and is not a native app inside a marketplace. A buyer who needs those things should buy the tool that does them. A buyer who mainly needs the right file to reach the right buyer, with the download logged, is the buyer a score-sheet set is built for, and saying so plainly is what keeps the reviews about the sheet instead of about the checkout.
The three delivery failures specific to a game scored once, at the very end
Most digital delivery failures are generic. These three are specific to a product whose entire value is one end-of-game count, and each one maps to a complaint pattern sellers in this niche repeat.
The first is the dismantled city. Everdell's count happens after the game, often while the table is already tidying: cards are gathered, tokens are tipped back, event tiles return to the box. The buyer prints your sheet, reaches the Prosperity line, and finds there is nothing left to check it against, because the sheet gave them one slow total to build while the evidence was being packed away. This is a sheet-design failure before it is a buyer failure: the set needs a count-in-order prompt — categories in the rules' own sequence, city checklist first — that gets a city recorded before anyone's tidying instinct reaches it.
The second is the wrong-version delivery. The buyer purchases the set with the expansion version, receives or opens the base file — because the files were named alike, zipped together carelessly, or attached in the wrong order — and discovers at the table that the sheet has no lines for the systems their game actually used. Version discipline is delivery discipline: one clearly named file per version, the player count on the cover page of each, and a first page that says which game this sheet scores and which it does not.
The third is the dead link on game night. Score sheets are bought close to use — often the day of the game. An expiring link with a short window, a delivery email eaten by a spam filter, or a download limit consumed by the buyer's own failed first attempts all land at the worst possible hour, when there is no support reply fast enough to save the evening. Generous download windows, a recovery path a buyer can use without emailing you, and a delivery log you can check when someone writes in are not luxuries in this niche. They are the product working at the moment it was bought for.
Editions and occasions are different products
The base game and the expansion game are two recording problems, not one sheet with extra columns. Added systems change what needs logging; a sheet stretched to cover everything covers each thing badly. Sell the base set cleanly first. List an expansion set as its own product, with its own worked example, when you have actually recorded a game on it — and keep the solo game out of both, because Rugwort's scoring is a different formula, not a variant of this one.
Occasions split the catalogue the same way. A weekly league wants many sheets cheaply, room for four cities a night, and season standings space. A one-off game night wants one beautiful sheet and the tiebreak strip impossible to miss. A gift buyer wants the set to look like an object, not a spreadsheet. These buyers search differently, review differently and refund for different reasons, and a listing trying to speak to all three usually converts none of them well. Pick the occasion your file actually serves and write the listing to that table, that night, that argument about an event count nobody wrote down.
Print format is an edition too. A fillable version a buyer can complete on a tablet at the table is a genuinely different product from a print-only pad — different checks, different failure modes, different buyer. If you offer both, deliver both as clearly separate files. If you offer one, say which, in the first screen of the listing, before the price does its persuading.
The setup that prevents all three (and when to stay put)
The setup that prevents the dismantled city, the wrong version and the dead link is boring, which is why it works. Build each version as its own file with the paper size in the filename. Test-print every file at full size and record a worked game on paper — use the 61, 61, 58 game above if you like; a sheet that cannot hold it cannot hold a real one. Attach exactly the files the listing promises, in the order the listing names them. Set download limits and expiry generously enough that a buyer preparing on Friday for a Saturday game is never locked out of their own purchase, and keep a delivery record you can actually look up when a buyer writes in, so "I never got it" is a lookup, not an investigation.
Stay put, though, if your current channel is not actually failing you. If your sheets are selling, delivering cleanly and reviewing well where they are, moving them for a theoretical saving costs you search position and a working setup, and no fee table repays that. Move when the numbers at your volume say the cut is the problem, when delivery failures are reaching your inbox, or when a buyer segment you want — the league that buys the big bundle, the expansion table that needs its own lines — is one your current setup cannot serve properly.
Everdell will keep ending the same way it always ends: not with an argument about the total, but with two totals level, the event tiles already back in the box, and someone asking — too late — whether four small events beat three bigger ones. The seller who wins this niche is not the one with the prettiest woodland illustration. It is the one whose sheet recorded the game the way the rules count it — five categories in five lines, every event named and counted, and events achieved and leftover resources captured in order before the city comes apart. Build that sheet, print it, record Ben's four-to-three tiebreak win on it by hand, and only then list it.
Top comments (0)