In general, we recommend keeping the same type of information consolidated within one single table; different tables should only be used to distinguish distinct types of records (e.g. products from clients from events) - not to
categorize things of the same species, like projects for different months, work orders for different companies, or content pieces for different channels. You will quickly hit limitations if records are split up across tables without
warranting such independence.
To optimize your Airtable experience, we highly recommend categorizing records of the same species by using field values and filtered views, rather than filing them into separate tables and/or duplicating them to other tables to
indicate a status change.
For guidance on reworking your current setup, this article
may be helpful.