Browser Kitty
日本語
productivity

Check-in Desk

Reuse a roster for check-in, attendance, and entry/exit sessions, then review history and export CSV or JSON on one device.

View on GitHub
Local processing
About your filesFiles and content selected in this tool are processed in your browser and are not uploaded to a Browser Kitty backend.
Operation demo See the basic workflow in a short video.

About this tool

Check-in Desk is a browser tool for keeping an event, class, or group roster on one device and reusing it across repeated attendance sessions. Names can be stored with optional IDs, groups, and notes, so you do not need to rebuild the roster each time reception starts.

Use it for one check-in state per person or for repeated entry, exit, and re-entry events. After a session, review completed results and per-person history, then export roster/history CSV or a complete JSON backup only when needed. Roster and attendance history are stored in browser localStorage and are not sent to an application server.

Good for

  • Reuse the same participant roster for repeated classes, clubs, internal events, or small gatherings
  • Let a receptionist search by name or ID and quickly mark arriving people as checked in
  • Record repeated entry, exit, and re-entry events on one device instead of only a single attendance state
  • Review completed attendance later and export CSV for analysis or JSON for backup and device transfer

What it can do

Key capabilities available in this tool.

How to use

  1. Add people under Roster or import a CSV, reviewing possible duplicates and skipped rows before changing the roster.
  2. Start a new session from Check-in and choose all members or a target group.
  3. Choose Check-in for one attendance state or Entry / Exit for repeated entry and exit events.
  4. Search by name, ID, or group and record arriving people. Reception view hides management navigation, and Enter records the action when one actionable result remains.
  5. Add a walk-in when someone is not on the roster, optionally adding that person to the reusable roster too.
  6. End the session and review results, per-person history, and the attendance matrix. Reopen a completed session when needed.
  7. Export roster or history CSV for analysis/sharing, and save a JSON backup before moving devices or clearing browser data.

Supported

  • Roster: name, optional ID, group, and note. CSV recognizes name/id/group/note and common Japanese headers, with up to 5,000 people per import.
  • Session modes: Check-in and Entry / Exit, with Pending / Checked in / All, group filtering, name / ID / group search, Reception view, and walk-in handling.
  • History: completed-session details, per-person history, renaming, reopening, attendance matrix, and session deletion with Undo.
  • Exports: roster CSV, all-history CSV, per-session CSV, and complete JSON backup / restore. CSV and JSON can contain names and attendance information.
  • Device storage: roster and attendance history are stored in browser localStorage. Because browser data can be cleared, save JSON backups for data that must be retained.
  • Browsers: current Chrome and Edge are the primary release targets. The normal standalone HTML is designed to open directly with file:// and has no third-party runtime dependency.

Limitations and notes

  • There is no automatic multi-device synchronization or simultaneous shared editing; the design assumes one device acting as the reception desk.
  • Data changed on another device is not automatically merged with restored JSON data.
  • The app is not an identity-verification system, security access gate, tamper-resistant audit system, or legal attendance register.
  • Browser localStorage is not a durable backup and can be cleared by site-data deletion, private browsing, browser policy, or device cleanup.
  • QR-code, camera, facial-recognition, invitation, payment, ticketing, and cloud event-management features are intentionally not included.
  • Exported CSV / JSON files are not encrypted by the app. Manage files containing names or attendance information according to the rules of your environment.

Frequently asked questions

Are roster or attendance records sent to a server?

No. Roster management, attendance records, history, CSV import/export, and JSON backup/restore run in the browser. The hosted version only requires the initial HTML download.

Can I reuse the same roster for later sessions?

Yes. The roster is stored in browser localStorage and can be reused while that browser storage remains. Save a JSON backup before moving devices or clearing browser data.

Can it record repeated entry and exit?

Yes. Entry / Exit mode records entry, exit, and re-entry events over time. Use Check-in mode when one attendance state per person is enough.

Can I check in a walk-in who is not on the roster?

Yes. Add the person for the current session only or add them to the reusable roster at the same time.

Can several reception devices share the same live roster?

No automatic synchronization is provided. The tool is intended primarily for one reception device rather than simultaneous shared editing across several devices.

Offline version and source code

The root-level check-in-desk.html is a self-contained HTML file that provides roster management, check-in/entry-exit recording, history, CSV import/export, and JSON backup/restore without runtime network access. Roster and history data are kept in device localStorage, so save JSON backups for data you need to retain.

View source on GitHub

Use together

Useful next steps and companion tools, organized around the workflow.

Use local face matching for temporary reception Pop-up Face Check-in Use it for a temporary event when local face matching plus manual reception is more useful than a reusable roster. Print a large reception sign Max Text Print Use it to print a large A4 sign for reception location, instructions, or notices. Show reception guidance on screen Signal Screen Use it when you want to show a large reception number or instruction on another screen instead of printing it.