Forms, records and documents
Tables and records
A table holds structured records such as customers, jobs, equipment or leads. Forms can be configured to record answers there, but a form does not create a row unless its setup says so.
Read before changing
Open the table to review the existing rows and columns. When an agent is helping, ask it to identify the table and the exact row first, especially before it changes or removes information.
Keep records dependable
Use fields consistently so a later reader can filter and compare records. Review a small sample before importing or changing many rows. A table is shared workspace information: a bulk update can affect pages, forms or follow-up work that use those records. Ask for the proposed rows and fields before making a change, and keep task-specific discussion on the task rather than turning a table into a notes dump.
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.