Some quick thoughts …
-
Follow database normalization rules. If you get the schema right, adding more data should not cause issues (up to Airtable’s record limits).
-
Get the schema solid, then build interfaces for your users that fit their workflows. Show them everything they need and nothing that they don’t.
-
Most of your linked relationships seem fine. Having resources linked to both Projects and Tasks might be a bit more complex than necessary. For my team, having resources linked at only a single level makes it easier for them to know where to link the resources and where to find them, but your mileage may vary.
-
If you have more than one linked relationship between two tables, make sure you understand the distinct purposes and name them appropriately.
-
If you have “circular” or “triangle” linked relationships, versus a tree structure (parent/child), make sure you understand the reasons why that is necessary instead of lookups/rollups.
-
The Base Schema extension should be able to show the relationships in your six tables without being a tangled mess. Just turn off all the lookup/count/formula/rollup/etc relationships and show only the linked relationships.