# Tables and records

A table holds structured records, such as your customers, jobs, or equipment. Forms can be set up to add a row to a table automatically when someone submits, but not every form does this: check the form's setup first if you're relying on it.

## Before you change a table

1. Open the table and look at the existing rows and columns.
2. If an agent is helping, ask it to confirm exactly which table and row it means before it changes or removes anything.

## Keep records accurate

Use fields consistently so records stay easy to filter and compare later. A table is shared: a bulk update can affect other pages, forms or follow-up work that rely on the same records. Before changing many rows at once, review a small sample first and ask your agent to show you the proposed changes before it applies them. Keep job-specific discussion on the task, not scattered across table rows.

~~~
In Forge, find the [customer/job] record for [name]. Summarise the current fields and ask before changing anything.
~~~

~~~
Check this proposed import against the [table] fields. Show which rows would be added or changed, but do not import it.
~~~

## Related help

- [Forms and surveys](/help/forms)
- [Knowledge and connected records](/help/knowledge)