Dashboard
Site Spotlight
Highest Risk Sites
Recent Open Items
Open Follow-ups
Recent Visits
Gym Register
Add Gym
Visit
No photos added.
Findings This Visit
Visit Summary
Regional KPIs
Monthly Risk Score Trend
Issue Type Severity Mix
Highest Risk Sites
Issue Type Severity Breakdown
Monthly Risk Snapshots
Trends
Repeat Area and Issue Trend
Area × Issue Type Heatmap
Repeat Area and Issue Patterns
Site Movement
Open Follow-ups
Worsening Sites
Weighted Area Risk Ranking
Reports
Site Scorecard
Manager Conversation Summary
Filtered Findings
Site Profile
Monthly Trend
Site Summary
Top Issue Themes
Top Areas
Open Items
Visit History
Help
User Manual
Use these sections in the same order as a normal field workflow, from site setup through to reporting and review.
Showing all help sections.
Quick Tips
Record findings during the visit, not after.
Use clear notes that another person can understand.
Check reports before export so the filter set matches the output.
Purpose
This app is for recording gym visit findings, tracking open issues, and reviewing site and regional patterns. A normal workflow is, add or review sites, carry out the visit, record findings, end the visit, then review dashboards, trends, and reports.
Before you begin
Confirm the site list is current before starting a visit.
Check the device has enough storage and battery for photos and field use.
Use the same approach each time so data stays consistent across all sites.
Start each day by checking Dashboard for priority sites, open follow-ups, and the most recent visit activity.
What this section covers
Use the Gym Register to add sites, assign a simple priority, and keep the site list usable for field work and reporting.
Core actions
Add the correct site name and region so reports stay readable.
Set priority based on operational attention, not personal preference.
Use notes for stable site context, not temporary visit comments.
Keep site names consistent. Small naming differences break clean trend reading, like creating duplicate enemies in a game roster.
Visit flow
Start the visit from the selected site, record findings as you move through the gym, then end the visit once the live finding list reflects what you found on site.
Visit sequence
Select the site and start the visit.
Add each finding at the point it is seen, rather than trying to rebuild the visit later.
Review the findings list before ending the visit so nothing is missed.
Treat the live findings list like a combo chain in a fighting game. Keep the sequence clean while the visit is active.
What good capture looks like
A good finding record identifies the correct area, the correct issue type, the right severity, and a short note that explains what was found. Photos should support the record, not replace the written note.
Required checks
Choose the area that best matches where the issue sits.
Choose the issue type that best reflects the nature of the issue.
Write a short note that states the condition, gap, or unsafe situation clearly.
Write notes so another person can understand the issue without needing you there to explain it.
Severity model
Low is a minor issue with limited immediate risk. Medium is a stronger control gap or developing risk. High is a significant risk, urgent gap, or issue needing rapid management attention. Flags then show the action status around that finding.
Decision guide
Set severity according to risk and urgency, not how easy the issue is to fix.
Use Resolved on Site only when the issue was fully dealt with during that visit.
Use Follow-up or Revisit when further checking, action, or verification is still needed.
A clean severity choice gives stronger charts and better reports. A poor severity choice is like using the wrong stance in kung fu, the movement still happens, but the result is off.
What users see here
Dashboard gives a working picture of current field status. KPIs give the higher-level regional counts and score patterns. Use these screens to decide where attention is needed first.
Use this screen to
Spot the highest-risk sites and open issues.
Check follow-up pressure and revisit demand.
Review whether findings volume or risk score is rising or falling.
Dashboard is your quick read. KPIs are your score screen. One tells you where to go next, the other shows how the campaign is going.
Why this matters
Trends help move from single findings to recurring themes. This lets you identify repeat issue types, repeat sites, and areas that keep appearing across the dataset.
Pattern checks
Review repeat issues to find recurring control gaps.
Review repeat sites to identify drift or weak follow-through.
Review heatmap and area ranking to see where issues cluster.
Look for patterns, not one-off noise. This is the same as reviewing a training replay and spotting repeated openings, not reacting to one exchange only.
Report outputs
Reports let you filter the dataset by site, date, severity, and flags. The PDF export produces a printable summary with scorecards, conversation points, and the filtered findings list.
Report steps
Set filters to match the review period or site focus.
Run the report and review the output before exporting.
Use the PDF only after checking the result matches the intended filter set.
The report screen is not just export. It is your final edit timeline before the output goes to others.
Site view purpose
Site Profile brings one site into focus. It shows metrics, monthly trend, top issue themes, top areas, open items, and recent visit history.
Use this page to
Review the current status of one site in detail.
Check whether the same issue themes keep returning.
Prepare for follow-up calls, revisit planning, or management discussion.
Use Active Only for normal review. Use Show Archived when you need the wider record and closure history.
Local-first behaviour
This app stores its working data in local browser storage on the device being used. Export creates CSV files from the stored records. Import replaces the current live data with the imported file content for that record type.
Main controls
Export all data at regular points as a working backup.
Import only when you know the file is correct and intended for this app.
Treat one device or browser profile as the live source unless you have a clear manual transfer routine.
Local-first is fast and simple, but the data stays with the device unless you export it. Think of export like saving your project file before closing a video edit.
Data quality standard
Good data is consistent, readable, and current. It lets your dashboard, trends, and reports reflect the real picture without distortion from poor wording or weak status control.
Quality checks
Use the same naming approach for sites, areas, and issue selection.
Write notes that are short, factual, and useful.
Keep follow-up, revisit, resolved, archive, and close-out status current.
Poor input gives poor output. Clean data is like clean structure in app design, the interface on top only works well when the layer underneath is stable.