From a blank workflow to a locked record.
Four steps, the same every time. Each one leaves a trace, so the finished record shows not just the answers but who gave them and when.
- 1Department head
Write the workflow
Lay out the steps in order and choose what each one asks for: a yes or no, text, a choice, numbers, or a file. Make a step depend on an earlier answer where it should.
Site visitDraft, version 2- 1Is the site safe to enter?Yes or no
- 2Photo of the meter readingFile upload, required
- 3Readings per tankTable of numbers
- 2Department head
Publish it
Publishing makes the version available to the department. A later edit becomes a new draft version, so nothing changes under people already working.
ActiveSite visit
Operations department
Start execution - 3Members
Do the work
People run the workflow on a phone or computer and answer each step. Steps that need proof cannot be completed without it. Every action is timestamped and attributed.
Step 2 of 3
Photo of the meter reading
IMG_2041.jpg
Uploaded 09:42 by Wanjiru K.
- 4Department head
Review and lock
Completed work is reviewed and approved or rejected. Once completed it is locked: both the application and the database refuse changes.
ApprovedSite visit, Kitengela
Approved by the department head
Locked. Further changes are refused and every past action is in the audit trail.
Every action is on the record.
Starting, answering, uploading, approving: each is written to the audit trail with who did it and when. Each entry carries the hash of the one before it, and the chain is checked every night, so a removed or altered entry shows up.
Run your first workflow this week.
Start a free trial and write the steps your team already follows.