Work should be provable.
We built Hakiki because a ticked box on paper or in a form says nothing about whether the work was done. Organisations need a record they can stand behind: the answers, the proof, and who gave them.
One record per piece of work.
A department head writes a workflow and publishes it. Each time someone runs it, Hakiki keeps a separate execution tied to that exact version, with every answer and file, who gave it and when. When the work is completed it is locked, and every action stays in a tamper-evident audit trail.
Owner
Runs the account: people, billing, settings and the full audit trail.
Admin
Sets up departments, invites people and assigns their roles.
Department head
Writes and publishes the department’s workflows and reviews the work.
Member
Runs workflows step by step and attaches the proof each step asks for.
What is in the box.
- Versioned workflows: an edit makes a new version and history is kept
- Steps can be required in order, and can depend on earlier answers
- Several people can take part in one execution
- Evidence files served only to signed-in people, never by public link
- Six kinds of step: yes or no, text, one choice, several choices, file upload, table of numbers
- An audit trail where each entry carries the hash of the one before it
- Email notifications at the moments that matter
- Each organisation’s data kept apart by the database itself
Built by 4M Consulting.
See it with your own process.
14 days free, no card needed.