Relationship
Two products, one operational world
DWERK records and proves. VORQON interprets and guides. If you mix that up, you will expect the wrong thing from the right tool.
Side by side
Same field: sites, shifts, proof, and clients. Different responsibilities.
DWERK
- Append-only style truth for your organisation: attendance, tasks, exceptions, exports.
- Authority operations: tenant console, roles, policies, verified work records.
- What you need when someone asks “prove it” — hashes, timestamps, audit posture.
VORQON
- Structured guidance from a described situation: what to check, what to say, what to log.
- Language and framing for supervisors, FM, and field roles — not a replacement ledger.
- Public workspace to try the surface; limits apply. Tenant depth lives with your stack.
How they work together
Not every click needs both. When proof or billing defense matters, the record system carries the weight.
01
Situation
Someone describes what is happening on site — in text, voice, or with an attachment.
02
VORQON
Structures guidance: safety ordering, likely next steps, what to document, when to escalate.
03
Action
People act in the real world — calls, coverage, client comms, vendor follow-up.
04
DWERK
When your organisation uses DWERK, the durable record, export, or exception lives there — not in chat.
When each one matters
VORQON alone
- You need a clear next step from a messy description.
- You are on the public workspace: try a question, no tenant record required.
- You want language for a handover, checklist shape, or client-ready phrasing.
DWERK in the loop
- You must defend hours, deductions, or incidents with evidence.
- Policy and roles must enforce who can change what.
- You need exports your auditor or client can trace to a verifiable record.