Create a form

A form is a way into your workspace for someone who has no need to know how it is structured.

The candidate must not see your hiring pipeline. The client must not see your internal notes. They fill in a few fields, and a record appears on your side.

What a form produces

An answer becomes an ordinary record in the object the form feeds. Not a separate table, not an export to clean up.

Which means it filters, sorts, links and gets handled like the rest, and an agent can pick it up as soon as it arrives.

Internal or public

Internally, a form frames data entry. Rather than opening a record with forty fields, you show the six that matter, in the order you ask them.

Publicly, the form opens from a link, with no account. That is what lets a client, a candidate or a contractor fill it in.

A form is not a record

This is the most common confusion, and it is expensive.

A record shows everything an object carries. A form shows what you want to ask, in the order you want to ask it. Both live on the same object but they do not serve the same moment.

Chaining steps

A form can unfold in several stages rather than on a single page.

Useful when what comes next depends on earlier answers, or when filling it in is long enough that a single page puts people off. Each step is validated before the next, so a mistake is corrected right away rather than on submit.

Before you publish

Two habits that prevent unusable answers.

Fill it in yourself, from the point of view of the person who will receive it. Questions that are obvious to you almost never are to them.

Check what is required. One required field too many makes people give up; one too few brings in half-empty records you will have to chase.