# Forms

Build inspections, checklists and daily reports with the platform's form engine: builder, renderer, lookups and signatures.

Inspections, checklists, daily reports, sign-off sheets: half of operations runs on forms. Don't build a form designer from scratch. The platform has one, the same **form engine** that powers **Inspections & Forms**, and your module can use its drag-and-drop builder, its renderer and its checks. Forms look and behave the same in every module, on the web and on the **DV Field** phone app.

## The form builder and renderer

There are two halves:

| Half | What it does | Who uses it |
|---|---|---|
| **Builder** | Drag fields and sections onto a layout, set labels, required, choices, min and max | Form designers in the workspace |
| **Renderer** | Draws the form for filling in, then hands your module the answers | Crews and office staff |

Field types include text, long text, email, phone, number, currency, rating, single and multiple choice, yes / no, pass / fail, date and time, photo, location (GPS), instructions, **lookup**, **table** and **signature**.

Your module can also add **its own sections** to the builder's toolbox, like a parts list drawn your way. The builder offers them next to the standard fields, and the renderer asks your module to draw them.

People can talk instead of type: each section can have a **mic**. They say what was done, the AI fills only that section, and every value is marked *AI filled — review* with an **Undo**.

## Lookups, tables and rules

- **Lookups** pick a record from any module that offers one: an employee, a project, a customer, a piece of equipment. The answer keeps the record's name and id, so reports can follow it back. People only see records they're allowed to see.
- **Tables** are repeating rows, like Labor or Materials lines. A column can show only when another answer calls for it, such as *Which unit* when the item is owned and *Rented from* when it's rented.
- **Rules** are checked the same way everywhere: required fields, numbers in range, choices that exist. Submit names exactly what's missing (*Labor row 2: Hours*), and a value that doesn't fit is refused, never quietly dropped.

Your module can also offer a whole section to every form, such as a Labor section that posts hours to your module when the form is submitted, and takes them back if the form is reopened.

## Signatures

A **signature** field lets the signer draw with a finger, pen or mouse and type their name. It's kept with the time it was signed. A required signature needs both the drawing and the name before the form can be submitted.

## Check on the server, always

The screen helps people fill the form in; the server makes sure it's right. Before your module stores anything, it asks Inspections & Forms to:

1. Tidy the layout before saving a form design.
2. Clean the answers before saving them.
3. List what's still missing before accepting a submit.

Store a **copy** of the layout with each filled-in form, so editing the form later never changes old records.

## Ask the Module Builder

> *"Add a daily vehicle inspection to my fleet module using the platform form builder: a truck lookup, pass/fail checks for brakes, lights and tires, photos, and the driver's signature. Check required fields on the server before saving."*

```json
// For developers: module.json
"service_dependencies": [
  {"module": "INSPECTIONS_FORMS", "service": "clean_answers",
   "usage": "Check inspection answers before saving"},
  {"module": "INSPECTIONS_FORMS", "service": "missing_required",
   "usage": "Refuse a submit with required fields empty"}
]
```

## Good to know

- **The server checks come from Inspections & Forms,** so the workspace needs it installed for them. Declare it as a dependency and the Marketplace brings it along.
- **Photos are yours to store**, in your module's storage, linked to the field. See [Storage: files and photos](article:4c8a50b6-7a7d-4f07-b1fe-b8748ecddd6f).
- **Forms show filled-in answers on your records.** Inspections & Forms can list the forms filled about one of your records, for its page.
- **Fields are named for the assistant automatically**, so it can fill a form on screen. See [Module help and Show me](article:53508199-cd90-4a4c-a453-f6e5c68bdd8e).


Source: https://datavisions.ai/docs/creators/platform-services/forms
