Visual schema
Build report templates from sections and fields without writing code.
Platform · Form Builder
Report templates you control.
Design the schema behind field reports and forms — sections, fields, and role-based visibility — with versioning so changes never break in-flight work. Update the form without touching code.
No-codeschema editing
Versionedtemplates, safe changes
Role-awarefield visibility
Drag to rotate
Illustrative interface — a versioned report schema with role-based field visibility.
What makes it different
Forms that adapt.
Versioning
Every change creates a version, so in-flight reports keep the schema they started with.
Role visibility
Show or hide fields and sections by role, so each person sees only what's relevant.
Bilingual labels
Define titles and labels per language for fields and sections.
Drives field reports
The schema powers the mobile field report experience directly.
Safe rollouts
Publish new versions confidently — past submissions stay intact and comparable.
Static PDF forms vs Prime RP
| Capability | Static / PDF forms | Prime RP |
|---|---|---|
| Edit without code | Designer needed | Yes |
| Versioned, non-breaking | No | Yes |
| Role-based field visibility | No | Yes |
| Feeds the mobile app | No | Yes |
| Bilingual labels | Manual | Yes |
FAQ
Questions, answered
Nothing — each submission references the template version it was created with, so historical reports stay intact and the new version applies going forward.
Yes. Sections and fields carry role visibility, so each user sees only what applies to them.
No — the schema is edited visually, so operations can adjust templates without code.
Change the form, not the code.
See a new template version roll out without breaking history.