From looking at things, what I'm working on sounds very smilar to this:
Very open to ideas. I'm considering the prospect of setting up tabs within the audits for handing each question section so they don't have to scroll through as many as 91 questions on a single layout.
I think your making it harder than it needs to be
Your not crunching numbers, and it appears to be a simple text database bulding description and inspectors, with some code references
you could probably get it all into two Tables then just make some menus with some portals
anyway I would try to simply it first, then you won't have all the referencing to worry about.
Actually my original plan was a table for each audit type tied to a table with the stuff common to all of them & essentially calling it done. Then the decision was made to make things relational for various reasons. So this is where I'm at.
I sincerely doubt that this could all be done "in just two tables".
But what handicaps anyone who comes at this cold is that while you know the purpose and function of each table occurrence in Manage | Database | Relationships, anyone else will not know that nor will they always be able to tell when you have two occurrences of the same table in your relationships graph.
So you'll need to explain things in a bit more detail.