Skip to content

Live Event Report

The Live Event Report is a standalone HTML tool for running a quick post-show or live-night operations review. It is built for venue, event, or production teams that need a lightweight report without setting up a backend.

Open the live report tool

  • Event basics: date, reporter, event, venue, doors, music start, close, headliner, and support.
  • Live pulse: crowd energy, ops status, ticket count, peak count, peak time, and quick timestamped notes.
  • Production: sound, booth, visuals, lighting, issue notes, fixes, and issue time.
  • Talent and schedule: arrival status, schedule status, green room readiness, changeovers, actual set times, and talent notes.
  • Security and incidents: no-incident confirmation, security coverage, entry flow, crowd safety, incident type, incident time, and resolution notes.
  • Revenue and social: bar sales, food sales, Instagram reach, and strongest social moment.
  • Retrospective: what worked, what did not work, next action, owner, deadline, and overall night rating.
  • Runs as a static file under public/experiments/.
  • Saves report data locally in the browser with localStorage; no report data is sent to a server.
  • Supports manual save, autosave, focus mode, timestamp helpers, time-now helpers, JSON backup export, reset, print, and PDF export through the browser print flow.
  • Version: 1.0.0
  • License: MIT
  • Source: Public source repository not linked yet. The previous GitHub reference was removed after verification showed it was unavailable.
  • Privacy: Report fields stay in this browser’s local storage until the browser or the tool’s reset action clears them.
  • Recovery: Export a JSON backup before clearing browser data or changing devices. If saved data cannot be restored, use Reset to clear the local copy and start a clean report.
  • Limitations: This is an operational notes tool, not a formal incident-reporting system. It has no account, server backup, multi-user sharing, encryption layer, or automatic submission workflow.
  • Last verified: 2026-10-26.
  • Convert the field map into a typed schema.
  • Extract the inline CSS and JavaScript into source-managed modules if the tool grows beyond the standalone prototype stage.

Want something like this built for your team? Discuss a systems/software project.

WORK WITH RICHIE // SYSTEMS INQUIRY

Build something that can actually be used.

Bring a tangled workflow, technical decision, or ambitious idea. Start by making the problem clear enough to shape.