Attendance Access & Login

US-01 — Independent Attendance Login as a camp team member (Registration Officer, Nurse, Radiographer, Lab Technician, Counselling Officer, Coordinator, Community Mobilizer, Surveillance Officer, or other authorized role), I want to access an Attendance Module directly from the application's login screen using my Employee ID, So that I can record my attendance without needing full TB Screening application credentials.

Acceptance Criteria:

• Attendance Module is visible/accessible as a separate option on the app login screen.
• Employee ID is the sole credential required to enter the module.
• User registration (creation/issuance of Employee ID) happens centrally at the portal, not within the mobile app.
• Authentication requests travel over a secured pipeline; identity validation is performed using an encrypted key rather than a plain-text credential check.
• Users without TB Screening workflow access can still record attendance.
• Camp Coordinator role is fulfilled by members of the Ops Team.

 Camp Master GPS Configuration

US-02 — Configure Camp Master Location as a Coordinator / Administrator, I want to configure the GPS reference point and details of a village camp as part of pre-camp planning, once the camp site is finalized, so that attendance can later be validated against a fixed camp location.

Acceptance Criteria:

• Camp location finalization is a pre-camp activity carried out by the Ops Team before the camp opens; GPS configuration in the app reflects this finalized site.
• Settings screen captures State, District, Block, Village (dropdowns), Camp Start Date (mandatory), Camp End Date (optional, updatable later), and auto-generates Camp Name, Camp ID, and Camp Duration.
• "Get GPS Coordinates" button captures Latitude, Longitude, GPS Accuracy, and Timestamp.
• Configuration is completed once at the start of each camp via "Submit."
• Attendance cannot be recorded until Camp Master GPS is configured (FR-05).

US-03 — Reset Camp Master Location: as a Coordinator, I want to reset the configured Camp Master GPS location when needed, so that incorrect or outdated camp coordinates can be corrected.

Acceptance Criteria:

• Reset option is restricted to Administrator/Camp Coordinator roles only.
• A confirmation prompt is shown before the reset is applied.
• Reset action is captured in the audit trail.

 Attendance Recording

US-04 — Select Attendance Type as a team member, I want to select whether I am attending "In Camp" or "Outreach" activity, so that the correct validation logic is applied to my attendance.

Acceptance Criteria:

• Attendance screen offers a radio-button choice between "In Camp" and "Outreach."
• Employee ID must be entered alongside the selection.

US-05 — Check-In as a team member, I want to check in with my current GPS location, so that my arrival is recorded accurately and linked to the camp.

Acceptance Criteria:

• On Check-In, system captures Timestamp, Latitude, Longitude, GPS Accuracy, Device ID, and (optionally, if internet is available) Address.
• Check-In button is enabled only after a successful prior Check-Out (or if no prior check-in exists for the day).
• Multiple Check-In/Check-Out cycles are allowed per day, in sequence.

US-06 — Check-Out as a team member, I want to check out with my current GPS location, So that my departure time and location are recorded.

Acceptance Criteria:

• Same data points captured as Check-In (Timestamp, Latitude, Longitude, GPS Accuracy, Device ID, optional Address).
• Check-Out button is enabled only after a successful Check-In.

US-07 — In-Camp Attendance Radius Validation As the system, I want to validate "In Camp" attendance against the Camp Master GPS within a configurable radius (default 1000 m), So that attendance is only accepted from within or near the actual camp location.

Acceptance Criteria:

• If Check-In/Check-Out location is within the allowed radius, attendance is accepted automatically.
• If outside the radius, a pop-up alert is shown: "You are outside the camp attendance area! Do you still want to proceed with Check-In?" with "Yes" and "No" options.
• Selecting "Yes" proceeds with attendance; selecting "No" allows the user to retry Check-In.

US-08 — Outreach Attendance (No Radius Validation) As a camp team member on outreach duty (e.g., conducting household registration in the community), I want my GPS location recorded at Check-In/Check-Out without radius validation, so that outreach attendance outside the camp premises is still captured correctly.

Acceptance Criteria:

• Outreach attendance corresponds to field activity such as household-level registration, where people are registered away from the fixed camp site.
• GPS coordinates are recorded for outreach attendance without comparison to Camp Master location.
• If GPS cannot be captured, the system provides a "Retry" option.

US-09 — Automatic End-of-Day Check-Out: As the system, I want to automatically check out any user who forgets to check out by a configurable end-of-day time (default 5:00 PM), so that no attendance record is left open indefinitely and non-compliance is visible.

Acceptance Criteria:

• Auto Check-Out triggers at the configured time (default 5:00 PM) if no manual Check-Out was recorded.
• The resulting record is flagged with status "System Check-Out."
• A user who receives a System Check-Out is blocked from checking in again the following day until the flag is reviewed/cleared (e.g., by an admin).
• The flag is surfaced to the affected team member (on their next login/attendance attempt) as well as to the Admin/Ops team for follow-up.
• End-of-day time is configurable by an administrator.

US-10 — Attendance Linkage as a program monitor, I want each attendance transaction linked to Camp ID, Camp Name, Camp Dates, Village, and Employee ID, so that attendance data can be traced back to the correct camp and person for reporting.

Acceptance Criteria:

• Every Check-In/Check-Out record stores the associated Camp ID, Camp Name, Camp Dates, Village, and Employee ID.

Offline Support & Sync

US-11 — Offline Attendance Capture as a team member working in an area with poor connectivity, I want to check in/out even when offline, so that my attendance is not blocked by lack of network access.

Acceptance Criteria:

• Device-level GPS capture works fully offline (does not depend on internet connectivity), so location can always be recorded.
• Internet connectivity is required only for the very first login; after that initial login, the app can operate offline.
• The app supports up to 10 consecutive days of offline operation, storing Check-In/Check-Out records (with GPS, timestamp, etc.) locally during that period.
• Once the device regains network access within that window, all locally stored records automatically synchronize with the central server (FR-13).
• If the offline period is expected to exceed 10 days, the user should be prompted to reconnect and sync before continuing.

 Reporting & Non-Functional Needs

US-12 — Attendance Reports as a program administrator/M&E officer, I want to generate attendance reports across camps and team members, so that I can monitor participation and staffing for camp and outreach activities.

Acceptance Criteria:

• Reports can be generated showing Check-In/Check-Out records by camp, date, employee, and attendance type.
• Reports support monitoring and evaluation use cases.

US-13 — Performance, Security & Audit as a system stakeholder, I want the module to meet defined performance, security, and audit standards, so that the system is reliable, secure, and traceable.

Acceptance Criteria:

• Response time < 3 seconds; GPS capture time < 10 seconds; GPS accuracy ≤10 m preferred.
• Data transmitted over HTTPS with encryption; 99.5% availability target.
• All Check-In/Check-Out and administrative actions (e.g., GPS reset) are captured in an audit trail.
• Platform: Android.

 Session, Validation & Error Handling (Gaps Identified in BSA Review)

US-14 — Logout from Attendance Module as a team member, I want a clear way to log out of the Attendance Module, so that my session is closed securely and the device is ready for the next user.

Acceptance Criteria:

• A dedicated Logout button/option is available within the Attendance Module.
• On logout, the user is redirected back to the TB Screening application's login screen.
• Open question: Is logout available while offline, or does it require connectivity?