Feature
Set the steps, get the same data back every time
You decide what each step asks for and who can run it. Whoever runs it collects the same things, and what comes back is already certified.
Components
What a step can ask for
Each step asks for one thing: a value, a photo taken on the spot, a signature, a document to accept. The seal is applied while the person is collecting, so nothing needs certifying afterwards.
Fields to fill in
Text, dates, amounts, a list to pick from. Mark a field mandatory and the step does not close without it.
Captures and files
A photo, a video, a recording, a document scanned on the spot, a web page as it appeared. Files that already exist go in too: a PDF, a contract, an export from another system.
Identity and signature
Choose how much certainty you need about who is on the other side: a code by SMS, a signature, a contract to read and accept, several people signing the same file.
Rules around the steps
Where the capture has to happen, what cannot be skipped, which fields arrive already filled in, how the report is named and laid out.
What changes
The procedure stops depending on memory
Today the same job runs on memory: a checklist in a drawer, a colleague who knows what to photograph, an email that arrives with half the attachments missing.
The same steps for everyone
The order of the steps is the procedure. Someone on their first day collects what a colleague with ten years collects.
No second trip
A mandatory step cannot be skipped, so nobody goes back on site for the photo that was never taken.
One session instead of days
Data, files, identity and signature are collected in one pass, on site, instead of moving between mailboxes.
Consent recorded where it happens
Acceptance and signature sit in the step that requires them, and the record shows they happened before the process could go on.
In the field
Send the process to whoever has to run it
From the portal you choose who collects: a colleague, or a customer, a supplier, an outside technician. They get a link, follow the steps on their own phone, and everything comes back sealed in your archive.
Access and execution
A colleague
already in the workspace
Someone outside
no account to create
