Trust and Security
DWERK is designed so physical work is not reduced to claims, memory, or backfilled reporting. Every record is structured to hold up — in operations, in billing, and in formal scrutiny.
100%
Tenant isolation
0
Cross-client data sharing
∞
Append-only records
100%
Role-scoped access
Why Trust Breaks
Unverifiable attendance
Staff presence confirmed by registers and calls — not system records.
Unverifiable task claims
Work completion reported verbally or through messages with no proof.
Delayed reporting
Operational data aggregated after the fact — not captured at source.
Message-based ambiguity
WhatsApp and calls create no auditable record of what was said or decided.
Unclear ownership
When something goes wrong — nobody has a record of who was responsible.
Weak evidence
Disputes resolved by memory and seniority — not facts.
The DWERK Trust Model
Append-only records
Events are written once. Never overwritten. The truth layer is permanent.
Evidence capture
Every event carries geo, time, and media proof at the moment of capture.
Role-scoped visibility
Each role sees exactly what their authority permits — nothing more.
Authority control
Approvals, escalations, and assignments are logged and bounded by role.
Continuity trail
Relievers, handovers, and exceptions are tracked — gaps never disappear.
Exportability
Full operational history exportable for billing, audits, and dispute review.
The Evidence Chain
Who
Identified actor — staff, supervisor, or system — with role and assignment.
Where
GPS coordinates captured at the moment of the event.
When
Server-side timestamp — not device clock.
What
Event type, task, shift, or action — structured and categorised.
Proof
Media, selfie, or structured data attached at point of capture.
Action
What was done in response — assignment, escalation, or resolution.
Approval
Who authorised or acknowledged — with timestamp and role.
Record Integrity
Dashboards and reports are projections — derived views of the underlying event stream. The event stream itself is never modified. What was captured is captured permanently.
Events are write-once
No update, edit, or delete operation exists on source event records.
Projections are separate
Dashboard views are derived. The source truth is never the display layer.
Corrections are appended
If something must change, a correction event is added. The original remains.
Tenant isolation
Your operational data is isolated. No cross-client visibility is possible.
Role Boundaries
Staff
Their own check-ins, tasks, and shift history only.
Supervisor
Their assigned sites, staff, and open exceptions.
Facility Manager
All sites and vendors under their account.
Vendor Manager
Their own staff and delivery records only.
Finance / CFO
Verified billing summaries and exception reports.
Platform Admin
Configuration only — no operational records outside scope.
Reporting Defensibility
Attendance summary
Every present, absent, and late — backed by event records.
Verified work records
Proof-backed event logs — exportable for billing and audit.
Exception reports
Every gap, late arrival, missed task — timestamped and traceable.
Billing support
Line-item verified summaries ready for client invoice review.
Dispute exports
Full evidence chain exportable for formal dispute resolution.
Audit history
Complete operational record — downloadable on demand.
What We Don't Claim
Not claimed: SOC 2 / ISO 27001 certified
We are not yet certified. These audits are planned. We will not claim them until they are complete.
Not claimed: Published uptime SLAs
We do not yet publish formal SLA commitments. We operate with high availability as a design goal, not a contractual guarantee.
Not claimed: Penetration tested
Independent pen testing is planned and not yet completed. Our architecture is designed for security — formal testing is in progress.
Frequently Asked
Built For Scrutiny
Self-serve. No sales call. Full access free for three months.
Talk to the team →