Judge's App
DC Sketchfest 2027 · submission review
Lost your code? Email it to me
Your code came from the festival organisers. It's personal — your scores are recorded under your name. Need help? Email admin@dcsketchfest.com.
How judging works
Your slate
Nothing assigned to you yet. Check back once the festival loads submissions.
Your ballots
Committee standings
Borda count. Rank 1 scores the full list length; the last rank scores 1.
Festival admin
Scores exclude judges who declared a conflict.
Values that appear in many places at once. Changing one here changes every page that says it, including the generators that rebuild the lineup and photo pages — the part that is easiest to miss by hand. Nothing is written until you review the list.
Committee Borda tallies
Add people
One per line: Name <email@example.com> or Name, email. Codes are generated automatically.
Demo account
A sign-in for a producer or anyone you want to show the app to. It sees what a
judge sees, every team, but nothing it does is saved, emailed or counted, and it’s never
put on a panel. Its code is DEMO; since that’s easy to guess,
press Remove on “Demo judge” when you’re done (this button turns it back on).
Import from a spreadsheet (.csv)
Columns: first name, last name, email, gender, race, team.
Everyday wording is fine (“Male”, “Latina”, “Black; White”).
Separate several teams with ;. Someone already on the roster
(same email) is updated, not duplicated, and a blank cell never erases what’s there.
Download a template
Judges who asked to be taken off a team. Their scores for it stopped counting the moment they asked; what is left is refilling the panel. Every option keeps the judge recused.
History
Recommended panels
Live slates: edit one judge
Changes here go straight to the judge, no publishing step. Use it for fixes after publishing, like a late team or a swap. Before slates are published, a judge with no teams ticked sees every team. After, they see none.
Who works with whom
Most frequent pairs
Repeated panels
Sent
Import teams
Paste CSV with a header row. Recognised columns include
team, city, region,
local, solo, video,
duration, description.
Teams that applied through the public form. Submitted applications are already on the Teams list; drafts are people who started and haven't finished.
Donation alerts
The donation settings above are what arm Givebutter → Slack, and Slack will not tell you when they are wrong. A bot that was never invited, and a channel name pasted where an ID belongs, both come back as success. These checks are how you find that out before a real donation does. None of them shows a donor’s name, amount or message: the ledger holds a transaction id and Slack’s own error string, and nothing else.
Backfill past donations
Posts donations that happened before the webhook existed. It walks Givebutter oldest first, skips anything already in the ledger, and claims each transaction as it posts — so anything posted here can never post again. Dry run first: a real run cannot be undone except by clearing claims one at a time, and it needs both a Givebutter API key and a campaign code.