Skip to main content
An inspection set is one filled-out QC form: which template version it came from, what it was inspected against, and the outcome. Standard CRUD applies. See standard endpoints.

Fields

Every property the API returns for a QC inspection set.

Status is derived, and filterable

status is computed on every read from the inspections underneath the set, so you cannot write it. The precedence is worth knowing:
  1. A set detached by rework always reads reworked.
  2. Otherwise the most recently touched inspection decides: failed if anything failed, passed if it passed, information for a questions-only record.
  3. An empty set stays pending.
Because it is a computed column rather than a stored one, you can still filter and group on it:

Where a set came from

triggerKey tells you why the set exists, which matters when you are separating inspections someone chose to run from ones the system opened automatically: null means the set predates the field. rootDeliverableId, deliverableId, stageId, and projectId are all set to null if what they point at is ever deleted. The QC record itself is kept, because losing the inspection history along with the work is worse than losing the link.

What you can write

Everything else in the table above is set by BuildingSwell.

Deleting

DELETE /qc-inspection-set/{id} is destructive.Permanently removes the set and the inspections under it, which is your QC record for that work. This cannot be undone and there is no archive for QC sets.
See archiving and deleting for the full picture across resources.