Skip to main content
KalinkloOS

Reports Center

Every number leaves the building with you.

The Reports Center exports 24 tenant-scoped reports as CSV — roster, schedule, personnel, acknowledgements, attendance, library, payroll service counts, the engagement ledger, and more — plus printable PDF report packs. Your data is yours: no lock-in, no “request an export ticket.”

The report shelf — all 24, as shipped.

Rendered from the product’s own registry

This list is generated from the same code the workspace Reports Center runs, so it can never advertise a report that doesn’t exist.

Production archive

One closeout row per production — services, cancellations, personnel, documents, acknowledgements, readiness, attendance, and linked engagement states.

Roster

Every member — name, email, role, section, instrument, status, last seen.

Service schedule

All rehearsals, performances, and calls across every production.

Personnel assignments

Who is called to which service — section, chair, status, response time.

Acknowledgements

Read/confirm receipts for announcements, services, and documents.

Attendance

Per-service attendance marks — present, late, absent, excused, notes, and recorded time.

Document access log

Who viewed or downloaded each library document, and when.

Engagement ledger

Guest engagements — artist, agency, stage, fee, contract and invoice status.

Payroll / CBA service counts

Per-musician weekly service load with guideline flags and attendance reconciliation for payroll / CBA review. Export aid only; not a payroll engine.

Payroll-ready summary

One row per musician for your CBA / payroll review — total + overtime services beyond the weekly cap, peak week, and attendance. An export for your payroll process; Kalinklo does not run payroll or payments.

Repertoire & performance history

Every work in the library — composer, duration, instrumentation, how many times programmed, and when first/last performed.

Performance history

Every work programmed across past, present, and future — work, composer, production, date, conductor, soloist, season, and status.

Program & running order

Each production's works in program order — the concert program / rehearsal running order, with the order number, composer, soloist, and conductor.

Instrument inventory

Every org-owned, loaned, and rented instrument — make, serial, asset tag, insured value, condition, storage, insurance status, and which tour case it is packed in. A touring and insurance manifest.

Tours

Every tour — code, status, dates, and counts of stops, travel groups, and documents.

Tour stops

Itinerary across all tours — city, venue, arrival/departure, performance date, and hotel.

Travel groups

Travel + hotel groups across all tours, with member counts.

Travel group members

Who is in each travel group, by tour and group.

Tour documents

Tour document metadata (itinerary, hotel, visa, carnet, insurance) — references and expiry, no sensitive data.

Tour cases

Transport cases — capacity, location, assigned tour, packed instrument count, and return status.

Resources

Bookable resources — rooms, spaces, equipment, vehicles — with type, location, and capacity.

Resource bookings

Every resource booking — resource, title, start/end, and status. A room-usage manifest.

Address book

Your organization's full contact directory — venues, conductors, soloists, agencies, presenters, suppliers, ensembles.

Member requests

Member self-service requests — leave, time off, change of address, conductor evaluations — with status and review note.

Sample export · Illustrative

What a personnel export reads like.

Placeholder rows only — real exports carry your roster, and only yours. Names below are redacted stand-ins, not customers.

MemberSectionStatusService
Musician 01 — redactedViolin ICONFIRMED2026-09-14 10:00
Musician 02 — redactedViolaCONFIRMED2026-09-14 10:00
Musician 03 — redactedHornPROPOSED2026-09-15 19:30

PDF report packs render the same permission-gated data print-ready for boards, committees, and payroll.

Proof, not promises.

Tenant-scoped by construction

Every report row is keyed to your organization. A codebase-wide export-scope invariant test fails the build if any export route ships without tenant scoping.

Permission-gated

Each report requires the matching staff permission — a member or an outsider requesting a report URL gets a 404, not a file.

Injection-safe files

CSV cells are escaped against spreadsheet formula injection before anything downloads.

Honest about limits

Large exports state their row caps and flag truncation in the file itself instead of silently dropping rows.

The whole workspace, too

Owners can export the entire workspace as one JSON file — step-up verified, rate-limited, and written to the audit log — from Settings → Workspace export.

Security model

The full access-control, retention, and disclosure posture — stated honestly, including what is not yet certified — lives on the security page.