These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Environmental Compliance
- Features
- Review and evidence
Review and evidence
Keep assessment attachments, revision-linked decisions and operation outcomes together.
OverviewOperation exceptions×
Environmental Compliance · Review and evidence
New
Operation exceptions
Operation receipts
| Operation key | Action | Expected revision | Result state | Occurred at | Failure reason | |
|---|---|---|---|---|---|---|
| OK-451 | ACT-674 | 890 | Failed | 17 Oct | Cut to length | |
| OK-231 | ACT-571 | 540 | Needs review | 04 Oct | Weld frame | |
| OK-943 | ACT-506 | 380 | Failed | 20 Oct | Drill and tap | |
| OK-477 | ACT-367 | 400 | Needs review | 18 Oct | Deburr | |
| OK-853 | ACT-186 | 190 | Failed | 04 Oct | Assemble |
6 of 6 records
OK-451Operation receipts · OR-11164
FailedActionACT-674
Expected revision890
Occurred at17 Oct
Failure reasonCut to length
ParentASS-27143
What you can do
Make the decision traceable
The assessment is the common parent for supporting attachments, permit measurements, review decisions and operation receipts. An attachment names its evidence type, uploader, upload date and visibility. A reviewer decision names the independent reviewer, decision, reason, decision date and source revision. The source revision matters when a measurement changes between submission and decision. The reviewer checks the reading and its support under the assessment before recording a decision. The operation receipt records the attempted action, expected revision, result and occurrence date.
These records answer different questions. The attachment shows what was available. The decision shows what the reviewer concluded and why. The receipt shows what happened when a guarded operation was attempted. A completed receipt should not replace the reviewer’s reason; a failed receipt should remain visible so the lead can investigate the attempted change.
How the work is organized
- Attachments. Keep supporting files under the assessment with explicit evidence type and visibility.
- Decisions. Record approve, reject or return with a reason and the source revision reviewed.
- Receipts. Inspect each operation result and retain its key, expected revision and failure reason.
What to agree during setup
Decide which evidence types are required for a submitted permit measurement and whether an attachment is internal or shared. Agree how the reviewer verifies that an attachment belongs to the reading under consideration. Define how a changed reading is resubmitted so the decision refers to the correct revision. Identify who investigates failed and needs-review receipts and how they determine whether another attempt is appropriate.
The reviewer and recorder should rehearse a returned submission. A missing required file must lead to a return rather than an approval. A decision for an older revision must not silently approve a newer value. The compliance lead should be able to inspect both the human reason and the operation outcome before treating the case as settled.
Check the handoff on an actual case
A recorder submits a permit reading after adding a source file to its assessment. The independent reviewer checks the measurement and attachment. The attachment’s evidence type and upload date help establish what was present at review time. The reviewer records an approve decision with a reason and the source revision. If a guarded attempt is made, its operation receipt shows the action, expected revision and result.
Now consider that the attachment was omitted. The reviewer records a return decision with a reason. The recorder adds the evidence and submits the revised measurement. The reviewer examines the new revision before deciding again. If the guarded operation fails, the receipt records the failure reason and remains in the exception view for follow-up. No participant needs to infer the outcome from a changed status alone.
What your team sees
- Operation exceptions — Investigate failed or needs-review guarded attempts.
- Measurements awaiting review — Find submitted readings whose evidence and revision need a decision.
- Measurement decisions — Revisit the resulting status and decision date.
Follow the work through
Rehearse evidence and operation review alongside permit measurement review.
What it keeps track of
Data model- Record attachments
- Supporting evidence files linked to an assessment.
- Review decisions
- Independent reviewer decisions recorded per source revision.
- Operation receipts
- Durable receipts for each guarded operation attempt.
- Assessments
- Compliance assessment periods covering planned tests and review.
- Permit measurements
- Permit readings logged against an assessment for exceedance review.
- Team members
- Named people holding compliance roles within an organization.
Who uses it
Permissions- Independent Reviewer
- , Measurement Recorder, Compliance Lead, Assessment Owner, Admin
Set up Environmental Compliance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.