Quality Control Plans Overview
A quality-control plan defines what must be checked on a project. The shared form attached to each control item defines how the inspection data is collected.
How KS is structured
KS is the tenant-side quality-control domain. It uses reusable company templates and project-specific control plans. When a template is applied to a project, the backend copies categories, control items, and the attached form reference.
- Template: the reusable structure maintained by the company.
- Category: a group of related control items.
- Control item: the specific item or checkpoint that must be inspected.
- Attached form: an existing shared form selected by form_id.
- Project control plan: the copied plan used for one project.
The shared form system defines how answers are collected. KS does not copy form schemas, fields, or field rules when a project plan is created.
What this means for field users
- 1Open the project
Start in the project workspace where the inspection work belongs.
- 2Find the project control plan
The plan should contain the categories and control items copied from a template or adjusted for the project.
- 3Choose the control item
Select the item that matches the work you are checking.
- 4Complete the attached form
The control item decides which shared form is loaded for the inspection.
- 5Submit the inspection record
The saved record keeps the answers, attachments, optional drawing pin, and project context together.
When something looks wrong
- If a control item has no form, ask an admin to attach a published shared form.
- If the form questions are wrong, the shared form needs to be updated, not the KS plan alone.
- If an item is missing from a project, the template may not have been applied or the project plan may need adjustment.