Client record columns

Adding your own fields to every client record, and why they show up everywhere at once.

2 minute read

The basic contact details are the same for everybody. What you keep on top of that depends entirely on your trade: a company number, an Instagram handle, a vehicle size, a hosting login, a delivery preference.

Those are columns you define yourself, and they apply to every client record you have.

Adding one

From My fields, create a reusable field whose scope is client record field. You choose its type as you would for any question: text, number, date, list, checkbox.

They apply immediately, everywhere

This is the important part, and it is the opposite of how form questions behave.

A column added today appears immediately on every record, including the ones created last year. They are empty, of course, but they are there and you can fill them in.

In the same way, renaming a column renames it everywhere, and deleting one removes it from every record.

The contrast again, because it is the only thing genuinely confusable between the two kinds of preset:

Behaviour
Form question Copied on insertion. Editing the preset touches nothing that already exists.
Client record column Read live. Editing the preset changes every record at once.

That is not an inconsistency: a form already sent must never change under the client's eyes, and a client record must always reflect what you know today.

What not to put in one

Anything belonging to a job rather than to a person. The colour chosen, the fitting date, the budget: those change with every order, so they belong in the form, not in the record.

The question to ask is "will this still be true in two years?" If yes, it is a record column. If not, it is a form question.

Updated on August 25, 2026

Read next