A bundle for desk work: keeping a block of focus intact, dividing people into teams, picking who does what, and getting documents into one file before you attach them.
Presentation order, review pairs, on-call rotation, who takes the notes — the moment a person decides, somebody reads intent into it. Randomising does not make outcomes fairer in any deep sense; it removes human intent from the decision, which is exactly what makes it easy to defend in a room.
Announce the method before you draw, not after. A draw explained afterwards looks like a result being justified; the same draw announced in advance is simply a rule everyone agreed to.
Note that the Korean payroll tools in this collection — take-home pay, severance and statutory annual leave — appear only in the Korean edition, because they implement Korean labour law rather than a general formula.
Genuinely random draws produce streaks. The same person coming up three times running is not a broken generator — it is what randomness looks like at small sample sizes, and it is why «the tool is rigged» is such a common complaint.
For anything that repeats, draw without replacement: keep a record of who has already been picked and exclude them until the cycle resets. A weekly rota that resets every quarter is far easier to run than a fresh coin flip every week.
For one-off splits, the awkward case is a headcount that does not divide evenly. Decide in advance where the remainder goes — largest team first, or by joining date — so the leftover person is not a negotiation.
A ghost-leg ladder does the same job as a shuffled list, but people watch the line being traced. That visible process matters more than the mathematics: an outcome people saw being produced generates far fewer objections than one that simply appeared.
It works best for matching two sets of equal size — names to slots, people to tasks, reviewers to pull requests.
Fix the outcomes before anyone claims a starting line. Letting people choose their entry point after seeing the prizes is where the format loses its credibility.
Expense claims, signed contracts and scanned evidence usually have to arrive as a single file. That means merging PDFs you received separately, or turning a stack of photographed receipts into one document.
All of it finishes inside the browser, with no upload. Payslips, contracts and bank statements are precisely the documents involved here, so keeping them off a conversion site is not a nicety.
Check page order and rotation before you send. Scans and phone photos arrive sideways or out of sequence often enough that it is worth one look.
Write down the rule, run the draw, and share the result in the same place. Most disputes come from a rule that existed only in someone's head.
If a draw has to be repeated because of a genuine mistake, say why before you redo it. A silent re-roll destroys more trust than an unpopular result ever does.
Exclude anyone the outcome cannot apply to — someone on leave, someone who already did it last cycle — before the draw, not after.
Splitting a group fairly and merging a file are the visible tasks. What actually consumes an office day is usually not a long meeting but a run of interrupted twenty-five minutes.
The cost of an interruption is not the interruption. Being asked something while reading code or drafting a document means several minutes afterwards spent rebuilding the state you had in your head, which is why "it will only take a second" rarely does.
Cutting the day into fixed blocks buys two things. One is a defensible reason to say not right now — a block ends at a known time, so you can name it. The other is a countable number: how many blocks the day actually held. Once you start sizing work as a three-block job, what fits in a day stops being a guess.
Match the block length to the work: around fifty minutes for anything with a long warm-up, fifteen for a task you keep avoiding, and a shorter cycle before the long break on a day broken up by meetings.
The random tools produce a selection, not a record. Nothing is stored on a server, so if you need an audit trail, save the result yourself.
Merging files does not redact them. If a document contains information the recipient should not see, remove it before combining.
For anything with legal weight — leave entitlement, notice periods, final pay — the source of truth is your contract and local labour law, not a calculator.