Make the guest list unambiguous
Two people named Sam need distinct labels in a seating list. Use a surname, initial or another identifier that the event organizer can understand without exposing unnecessary private information. The seating tool requires unique labels so a repeated name cannot silently become two uncertain assignments.
Enter each table with its capacity. A label such as Table 1 | 4 means four seats, not four additional seats after manual assignments. Check the venue’s actual layout and any accessibility or service requirements separately. The tool does not contact guests, send invitations or know relationship preferences.
Choose the assignment mode deliberately
Manual mode uses the table entered beside each guest. Fill blank assignments preserves explicit table entries and then allocates the unassigned rows to available seats. Shuffle all assignments redistributes everyone within capacities. These modes answer different questions, so review the chosen one before generating.
For example, three tables with capacities 4, 4 and 6 provide 14 seats. Twelve guests leave two unused places. If five guests are manually assigned to the first four-seat table, the plan still fails despite spare capacity elsewhere. The specific table capacity matters, not just the grand total.
- Enter the table names and real capacities.
- Use unique, concise guest labels.
- Add any required manual table assignments.
- Select manual, fill blanks or shuffle all.
- Generate and check every table’s list before exporting.
Use reproducible shuffling for a draft
The shuffle set acts as a seed, so the same inputs and set can reproduce a draft. Change it to try another arrangement. This is useful for classroom grouping or a low-stakes event draft, but it is not an audited lottery and does not encode fairness or social preferences.
Review the result with a human organizer. Keep families, interpreters, mobility needs and other relevant constraints in mind without putting sensitive explanations into a public chart. If a particular guest must stay at a certain table, use manual assignments or fill mode instead of expecting the shuffle to infer that rule.
Export the right amount of information
The printable cards paginate long table lists, and the CSV provides a straightforward guest-to-table mapping. Guest and table labels are bounded so they remain visible on the cards. Read the final printout for spelling and compare the guest count with the source list.
Save on this device is optional and uses browser storage. Export a backup if the plan matters, and remove local records on a shared computer when the event is over. Keep organizer notes in a separate private document and print only the information guests need. A seating chart is a snapshot, so label and distribute revisions carefully when assignments change.
References & method notes
The linked references explain the underlying formats, APIs or methods. Worked examples and instructions are original to this guide; a reference is not an endorsement of Nepocore.