Operative view

Why

Operatives are best positioned to provide accurate information about their work hours, breaks, and job activities. Currently, they cannot input this data directly, leading to inaccuracies, delays, and dependence on supervisors or office staff to manually enter timesheet information.

What

A self-service interface for operatives to view, update and submit their own timesheets. The system respects configurable review workflows, routing submissions to either supervisors or office staff based on organisational settings.

How

• Create operative-specific timesheet view showing their scheduled and actual hours
• Build interface for operatives to update their timesheet entries (hours worked, breaks, job details)
• Implement timesheet submission workflow
• Add validation to prevent submission of incomplete timesheets
• Display timesheet status and review workflow
• Route submissions based on settings (supervisor review vs office review)
• Implement mobile-first design for field access
• Add read-only view for approved timesheets

Dependencies

• Operative user authentication
• Timesheet settings configuration (review workflow)
• Timesheet data model
• Notification system for submission confirmations
• COR-1478 (parent feature)

Acceptance Criteria

• [ ] Operatives can view their own timesheets (scheduled and actual)
• [ ] Operatives can update hours worked, breaks, and job details
• [ ] Operatives can submit timesheets when complete
• [ ] Clear validation prevents submission of incomplete data
• [ ] Timesheet status visible to operative (draft, submitted, approved, rejected)
• [ ] Submissions route correctly based on review settings (supervisor or office)
• [ ] Operatives receive confirmation when timesheet is submitted
• [ ] Approved timesheets are read-only
• [ ] Rejected timesheets can be edited and resubmitted
• [ ] Interface is mobile-responsive for use on phones in the field
• [ ] Operatives can only access their own timesheets