Keep the rehearsal reference
One deck changed after rehearsal. What changed with it?
Save the checked schedule, record a named snapshot, then compare the updated talk against that reference. The history tracks manifests and file fingerprints; it does not keep the original presentation files.
1. Save the checked event
Enter a complete schedule, select any presentation originals and resolve room overlaps. Open Saved events and revision snapshots, then choose Save checked schedule. The first save creates an event. Later saves update that loaded event’s current schedule.
Every included talk needs a title, room, real date, start and duration. A checked schedule can cover part of an event, but it cannot contain incomplete talks. Renaming a saved event requires Save as new event so unrelated names do not share a revision history.
2. Capture the rehearsal snapshot
Enter a label such as “After rehearsal” and choose Capture revision snapshot. This saves the current checked schedule and stores an independent copy. Later saves cannot edit that snapshot. Its recording time is when this browser recorded it, not speaker approval, file creation or room receipt.
3. Replace the changed presentation
Keep the talk ID stable. Select the replacement file, wait for its fingerprint, and update any related title, room or timing. Choose the rehearsal snapshot and Compare with snapshot. The comparison names added/removed talk IDs and changed fields such as filename, SHA-256, room or start.
If the file content changes while its filename stays the same, the SHA-256 field changes. A matching hash identifies matching bytes; it does not prove the deck renders correctly, includes linked media or was approved.
4. Save and build the next handoff
Save checked schedule when ready. Record another snapshot if that revision needs its own reference. Reselect original files after refreshing or loading a saved event, then build the rehearsal ZIP. Packaging checks the actual bytes against their recorded fingerprints.
Reloading and switching events
Refresh loads the last saved active event. Loading another event asks before replacing unsaved edits and selected files. It clears the comparison baseline. File names and hashes remain, but the app explicitly asks you to reselect the originals before packaging.
Limits, backups and stale tabs
The local library holds up to five events with five snapshots each, within 2 MB serialized data. Download saved library preserves the checked schedules and snapshots, not original files. Restore validates the complete library before asking to replace saved work. Keep separate ZIPs for original files.
Writes use an atomic saved-version check. If another tab saved first, the current save is rejected and the in-memory schedule remains available to export. Reload only after keeping the work you need. Explicit deletion can remove a snapshot or event; download the library first if you need its history.
Browser storage can be cleared or evicted. This is local history, without shared accounts, cloud backup, approval tracking or automated room delivery.
Open the schedule toolkit ↗