Draft-first preparation
Create briefings as drafts, select templates, build distribution lists, and prepare content before presentation starts.
Safety module
Site briefings with a controlled start-to-finish flow
SiteGrip helps teams prepare, present, and close briefings with structured templates, verified attendance, and clear distribution notifications so safety communication stays consistent across active projects.
What teams get with briefings
Structured status lifecycle
Run each briefing through draft, prepared, presenting, and completed states with controlled transitions.
Attendance + signature evidence
Capture attendee names, trade, and signatures during presenting mode with progress tracking against persons present.
Live discussion notes
Record time-stamped presenter notes with optional tags during delivery so briefing context is preserved.
Step-by-step flow with arrows
This flow follows the documented briefings lifecycle and makes it easy for teams to understand how a briefing moves from preparation to final evidence outputs.
Planning flow
Template Selection → Distribution List → Content Entry → Mark Prepared
Status flow
Draft → Prepared → Presenting → Completed
Presentation flow
Start Presenting → Add Notes → Capture Signatures → Validate Count → Complete
Completion outputs
Complete Briefing → Queue Distribution Notifications → PDF Status Pending → PDF Ready
Briefing operating model
Delivery combines template-led preparation, present mode controls, and completion outputs in one traceable flow.
Template model
- Briefings use reusable templates with section snapshots preserved per version.
- Default templates cover daily pre-start, weekly coordination, and safety stand-down use cases.
- Prepared state protects briefing setup from uncontrolled last-minute changes.
Present mode controls
- Prepared content is displayed read-only while presenting.
- Discussion notes are presenter-led and time-stamped for traceability.
- Completion is blocked until signature count equals persons present.
Outputs and records
- Completed briefings retain attendee signatures and notes as evidence.
- PDF generation is queued on completion and linked back to the briefing record.
- Briefing number format supports clear project-level retrieval and search.
Notification system explained
When notifications are sent
- Distribution recipients are notified when a briefing is completed.
- Completion notifications can include briefing context and PDF access when available.
- Event-driven delivery supports briefing lifecycle communication without manual follow-up.
In-app notification experience
- Notifications appear in the bell dropdown with unread badge counts.
- The dropdown refreshes every 30 seconds while open to surface new events quickly.
- Users can mark items as read individually or clear all notifications in one action.
Delivery reliability
- Notification payloads carry type, title, body, action link, and metadata context.
- Read state and soft delete keep user inboxes manageable without losing event traceability.
- The same notification APIs are ready for both web and mobile briefing experiences.
Governance and assurance
Permission-gated workflow
Briefing actions are wrapped in authenticated and protected server actions with organisation and project scoping.
Compliance-ready evidence
Attendance, signatures, status changes, and discussion notes remain linked to one briefing record for audit readiness.
Operational consistency
Template-led structure, validation rules, and completion checks help teams deliver briefings with predictable quality.
Keep briefing delivery clear and auditable
Give presenters, supervisors, and project teams a single briefing workflow for preparation, attendance evidence, and outcome communication.