Sites, Units and Locations
Snaglite is built around a simple structure that keeps inspection data organised and easy to report.
Inspection hierarchy:
Site → Unit → Location → Snag
Each level sits inside the one above it. This means snags belong to locations, locations belong to units, and units belong to sites.
Sites
Site
A site is the top-level record in Snaglite. It will usually represent the overall development, scheme, property or job.
Examples might include a housing development, an apartment block, a school project or a commercial fit-out.
You will normally create a separate site for each distinct project or inspection commission.
Units
Unit
A unit sits within a site. It represents the individual property, plot, apartment, house, block or other inspection division that you are inspecting.
The right unit structure will depend on the job. On a housing development, each plot may be a unit. On a larger building, a floor, flat or tenancy area may be a unit.
Keep unit names consistent. This makes navigation, search and reporting much clearer.
Locations
Location
A location sits within a unit. It is the specific room, area or sub-space where the snag is found.
Typical examples include Kitchen, Bedroom 1, Bathroom, Hallway, Plant Room, External Works or Communal Corridor.
Location names should be specific enough that another person can understand the record without explanation.
How this structure works in practice
A typical example might look like this:
- Site: Oak View Development
- Unit: Plot 12
- Location: Kitchen
- Snag: Scratch to worktop edge adjacent to hob
This structure keeps each defect tied to the correct place in the inspection record.
Notes and attachments
Depending on how you use the app, sites and units may also include broader notes or attachments. These are useful for holding context or supporting information that does not belong to one individual snag.
Examples might include drawings, specifications, on-site scans, general inspection notes or supporting photographs.
Good practice
- Use clear, recognisable site names
- Keep unit naming consistent across the project
- Use practical location names that match how the building is actually described on site
- Avoid duplicate or vague labels where possible
- Set up the structure properly before adding a large number of snags