English
+ Forms and checklists

A form is only useful once a path begins behind it.

Digital forms built in minutes, for internal and external use. Every submission then takes a defined path, with assignment, follow-up and an overview of every open case.

01 · The problem

The form is quick to build. What follows is not.

A hailstorm, a reorganisation, a new regulation, and suddenly a form is needed. The PDF takes an hour. Then 60 submissions come back by email, someone starts a spreadsheet, someone else chases, one case gets worked twice and two are left because the responsible person was on holiday. After four weeks nobody knows which case is in which state, and the analysis of how many incidents of which type were reported gets built by hand.

02 · Under the hood

What turns a form into a process.

Capturing the data is not the work. Handling it afterwards is. These five points carry it.

  • A form in minutes, Assemble the fields, publish, done. For employees, partners or customers, as the situation needs.
  • A workflow per form, Every form has a process behind it. Every submission takes the same path, whoever files it.
  • Automatic follow-up, Outstanding steps remind by themselves, with employees, partners or the insurer.
  • Assignment by responsibility, Tasks land with the right person or role, instead of in a shared mailbox.
  • Case overview and analysis, Processing status, bottlenecks and frequencies at a glance, without an Excel export.
03 · What it's worth

60 reports in a week, and the two that would otherwise be left lying.

Work it out with your own numbers. An event that triggers 60 reports costs roughly ten minutes per case in pure administration when handled manually: log it, assign it, chase it, keep the status current. That is ten hours before a single claim has been worked. More expensive than those hours, though, are the two or three cases that are left behind. Whether that means an angry customer, a missed notification deadline with your insurer, or a repeat of the same damage is something you know better than we do, and those cases are exactly why a workflow behind the form pays for itself.

04 · Who it is for

Who forms with a path behind them are built for.

This is meant for Swiss businesses and organisations with roughly five to fifty employees where more reports come in regularly than one person can keep in their head: property and real estate management, construction and trades, fiduciary and insurance offices, technical services, associations and cooperatives. Typically a few dozen reports per event, two to four people handling them, and a deadline set from outside.

It gives the most to those who work the same type of case again and again and look after it with several people. That is where it pays off to have the path defined once instead of agreed anew every time: whoever goes on holiday takes no case with them, and when the next wave arrives the form is already there.

05 · Switching

The move starts with a single form.

Take the one that generates the most traffic in your organisation and put the existing PDF or Word sheet next to it: the fields on it are your field list. Added to that is what is written down nowhere today but sits in a colleague's head: who may file the report, which steps follow, who is responsible for which step, and after how many days without a response a reminder goes out. Then you publish the form, internally for employees or externally for partners and customers.

After that, little follows. You build the second and third form yourself, because the procedure is clear once the first one is done, and you build them when the next case calls for them. The only thing you have to bring along is what is still open: cases on the old route you finish there, and the spreadsheet that has carried the overview so far runs out with the last of those cases.

06 · The platform

Forms and checklists are one module — here is the rest.

07 · Frequently asked

What managing directors and process owners ask first.

Our PDF form works. Why change anything about it?

As long as one person sees every report and handles it themselves, a PDF carries a long way. It gets tight in two moments: when two people work on the same inbox and do not know what the other has already dealt with, and when somebody asks how many cases are open and since when. A defined path answers both, without anyone having to keep a list up to date for it.

Can customers and partners who do not work for us fill in a form?

Yes. A form can be made available internally for employees or externally for partners and customers, depending on who is meant to report. Whoever fills it in does not need to know the platform and sees only the fields they have to complete. What is submitted arrives as a case with an owner and a processing status, not as another e-mail for someone to distribute by hand.

How does a report reach the right person, and what if they are on holiday?

Every step in the path has a responsible person or a responsible role. Through the role, the case reaches whoever is responsible at that moment rather than a name that was stored in the form. If somebody is away, you reassign open cases from the case overview, singly or in a batch, and the history then shows who held the step and for how long.

What keeps a case from sitting unnoticed for weeks?

Two things work together. If a step stays undone beyond the deadline set for it, the reminder goes out by itself, to the responsible person in the house as well as to a party involved outside it. And the deadline hangs on the form, it is not agreed anew for each case: every report of the same type gets the same patience, including in the week when there is a lot going on.

Where do the submitted reports sit, and what about the revFADP?

Your data is hosted in Switzerland. Before anything is sent to an external AI model, our Sensitive Data Guard masks or blocks personal, contract and financial data, only the released, non-identifying content is forwarded, under no-training agreements. That counts twice over here, because reports often contain personal data about third parties. Requests for access and erasure under the revFADP can be evidenced through the audit chain, with person and timestamp.

Who inside the company sees a submitted report?

A case sits with the person or the role the current step is assigned to, and appears there in the task list. Who beyond that may view and analyse the case overview of a form is something you set when the form is set up, not on the side in day-to-day work. Every assignment, every edit and every status change is in the audit chain, traceable with person and timestamp.

The regulation changes and the form needs a new field. Do we need you for that?

No. Assembling fields and publishing stays with you, and the same goes for the path behind it: steps, responsibilities and the deadlines for following up are yours to change. The practical advice from experience: let the first wave run through before you polish. After it, the reports that came in show you which field nobody fills in and which query comes back every time.

Does this also work for recurring checklists, a monthly inspection for instance?

Yes, a checklist here is a form that asks for the same items again and again. Every completed checklist becomes a case with a date, the person who recorded it and a processing status, and an item that stands out triggers the path behind the form instead of staying in a remarks column. In the analysis you see when the last check was made and which items stand out repeatedly.

Watch a form get built and a case run through it, in 30 minutes.

We build a form live, file a case, let the workflow run, and show you the case overview with the bottleneck in it. No contract, no preparation.