database design for a checklist app (units, inspections sheets, inspection questions)

I am working on a checklist app for inspection sheets for users on our shop floor. It's a paper process currently and they want to digitize it. I am using Postgres SQL for the database. I started out just making tables as I go but then they told me the number of inspections is over 100 so I'm hoping to find a more efficient way to do things. to start, we have different units that inspections fall under. For example, 1621 is a unit and we have I think 19 units. Within each unit there are at least 15 inspection sheets (assembly, roof enclosure, generator assembly, etc) and they have a different number of questions in each one. There is some overlap to the the inspections per unit (what I mean is most of the units have a generator assembly, roof assembly, and some others) but the questions for the inspection can/are be different per unit. I started by making 6 tables for 3 of the inspections before they told me about the units portion of the project. So I had a table with the questions for an inspection and a table for the submissions. I really don't want to go about it this way but if that's the best option I will stick with it. Can anyone guide me towards some already created schema's I can build off of or resources to read/watch/etc that may help?