Audit advanced Works with: Any AI

Airtable Base Structure and Normalisation Audit

Table output Has example

• 🧮 Airtable

Check tables and links for duplication and fragility.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Audit the structure of an Airtable base. Tables with fields and types: [TABLES_AND_FIELDS]. Linked records and lookups: [LINKS]. Number of records per table: [RECORD_COUNTS]. Problems noticed: [PROBLEMS].

Check for repeated information that should be a linked table, text fields storing lists, single selects with many near-duplicate options, fields never filled, formulas that depend on text names, a primary field that is not unique, and tables that mix different things. Explain each issue and its effect on reports.

Show one worked example: an Orders table repeating the customer's name, address and phone on every row (5,000 orders, 800 customers) is split into Customers (800 rows) and Orders (5,000 rows) linked by customer, so an address changes once instead of many times. Give before and after counts and the migration steps: create Customers from unique values, link, verify counts, hide the old fields, then remove them.

Return a table with Table or field, Issue, Evidence, Fix and Risk, with the effort in hours and a rollback plan. Take a backup first [VERIFY], list the views, forms and automations that depend on fields to be changed, and do not split tables unless it fixes a real problem.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Invented base. Orders table: 5,000 rows, each repeating customer name, address and phone; 800 distinct customers. Problem: a change of address must be edited on up to 40 rows. Proposed structure: Customers (800 rows) linked to Orders (5,000 rows) by a linked record; address held once. Migration check: customers created from unique names should total 800; every order links to exactly one customer; the sum of order totals is unchanged at 214,350.00. Rollback: keep the old fields hidden for 30 days before deleting.

• airtable