This English prompt is a noindex utility asset embedded by HRaaS.io for users who want to prototype their own attendance app.

You are helping me prototype an employee attendance and workforce management application.

Goal:
Design a practical MVP for a company that needs to track employee attendance, reduce manual timesheets, support manager review, and prepare cleaner records for payroll and compliance workflows.

Important context:
This is not only a clock-in app. Attendance data can affect pay, trust, manager decisions, labor cost visibility, and compliance records. Treat reliability, auditability, permissions, and edge cases as core requirements, not as optional polish.

Product scope to consider:
- Company setup with departments, positions, locations, work schedules, holidays, and basic policy settings.
- Employee records with employment status, assigned manager, department, position, schedule, location, and user account access.
- Clock-in and clock-out flows for mobile and web, with timestamps, timezone handling, location context, device context, and clear failure states.
- Geofencing or location validation that can record whether the employee was inside the expected work area without pretending GPS is always perfect.
- Device trust signals that help detect suspicious usage, repeated device sharing, or unusual login and attendance behavior.
- Attendance records that distinguish raw punch data from reviewed, corrected, approved, finalized, and historical records.
- Exception handling for lateness, absence, missed punch, early leave, out-of-location check-ins, duplicate punches, and manual corrections.
- Manager workflows for reviewing exceptions, approving corrections, rejecting invalid requests, and leaving an audit trail.
- Employee self-service views for checking personal attendance history, seeing pending requests, and submitting correction requests.
- Admin views for reviewing company-wide attendance, filtering by employee/team/date/status, and exporting operational data.
- Reporting for daily summaries, monthly summaries, exception trends, punctuality, consistency, and payroll-readiness.
- Finalization flow so past attendance periods can be locked, preserved, and reopened only with clear history.
- Role-based permissions for employees, managers, HR admins, company owners, and support/admin staff.
- Multi-tenant data separation if the app will serve more than one company.
- Notifications for important events such as missed punches, pending approvals, rejected corrections, and finalized periods.
- Privacy and security expectations for employee location, device, identity, and attendance data.

What I need from you:
1. Propose the core user roles and permissions.
2. Propose the main data models and relationships at a conceptual level.
3. Propose the main user flows for employees, managers, and administrators.
4. Identify the edge cases that will make attendance tracking unreliable if ignored.
5. Identify which features belong in the MVP and which should wait.
6. Explain the audit trail and finalization model in plain language.
7. Explain the risks around payroll, compliance, location data, device trust, and manual corrections.
8. Suggest a simple technical architecture, but keep it practical and maintainable.
9. Produce a phased build plan that starts with the smallest useful version and grows toward a reliable operational system.
10. List the assumptions I must validate with real users before building too much.

Output format:
- Start with a concise product brief.
- Then give roles and permissions.
- Then give data model concepts.
- Then give workflows.
- Then give MVP scope and later scope.
- Then give edge cases and risks.
- Then give architecture.
- Then give a phased implementation plan.
- End with questions I should answer before writing code.

Do not hand-wave operational complexity. If a requirement sounds easy but has hidden risk, call that out clearly.