Structured task creation
Create safety tasks with title, context, priority, and due date so actions are clear from day one.
Safety module
Assigned tasks with clear ownership and follow-through
SiteGrip gives project teams one workflow for assigning safety tasks, tracking progress, and keeping assignees informed through structured notifications and status visibility.
What teams get with assigned tasks
Internal + subcontractor assignment
Assign tasks to internal team members and external users through one merged, searchable user selector.
Status-led execution
Track task progress through not started, in progress, completed, and on hold states with consistent visibility.
Comment-based collaboration
Keep updates and clarifications on the task record so teams avoid fragmented communication.
Step-by-step flow with arrows
The flow below reflects the documented assigned task lifecycle so users can quickly understand how work moves from creation to completion.
Creation flow
Create Task → Assign Users → Notify Assignees → Start Work
Progress flow
Not Started → In Progress → Completed
Hold branch
In Progress → On Hold → In Progress
Assignment response
Pending → Accepted / Declined → Completed
Task operating model
Delivery combines assignment states, execution statuses, and collaboration in one trackable record.
Assignment model
- Task assignment supports both organisation users and linked subcontractor users.
- Duplicate assignment is prevented for the same task and user pairing.
- Assignment status can be tracked as pending, accepted, declined, or completed.
Daily delivery controls
- Teams can filter by status, assignee, priority, and due date to focus on risk-critical work.
- Bulk updates help managers move multiple tasks through status changes quickly.
- Project and personal task views stay responsive through cache + invalidation strategy.
Task states
- Not Started for newly assigned or queued work.
- In Progress while activity is actively underway.
- On Hold when site conditions pause execution.
- Completed when work is finished and confirmed.
Notification system explained
When notifications fire
- Task assignment notifications trigger when a user is assigned to a task.
- Task update notifications trigger when assigned tasks are changed.
- Update notifications exclude the user who made the change to avoid self-notify noise.
Channels and severity
- In-app delivery is the baseline channel across events.
- Email can be used for action-required updates such as new assignments.
- SMS and push are optional and can be enabled by workflow policy.
Reliability and anti-spam
- Notification payloads follow a standard structure with type, severity, project, and action URL.
- Rate limits prevent email and SMS over-notification on repetitive events.
- If assignment notifications fail, teams should validate user email, rules config, and provider logs.
Governance and assurance
Permission-based actions
Create, update, delete, assign, and view actions are gated by role permissions so task control remains intentional.
Audit-ready traceability
Task lifecycle changes, assignments, and status updates are captured for compliance and operational review.
Operational accountability
Ownership, due dates, priorities, and comments stay attached to one record, helping teams close actions faster.
Keep safety actions visible until complete
Give project managers, team leaders, and assignees one shared flow for ownership, updates, and task close-out without losing context.