Forms

The office's paperwork, filled in where people already work.

A remote work request, a team survey, a statement - built in the panel without a developer, published as a version, and filled in by your people when they sign in.

The responses to a team survey: each person, the status of their response, the version and when it was last changed.
Screens of the real system on made-up data.

How it goes today

Requests come by e-mail, surveys from five different tools

  • A request for days of remote work is an e-mail thread nobody can find in March.
  • The survey link lives in a chat, and nobody knows who has not answered yet.
  • The form changed in May - which answers were given to the old one?
  • An answer needs correcting, and the spreadsheet does not say who changed it.

Forms keeps the form, its versions and every answer in the system your people already sign in to - with who filled what, and when.

From a blank page to answers

Four steps, no developer

The same path for a one-page survey and a three-page request.

  1. Build

    Pages and questions with their rules: required, length, range, the number of choices.

  2. Publish

    The draft becomes a version people can fill in; Preview shows it first, nothing saved.

  3. Fill in

    Each person under My forms - or Admin or HR for them. A draft is saved page by page.

  4. Read

    The form's Responses tab lists everyone who answered or started to, newest first.

The builder

A form is pages of questions, each with its rules

Built on the form's own page and published when it is ready - the draft can go on changing after that.

  • Ten kinds of question: text, long text, number, date, yes/no, one or many choices, e-mail, phone, country
  • Rules per question: required, length, pattern, range, decimals, dates, the number of choices
  • A document is filled in once per person, a survey as often as needed
  • Every publication is a version of its own; a response stays tied to the one it was given to
  • Questions from your catalogue of system fields, pre-filled from a person's last answer
The form builder: a remote work request with its questions - dates, a reason, equipment choices and a safety statement.
The builder with a published form.

My forms

Every person has their own forms in one place

A member of the organization opens My forms in the panel: what they filled in, what is half way, and what they can start.

  • Add lists the forms published for members that can be started now
  • A one-per-person document opens the response already there instead of a second one
  • Only that person, Admin and HR see their responses
My forms of one member: a remote work request in draft and a submitted offsite survey, with the date of the last change.
My forms: a draft and a submitted survey.

Filling in

Answers checked as they are typed, saved page by page

The same rules hold in the browser and on the server - and the person can close a long form and come back to it.

  • A required answer, a date range or a pattern is checked before the next page
  • Every page left is saved as a draft
  • Submitted means final: a change is a correction by Admin or HR, with a reason
A member filling in a remote work request: dates, the reason and the equipment needed at home.
A draft, continued where it was left.

Responses

Everyone who answered, and what they said

Admin and HR see every response to a form on its own tab - and open each one with its history.

  • Person, status, version and the last change in one list
  • A response opens with its answers and the version it was given to
  • Corrections raise the revision and keep the reason in the history
  • Admin or HR can also fill a form in for a person
  • Admin or HR mails everybody who has not sent it yet - the first notice and any reminder
The Responses tab of the team offsite survey: nine people, seven submitted and two drafts.
The form's responses, newest first.
One submitted survey response: the rating, the place, dietary requirements and ideas.
One response with its answers.

What offices use it for

Paperwork that has no module of its own

A form keeps content and checks it; it decides nothing for you - which is why it fits so much.

Requests

Remote work, a training course, new equipment - the request on record, with its dates and reason.

Surveys

A team survey, an offsite, feedback after onboarding - filled in as often as you publish them.

Statements and consents

Read the safety rules, agreed to the photo policy - one document per person, kept with its version.

Said plainly

What it does not do yet

We would rather you knew before the demo than after it.

  • No conditional questions: every question of a page is shown.
  • No attachments: a question cannot take a file.
  • No export to Excel and no charts of the answers yet.
  • No anonymous surveys or links for people outside the organization.
  • No approval: a request is recorded, nothing in the system approves or refuses it.

Questions

Before you ask

Who builds the forms?

The administrator and HR: they create, publish and archive forms and correct a submitted response. Everybody else fills them in.

Can somebody else see my answers?

Only you, the administrator and HR. Other members of the organization do not see your responses.

What happens to answers when the form changes?

Nothing: a change is published as a new version, and every response stays tied to the version it was given to.

Can I stop a form?

Yes - archive it. Nobody can start it any more, and the responses already given stay as they are.

See it work on real screens

The demo has a company with its forms and its people's answers: build one, publish it and fill it in.