What happens when an inspector's certification expires mid-schedule?
Assignments are restricted automatically when a certification lapses, rather than relying on someone noticing. This is one of the quieter compliance risks in a large inspection programme, because certifications expire on their own schedule and the person who knows is rarely the person building next week's rota. If a lapse is missed, the work still gets done and looks complete, and the problem only surfaces when an auditor checks who signed off a regulated inspection. Tracking training completions and qualification expiry alongside the assignment logic closes that gap at the point it matters, which is when work is being allocated. The manager sees the coverage problem while there is still time to reassign, instead of discovering an invalid record afterwards.
How do we give a contractor access without exposing the whole project?
External contractors receive scoped access rather than an account that sees everything. They view the inspections assigned to them and submit their evidence, and the rest of the project data stays invisible to them. This is usually the blocker to bringing subcontractors onto a platform at all, because the alternatives are a shared login, which destroys the audit trail, or emailing forms back and forth, which destroys the record. Scoped access keeps the contractor inside the same system as the work, so their submissions carry the same evidence and timestamps as everyone else's. The commercial relationship stays separate from the data, which is what makes it safe to include them.
Can a regional manager see only their own region?
Yes. Users are organised into teams, departments, regions, and business units so the structure mirrors how the organisation actually runs, and data visibility is scoped to that structure. A regional manager sees their sites, a national team sees the portfolio, and an executive view rolls it all up. Getting this right matters for more than confidentiality. When managers see only their own scope, dashboards stay legible and people act on what is theirs rather than filtering a national list every morning. It also makes accountability unambiguous, because there is no argument about whether a site belonged to someone else when a result is questioned.
How do we spot an overloaded inspector before work slips?
Workload is visible as assignments are distributed, so imbalance can be seen and corrected rather than inferred from missed deadlines. Overload rarely announces itself. The usual pattern is that the most reliable inspector quietly absorbs extra work until quality drops or something is skipped, and the first visible sign is a compliance gap. Seeing assignment distribution alongside completion rates, average inspection time, and quality scores lets a manager tell the difference between someone who is slow and someone who is carrying too much. Balancing before that point is cheaper than investigating afterwards, and it removes a common reason good inspectors leave.
Can we run several business units from one platform?
Yes. A multi-tenant structure lets multiple business units, subsidiaries, or client accounts run from a single instance while keeping their data and permissions separate. This suits organisations that grew by acquisition, and service providers who run inspection programmes on behalf of several clients who must never see each other's records. The alternative is a separate deployment per entity, which multiplies administration and makes any consolidated view a manual exercise. Keeping them in one platform means central reporting stays possible, roles and certifications are administered once, and a new business unit is a configuration change rather than a project.
