Business V1.0 operating model: No daily roster or fixed crew is required. Supervisor Site + Shift creates the session; helper scans build the actual crew for that day.
TAYSAR SiteTime
Welcome
Loading workspace…
Simple attendance workflow
Today—Attendance status
Pending Approval0Waiting for manager decision
Approved Hours0.00 hCurrent month validated hours
Simple flow: Clock IN → Clock OUT → Manager approval → Timesheet.
--:--
Demo Worker • 10027
Current state Checking…
Device AuthenticatorNot registered
LocationNot captured
GPS Accuracy—
Latest Approval—
Shared V0.3: Clock In/Out is written to Cloudflare D1 through the Worker API. Reporting Manager sees the same record on another device.
Pending Approval0
Approved0
Rejected0
Returned0
Loading team shift status…
Showing all team shifts.
Manager Approval Queue
Approval is available only after a worker completes both Clock IN and Clock OUT.
Worker
Site
Clock IN
Clock OUT
Hours
GPS / Boundary
Status
Action
Helper QR Attendance
Supervisor scans only the helpers actually working with them that day. No fixed crew or daily helper roster is required. QR identifies the helper; the active supervisor session supplies Site and Shift.
Business V1.0.0
Active Supervisor Shift
No active shift. Clock IN yourself first. Site and Shift will then be inherited automatically for all helper scans.
Site—
Shift—
Helpers IN0
Today's Helpers0
Session started:— Helper attendance will automatically use this Site, Shift and Supervisor.
Workflow: Supervisor Clock IN → Scan whoever is working today → Clock helpers OUT → Supervisor Clock OUT.
Scanner
NFC-ready architecture: Helper credentials are stored by type. QR is active now; NFC can be enabled later without changing the attendance database.
Verify helper
—
—
Dynamic daily crew
Confirm the person matches the displayed profile before recording attendance.
Recent Crew Scans
Helper
Action
Time
Site
Shift
GPS
Status
Unified Attendance History
Filter by date, person, type or status instead of scrolling through the complete history.
Worker
Type
Timestamp
Site
GPS
Authentication
Status
Decision
Employee Registry
Register Staff, Workers and Helpers once. Registered employees automatically become available in Timesheet and History filters, even before they have attendance records.
Register Employee
Manager assignment: The employee will be assigned automatically to the logged-in Manager. Temporary password can be changed in a future password-management module.
Registered Employees
User ID
Name
Role
Designation
Status
Action
Configuration
Keep configuration small: maintain Shift Master and report branding. Daily roster preparation is not required for normal Business attendance.
Client Branding
Shift Master
Code
Name
Start
End
Grace
Lunch
Regular
Timesheet
Only approved completed attendance is included in final hours. SiteTime records actual attendance first; late/GPS/boundary conditions become review exceptions rather than preventing attendance.
Select an employee to view and export an individual timesheet.
Present Days0
Late Shifts0
Validated Shifts0
Total Hours0.00
Regular Hours0.00
Approved OT0.00
Pending0
Manager PDF: Select one employee and export a compact one-page monthly timesheet with employee details, attendance summary, approved hours, OT and approved shift details.
Shift rule: 9 elapsed hours including 1-hour lunch = 8 regular hours. OT starts after 9 elapsed hours.
Approved Shift Details
Date
Worker
Site
IN
OUT
Elapsed
Net
Regular
OT
Status
Profile
Name—
User ID—
System Role—
Designation—
Reporting Manager—
Device Authentication—
Keep it simple: role controls access; designation is only the employee's job title.
V0.3 Security Boundary
Shared database: attendance records are now sent to a Cloudflare Worker API and stored in D1.
Authentication: demo login is validated by the Worker and a signed short-lived session token is returned.
Biometric: Face ID/fingerprint/Windows Hello stays inside the operating system. This prototype invokes WebAuthn locally. The V0.3 backend records the client verification result, but does not yet perform production-grade WebAuthn assertion verification. That is the next security hardening step.
Location: Phase 1 captures GPS only at attendance events. No continuous tracking.
Production requirement: restrict API CORS to the production Pages domain, use corporate SSO, verify WebAuthn server-side, add device enrollment/revocation and formal data-retention controls.