Built without a PDF
Drag questions onto a page, add conditional questions, and lay a form out in sections, pages and columns. Or describe the form in plain language and edit the draft.
Answers stay governed
Answers are stored encrypted, sensitive formats are masked when read, and every submission keeps a hash chained audit trail. Publishing a form and reading its responses are separate permissions.
It ends in the work
A concern can open a case in DecisionCase, a licence can land on the register in DecisionLearn, and a form's analytics can go to DecisionSheets. Nobody copies an answer into another tool.
What is actually in it
Four areas, from the first question to the place the answer ends up.
Building the form
The builder is meant for whoever owns the process, not whoever owns the PDF.
- A drag and drop palette, with rows you reorder by dragging
- Sections, pages and one to three columns, so a long form does not read as a wall
- Conditional questions that appear only after an earlier choice or yes or no answer
- A logo and header image, with a company default logo for every form
- Draft questions from a plain-language description: the draft is yours to accept, nothing is saved until you do, and the description is scrubbed of personal data first
- Paste in an existing list of questions, or draft a form from a document
Publishing and answering
Forms are answered by signed-in members of your workspace, so you always know the answer came from inside.
- Publish, stop and reopen a form, and copy its link
- An opening and closing time, a cap on responses, and one answer per person
- Answerers can save a draft and come back later, on forms that are not anonymous
- An anonymous mode that discards the user, label, IP address and browser at the moment of submit
- A thank you message of your own, with a clear reason when a form is stopped, not yet open, closed or full
- The cap is enforced under a lock, so the last place cannot be taken twice
Responses
The answers, as a table somebody can actually work from.
- Responses as a sortable table, read one at a time
- CSV export that neutralises cells starting with a formula character, so it is safe to open in a spreadsheet
- Sensitive answers, such as SSN and EIN formats, masked on read
- An analytics page for each form
- Send a form's analytics to DecisionSheets
- A hash chained event trail on every submission
Where the answer goes
The point of a form is what happens after it is submitted.
- Submissions to a Raise a concern form can open a case in DecisionCase, once per submission and never twice
- A form linked to the licence register turns each submission into an unverified licence or permit for review
- The publisher is notified of a new response, and the notification carries no answers and no submitter identity
- Separate permissions to publish a form and to read its responses
- The Raise a concern form asks for the category and disclosure level a case needs
- Eight starters to begin from, listed below
Start from a starter
Eight starters cover the forms most teams build first. Change any question, add your own, and publish.
- Incident report
- Raise a concern
- Feedback or suggestion
- Equipment request
- Time off request
- Access request
- General enquiry
- Event sign-up
It is not a separate product
A form sits inside the platform, so an answer lands in the module that owns the work instead of in an inbox.
DecisionCase
A Raise a concern submission opens a case with the category and disclosure level it asked for. The routing is set through the API today.
DecisionLearn
Link a form to the licence register and every submission arrives as an unverified licence or permit awaiting review.
DecisionSheets
Send a form's analytics to a sheet, so the counts live where the rest of the analysis does.
Built to be trusted with sensitive answers
Encrypted answers, masked sensitive fields, an anonymous mode that discards who and where, and a notification that never carries the answer itself.