Factual answers about what DWERK is, how it works, and who it serves.
DWERK is operational infrastructure for making physical work verifiable. It captures proof of attendance, task completion, and workforce deployment — and stores it as an immutable, audit-ready record.
No. Attendance is one output. DWERK captures GPS location, photo evidence, timestamps, and task records — then stores them in an append-only operational ledger. The goal is proof, not just presence.
Staff check in via the mobile app. Each check-in captures GPS coordinates, a selfie photo, and a device-bound timestamp. Photos are hashed at capture. The record cannot be altered after the fact.
DWERK surfaces an exception automatically when a check-in is missed or falls outside the configured grace period. The exception is classified, tracked, and closed with an audit record.
Yes. A single client can configure multiple sites — each with its own staff, shift windows, and geo settings. All sites are visible in the console.
Supervisors see live attendance at their assigned sites. They can conduct roll call for workers without smartphones, classify exceptions, and view the evidence feed.
Excel and WhatsApp produce claims, not evidence. DWERK captures proof at the moment of work — GPS, photo, timestamp — and stores it in an immutable record that cannot be edited retrospectively.
Yes. Service partners are configured by the facility admin. Their workforce operates under the client's plan. Vendor managers can see their team's attendance and generate reports to support invoice reconciliation.
Finance roles see verified attendance records by period, vendor deployment summaries, and exception reports — all generated from source event records, not from aggregate counters.
The mobile app captures evidence offline and syncs when connectivity is restored. Proof is written to the record when the sync completes.
The Facility Admin role controls all configuration — sites, staff, service partners, shifts, task templates, and access. No configuration change is made without a record.
No. Tenant isolation is enforced at the database level. One client's data is not visible to any other client.