One-time downloads · $0.99 USD. No subscription.

Perunlight

Step-by-step guide

FrithRounds

Turn ranked workshop choices into a reviewed round-by-round plan. Keep participant itineraries, facilitator rosters and cancellation changes together in one approved revision.

You have ranked participant choices and a small workshop timetable, and need a reviewed allocation plus coordinated print packets.

Get FrithRounds · $0.99

See it in use

Revise a two-round workshop seating plan

A screenshot walkthrough with fictional practice data. Select a step to explore.

1. Start with

Revise a two-round workshop seating plan

Six people rotate through Repair, Printmaking and Seed saving.

Sample files and contents

Six people; Repair, Printmaking and Seed saving; two rounds with two seats per session. Explicit round-1 pins keep the demonstration consistent.

Practice files and guides are free. The complete app is included only where the product page says so.

2. In the app

The six-person FrithRounds example with twelve places across two rounds and rank sum eighteen.
Actual Chrome on Linux. Review choices, capacity and pins before approving a revision. Enlarge image ↗

Try it in three steps

  1. Generate and approve the first seating revision.
  2. Deactivate P02 and inspect the surviving places and cancellation checklist.
  3. Approve and print revision two.
Show every click and setting
  1. Generate and approve revision 1, then download its project and packet.
  2. Deactivate P02. The ten surviving draft places remain in place; review them against the previous approved snapshot.
  3. Inspect the cancellation checklist before approving and printing revision 2.

3. The result

Inspect the result

The second revision PDF records the changed seats after cancellation. Review the checklist before using it for a real event.

Page 1 of the actual 12-page fictional example PDF. Open the PDF to inspect the complete result.
Page 1 of the actual 12-page fictional example PDF. Open the PDF to inspect the complete result. Enlarge image ↗
What to check in the practice result

Round 1: Repair Ada/Ben; Printmaking Cora/Dev; Seed saving Elin/Finn. Round 2: Repair Elin/Finn; Printmaking Ada/Ben; Seed saving Cora/Dev. Twelve assignments, rank sum 18. After P02 cancels: ten assignments, rank sum 15, no surviving moves and five participant itineraries.

This fictional example is shown in the working interface and in the supplied result. Review the guide before using your own files.

See the workflow at a glance

Choose a short explanation, then follow the worked example below. Check the requirements and compatibility before using your own files.

Review what a cancellation changes for everyone else.

Ranked choices are only the start of a workshop plan. FrithRounds helps you review capacities and placements, approve a revision and keep itineraries and facilitator rosters together. The fictional making-day example places six people across two rounds; after one cancellation, five itineraries remain with no surviving moves in that example. The proposal search is bounded and does not guarantee fairness, optimality or a complete plan. Review the cancellation checklist and approve the revision before distributing new papers.

View the illustrated card
Review what a cancellation changes for everyone else. — the same explanation written above, with a labelled illustrative panel.
Download the full-size PNG card
An Empty Seat Is Not an Eligible Choice

An empty workshop seat does not mean every participant can take it. FrithRounds uses explicitly mapped ranked choices; unranked topics are ineligible. Before asking it for a proposal, review the roster, topic mappings and session capacities. The free fictional making-day files show the input structure. Search is bounded and may miss a feasible arrangement, so inspect the result yourself. This is an allocation tool for a timetable you already set, not a registration form or fairness guarantee.

55-second silent illustrated overview. Reference images and educational illustrations explain the documented workflow; this is not a new recording of it.

Read the complete video transcript · Download MP4

View the illustrated card
An Empty Seat Is Not an Eligible Choice — the same explanation written above, with a labelled illustrative panel.
Download the full-size PNG card

A cancellation after approval: keep the handoff clear

Use the P02 cancellation example to separate the previous approved plan from the replacement you intend to distribute.

  1. Keep the issued version

    Save the previous downloaded files before replacing them. The app holds the last approved snapshot and the current draft; it is not an archive of every edition.

    Check what the app retains

  2. Review the cancellation draft

    Deactivate P02 and retain the other ten valid draft places. Open Review changed papers to inspect the two cancellation entries against the approved snapshot. Reactivation leaves missing places to fill before approval; other source edits still clear the draft.

    Review the cancellation example

  3. Approve and distribute the replacement

    After review, approve and export the five remaining itineraries in the example. Replace previously distributed copies yourself and identify the replacement clearly; the app does not notify attendees or recall old files.

    Follow approval and export

Before you start

  • Desktop Google Chrome on Linux was tested (Chrome 152.0.7977.82). Extract and keep all buyer files together; opening index.html locally works without network access.
  • For your own event, prepare exact stable participant IDs, ranked topic choices, sessions and whole-number capacities. Every active person must attend every round.
  • No autosave is provided. Download the project and keep earlier approved packets before closing or replacing inputs.

