QC exception check: a clickable concept
This page runs a set of plain rules over a sample package: a concrete field sheet, lab cylinder breaks and a fill compaction log. Every value is compared with the spec limits. Anything outside a limit, missing or mismatched becomes a flag for an engineer to decide.
Spec limits here are illustrative only. They are not real CSA, OPSS or CCIL acceptance criteria, and this is not engineering advice.
The sample package
| Clause | What it covers | Limit |
|---|
| Ticket | Slump (mm) | Air (%) | Temp (degC) | Batch time | Placement time |
|---|
Cylinder sets on the field sheet:
| Set ID | 7-day (MPa) | 28-day (MPa) |
|---|
| Area | Location | % of SPMDD |
|---|
SPMDD: standard Proctor maximum dry density. This test set is separate from the slab pour.
Run the check
Pick a package, then press Run check. The rules compare every value with the spec limits and list anything that needs an engineer's decision.
Ready: Sample package 1 is loaded.
Flags for the engineer
Each flag shows the spec limit next to the measured value and where the value came from. Choose Accept, Reject or Add note. Your choice is recorded on this page only.
No check run yet. Press Run check.
Engineer decisions: summary, ready for an engineer
Run the check to build the summary.
How this works
- Plain rules. This first version is plain, rule-based, repeatable logic. Each value is compared with a fixed limit from the spec sheet, and the same package always gives the same flags.
- Nothing changes. The check only reads values. It never edits a value and never signs anything off.
- The engineer decides. Every flag waits for an engineer's choice. Nothing is sent anywhere.
- What could come next. AI could draft the write-up from these flags, such as a results summary or a note to the contractor. An engineer would still review it before anything goes out.