Jonathan Creek Maintenance Analytics

Loading…

Import / Edit Data
Session NameStart DateEnd DateGuests

Importing a CSV replaces the guest-form request pool (it does not affect the separately-tracked Teams staff reports below). Only rows whose date falls within the earliest session start and latest session end above are analyzed.

—
Total maintenance requests
(in current date range)
—
Total guests across current sessions
—
Requests per guest — all sessions
—
Requests per guest — sessions with requests recorded

Requests by Category

Requests by Building

Requests by Appliance / Item (top items)

Requests & Guest Volume by Session

■ Requests   ■ Guests
Session
Requests
Guests
Req / Guest

Click any bar or session row to see the individual maintenance requests behind it. Sessions with 0 requests may simply have no data in range yet.

Requests per Bed (Occupancy-Adjusted)

Loading…

#BuildingBeds% of CapacityRequests% of RequestsIndex

Index = a building's share of requests divided by its share of total beds. 1.00x means it's right in line with its size; above 1.00x means it's generating more requests than its size alone predicts — that's the real outlier signal, not raw counts. Bed counts are estimates and only cover overnight housing (event/amenity spaces aren't sized in beds). Click a row to see that building's requests.

Preventative Maintenance Priorities

Loading…

#BuildingCategoryMost Common IssueRequests% of Building

Ranked by request volume within each building this season. Click a row to see the individual requests behind it — use this list to target inspections and preventative repairs before next summer.

About the data: combines Guest Form submissions and Staff Report (Teams) messages; building, category, and issue type are inferred from free-text where a form field wasn't picked, so treat counts as directionally reliable rather than exact.