Hi @rcanaway -
Thanks for your question and welcome to Tulip Community 
A couple considerations here:
- You can use linked records within a single table to accomplish these parent-child type relationships
- a limitation of linked records is that they cannot be used in queries and aggregations (You can do a workaround as suggested here Allow Table Queries to Filter Over Linked Record Fields)
- You could also consider a table structure where each row is unique (ex. Parent 1, Child 1, More Info; Parent 1, Child 2, More Info, etc.)
- this type of structure would rely on uniqueID for tracking each parent-child combo and could use queries and aggregations
- That being said, it is worth reading this thread here (Reflexive Linked Record?) to see @giladl’s recommendation:
“We recommend that there is a table for every level or type of assembly or component. For example a “Devices” table that is linked to an “Assemblies” table that is linked to a “Sub Assemblies” table that is linked to a “Components” table. In this way anybody either with or without Tulip experience can immediately understand and use the data.”
@jasonh and @Preston may have some god insights here as both of them have navigated table hierarchy within Tulip tables as well.
As for make this natively easier within Tulip to manage these type of parent-child relationships within a table, our Product Team is aware of this and has some longer term work that should make it easier, but I don’t have any details on that yet, as it is still a ways away due to other priorities on our roadmap!
Hope this helps 