Gerencialab
Dynamic form · no code

Build any form without calling IT

Every lab has that one form the system doesn’t have: the balance check, the cleaning checklist, the inspection of the sample that just arrived, the pH meter log. Today it lives in a notebook or a spreadsheet no one audits. Here you build the form right on the screen, choose the fields, set who approves and publish. In minutes the form becomes a controlled, versioned record, ready for the audit, without opening a ticket for anyone.

You build it, not IT.

Add field by field, name it, mark what’s required and save. No developer, no waiting in the systems team’s queue. The form you need today is ready today.

12 field types for any form.

Text, number, decimal, date, date and time, dropdown, single choice, multiple choice, yes/no, file and photo. You can model anything from a temperature log to a full technical inspection.

The field shows only to whoever needs it.

You tie each field to an analysis group or a parameter classification. The effluent form shows effluent fields; the cosmetic one shows cosmetic fields. One form, many contexts.

Published means locked. Changed means new version.

A published form can’t be edited over the top. To change it, the system creates a new version and keeps the old one whole. It’s the version control ISO/IEC 17025 requires, without relying on manual discipline.

Approval that fires on its own.

You set the rule: a response outside the limit requires sign-off one level up. The form doesn’t close as conforming until the responsible person signs.

Scoring that separates pass from fail.

Each response can score. Below the cutoff the form fails, and the deviation can open a nonconformity without anyone typing a thing.

What you mark as certificate goes to the report.

Field by field, you decide what appears in the PDF. The data captured in the form prints on the test report, with no re-typing elsewhere.

Clone a form and adapt in seconds.

Found a similar form? Clone it, tweak two fields and publish. You don’t start from scratch for every new procedure.

Import and export the whole form.

Take a form’s structure to another site or bring it back. The template travels with its fields, rules and scoring.

Every form with the right permission.

Release the form to the whole system or restrict it to a role. Whoever collects sees what they collect, whoever approves sees what they approve.

Ever notice the form that trips up audits the most is the one living outside the system? The balance check in a notebook, the cleaning log in an ownerless spreadsheet. When it’s born as a versioned form, that gap disappears.
It’s the cycle auditors like to see: the form is born on the screen with fields and rules, gets published and locked as a version, each answer keeps who did it and when, what fails turns into a nonconformity and what matters prints on the report. From a blank field to a signed record, all in one system.

From raw answer to audit record

A form only counts in an audit if the answer has a trail, a version and an owner. That’s what separates a paper form from a controlled record.

Each answer knows which version it came from.

The completed form stays tied to the version used at the time. Changed the template later? The old record stays faithful to what was valid that day.

Who answered and who approved is on record.

Date, name and stage on every answer. When the auditor asks who did it, the answer is in the record, not in someone’s memory.

Preview before publishing.

You see the form the way the respondent will see it, test the rules and only then publish. No discovering the wrong field after the form already ran.

Frequently asked questions

Do I need to know how to code to build a form?

No. You add field by field on the screen, pick the type, mark what’s required and publish. It’s the same work as building a spreadsheet, except the result is already a controlled, auditable record.

Can I edit a form that’s already in use?

A published form is locked on purpose, to preserve the integrity of answers already filled in. When you need to change it, the system creates a new version and keeps the previous one intact. Old answers stay tied to the version they were filled in.

Does the same form work for different sample types?

It does. You condition each field to an analysis group or a parameter classification. So a single form adapts to context: it shows the microbiology fields when the sample is microbiological and hides the rest.

Do form answers go into the report?

The fields you mark as certificate print on the report PDF. What the team records in the form becomes part of the final document, with no re-typing in another system.

Want to see the QMS running with your lab’s routine?

Get through the next audit without burning a weekend night hunting for PDFs. Book a demo and see document control, CAPA and Westgard working with a case similar to your lab's.

Build any form without calling IT · Qualidade · Gerencialab