Your first result

  1. Open the example

    Extract the complete buyer ZIP. Open START-HERE.html, follow Open FrithRounds, and choose Try the six-person skills day.

  2. Generate the first plan

    Choose Generate proposal. Expect six participants, two rounds, twelve places, zero missing places and a rank sum of 18. Check each name and room before choosing Approve revision 1.

  3. Keep a durable copy

    Choose Download project. In Review & print, choose Download approved ZIP. The project stores the current draft and last approved snapshot, including when it is bundled in an approved ZIP. Approved print HTML and CSV stay tied to the approved revision; keep older downloads separately.

  4. Print the same revision

    Extract the exported ZIP and open packet.html. Print from Chrome to A4 or Letter, portrait, 100% scale, with browser headers and footers disabled. Preview every page. The original sample has six rosters, six participant itineraries and one checklist.

  5. Try a cancellation

    In People & choices, deactivate Ben (P02). Return to The plan: ten surviving places are already retained, with rank sum 15 and no surviving participant moved. Choose Review changed papers, inspect the two cancelled entries, approve revision 2 and replace superseded papers. No new proposal is required for this cancellation.

  6. Bring your own event

    Save your existing project first. Open the app in a fresh tab and choose Start an empty event. In Sessions & rooms, set the event and round count, read or edit the session CSV, then choose Apply session sheet.

  7. Map the roster explicitly

    In People & choices, import UTF-8 CSV. Match the ID, name, ranked-choice and optional active columns, then choose Review topic mapping and Apply mapped roster. Import replaces draft people and clears draft pins while preserving the last approved snapshot.

  8. Review deliberate changes

    Select a person to move or pin a place. Remove conflicting pins explicitly before source edits. Changes create a draft; an incomplete plan cannot be approved. Room/name changes can require new papers even when session assignments stay the same.

  9. Reopen the saved project

    Open the application again, choose Open project, and select the downloaded JSON. Saved inputs and assignments are rechecked. Without a downloaded copy, closed unsaved work cannot be recovered.

A worked example

A little day of making — original fictional example

Input: Six people; Repair, Printmaking and Seed saving; two rounds with two seats per session. Explicit round-1 pins keep the demonstration consistent.

  1. Generate and approve revision 1, then download its project and packet.
  2. Deactivate P02. The ten surviving draft places remain in place; review them against the previous approved snapshot.
  3. Inspect the cancellation checklist before approving and printing revision 2.

Expected result: Round 1: Repair Ada/Ben; Printmaking Cora/Dev; Seed saving Elin/Finn. Round 2: Repair Elin/Finn; Printmaking Ada/Ben; Seed saving Cora/Dev. Twelve assignments, rank sum 18. After P02 cancels: ten assignments, rank sum 15, no surviving moves and five participant itineraries.

Troubleshooting

Search limit reached or missing places

This does not prove infeasibility. Review capacities, choices and pins, then make deliberate changes or finish with manual moves. Review the complete result before approval.

Too few seats in a round

Add capacity or a session, or deactivate a cancelled participant. In the six-person example, lowering R2B to one seat leaves only five seats and blocks complete approval.

Source change conflicts with a pin

Remove the named pin explicitly in Sessions & rooms, then apply the source edit. Surviving pins are not silently dropped.

CSV import rejected

Use the documented UTF-8 comma-separated profile, exact unique IDs and explicit column/topic mapping. Quote commas and multiline values. Correct blank or malformed records instead of silently dropping them.

Approved packet shows an old room or name

The approved snapshot is intentionally preserved. Generate and review the corrected draft, approve a new revision, and distribute its packet.

Work disappeared after closing

Reopen your last downloaded project. The application has no autosave.

A reactivated participant has missing places

Reactivation keeps surviving assignments but does not invent places for that person. Review their choices and capacities, then move them into valid places or generate and review a new proposal. Approval stays blocked until every active person has a valid place in every round.

Compatibility & limits

  • Up to 80 participant records, including inactive records, 1–3 rounds, 8 topics and 24 sessions. All active participants attend every round. One session per topic per round; integer capacities 1–80.
  • UTF-8 comma-separated roster/session files and version-1 project JSON only. Each input/project is limited to 5 MiB; the exported ZIP is limited to 10 MiB. No XLSX or hosted form integration.
  • IDs use 1–32 ASCII letters, digits, underscores or hyphens and match exactly. Names/labels allow 1–120 Unicode characters. Choices must be unique, contiguous and explicitly mapped; unranked topics are ineligible.
  • The proposal search is bounded to 200000 transitions with a 10-second worker guard. It can miss feasible arrangements and does not guarantee global optimality, fairness or completion for every event. Review each result and use manual moves where needed.
  • No autosave. Keep downloaded projects and earlier revisions yourself. The app retains only the last approved snapshot and current draft; approval is a workflow label, not a digital signature.
  • Chrome on Linux and its A4/Letter PDF output were tested. Other browsers, operating systems, physical printers and mobile devices are unverified. Narrow-screen checks use desktop Chrome at 320 and 390 pixels.
  • Each participant itinerary uses a page; rosters and change lists paginate separately. Printed whitespace is collapsed for readability. Spreadsheet-facing CSV uses a disclosed apostrophe prefix for formula-like text; exact strings remain in JSON.
  • No registration collection, notifications, attendee accounts, payments, waitlists, variable attendance, instructor scheduling or timetable generation.

Need a hand?

Tell us the product, host application and version, what you tried, and the exact error. Contact support with a fictional example; keep private customer files and passwords out of your message.