Verified product workflow
From resident check-in to staff follow-up
- The resident checks in in the mobile app. The check-in records the meeting name, date, and time and evaluates the resident’s location against the meeting location for geolocation verification.
- The attendance view updates through normal API refreshes. Staff can review the result without entering a separate staff-side manual check-in.
- The house view shows the weekly picture. Operators can compare meeting counts and on-target status across residents.
- The resident view adds context. Staff can review meeting history, a calendar heatmap, weekly trends, streaks, geo-diversity, and verification status.
Important: geolocation verification describes whether a check-in passed the product’s location check. It is one operational signal, not proof of participation for the full meeting and not a clinical or legal determination.
Accountability settings
Set a house default, then adjust by resident
Weekly targets
Set a default weekly meeting target on the house profile and add an individual override when a resident’s plan differs. Residents without a configured target can still appear in attendance lists but are excluded from compliance calculations.
Operational attention
Use the house attendance list, check-in recency, on-target status, and trend views to identify records that may need staff follow-up. The product surfaces the information; staff decide what the context requires.
Reporting
Export the same attendance evidence your team reviews
Attendance analytics can be exported to CSV or PDF. Exports can include window-level summary metrics, residents below target, geolocation-verified and unverified check-in totals, and individual check-in rows. Narrower date ranges may be needed when an export reports that check-in rows were truncated.
MyMeetings does not describe these exports as Excel files, court certifications, or automatic proof of program compliance.
Explore operator workflows
Attendance is the foundation, not the whole record