Skip to content
DC Sketchfest 2027

Judge's App

DC Sketchfest 2027 · submission review

Your code came from the festival organisers. It's personal — your scores are recorded under your name. Lost it? Email info@dcsketchfest.com.

Your slate

    Nothing assigned to you yet. Check back once the festival loads submissions.

    Recuse yourself if you know anyone on this team, or have any other conflict of interest. Your scores for this team stop counting as soon as you ask, and the festival is emailed so they can give the team to another judge.

    Your scores

    Do you want this team to perform in DC Sketchfest?

    This vote is half of the team’s score.

    What this one is for
    This score matters the most. Unlike the two above, you can use the team’s tape, their written application, and any experience you have had with them live.
    How a team’s score is worked out
    Saved

    Your ballots

      Saved

      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.

      Export all scores

      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.

      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

      Assign by hand

      Pick a judge, tick the teams they should score, save. Saving replaces that judge’s slate and nobody else’s. A judge with no teams ticked sees every team, which is how the app behaves before any slates exist.

        Saved

        Build every panel automatically

        Panels are built to spread the load evenly, cap how many flagged judges sit together, and avoid the same pair or trio recurring. Running this replaces every existing assignment.

        Who works with whom

        Most frequent pairs

        Repeated panels

        Merge fields: {{first_name}} {{name}} {{link}} {{code}} {{deadline}} {{festival}}

        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.

        Saved

        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.