How the Seating Chart Maker Works

The planner manages explicit people, places and rules. These are the calculations, checks and limits behind its outputs.

One person, one valid place

Each person refers to one valid table/desk and seat. Validation rejects duplicate IDs, double bookings, missing tables and invalid seat numbers.

Limits: 500 event guests, 100 tables, 1–100 seats each; or 100 students/desks with 1–20 rows/columns. These are software bounds, not physical recommendations.

How event auto-seating handles parties

A table with five free seats can take this party of four. Existing guests stay seated.

Unassigned guests are grouped by Party after trimming and case normalization. Unlabelled guests are independent; larger groups go first.

The method prefers a table already holding that party, then a tighter fit. Existing seats stay. A group that cannot fit remains unassigned. This greedy method neither guarantees an optimum nor repairs split parties.

How classroom generation handles constraints

A and B satisfy a keep-apart rule. Crossed desks would conflict with A; this is a grid rule, not a physical distance.

Pairs exclude neighboring grid cells, including diagonals. Generation tries 64 shuffles, then up to 20,000 search candidates.

A result satisfies the rules. Failure preserves the chart and does not prove impossibility. Constrained outcomes are not guaranteed uniformly random. See the classroom planning guide.

What the diagram and printouts represent

The schematic canvas does not evaluate venue clearances or safety. Compact tables show at most 12 shortened labels. Full-name posters list all assigned guests; classroom prints add a desk key.

Paper: A4, Letter, A3, A2 or 18 × 24 inches. Browser and printer settings control final output.

Storage, backups and private notes

PDF is a finished display without private notes. JSON restores the full plan, including notes.

Event/classroom drafts are stored separately in this browser without server backup or added encryption. Storage failures are reported; an in-memory plan is not a durable backup.

Output	What it preserves	Includes private notes?
Printed document / PDF	The chosen readable chart or list	No
Guest CSV	People, party, notes, table and seat references	Yes
Complete JSON backup	The editable plan, table positions and classroom rules	Yes

CSV includes stable Table IDs and spreadsheet-safe escaping. Imports validate assignments and structure, accept up to 2 MB, and do not deduplicate appended names.

Checks behind this version

Tests cover assignments, parties, constraints and invalid backups. Chrome QA exercised keyboard editing, CSV round trips, storage failure, full-name printing, note exclusion, A3 output and mobile overflow. This is implementation testing, not browser/printer certification.

Keep a backup; see the revision guide.

Sources and further reading

MDN: how browser localStorage works

MDN: CSS and browser printing

Last reviewed 2026-10-25.

Questions about this seating plan

Does the tool find the best possible seating arrangement?

No global optimum is promised. Event seating uses a greedy party-aware method; classroom generation combines shuffled candidates with bounded search under the entered pair rules.

Does local storage mean the plan is encrypted?

No. Browser-local storage is not presented as an encrypted vault. Anyone with access to the browser profile may be able to open the plan. Use only appropriate information and protect exported files.

Is a CSV enough to restore the whole chart?

No. CSV does not preserve the complete room layout and classroom rule set. Use the full JSON backup to restore the editable plan.