Free browser-only decision record

COI Requirement Exception Decision Record

Keep each written requirement, proposed exception, insurance-availability response, authorized client decision, condition, effective period, and next checkpoint in one traceable record.

No document uploadUse short neutral references rather than confidential contract or policy text. Entries remain in this tab and exports are created only on your device.
A proposal is not approval. This tool cannot waive or amend a contract, change insurance coverage, authorize certificate wording, or decide whether an alternative is acceptable.
1

Identify the controlling request

Use one current source and project context. If sources conflict, keep the exception in clarification status.

2

Record each proposed exception separately

One row should preserve one baseline, one specific proposal, one decision, and one downstream action.

Review this proposal
Review this proposal
Activate this row
Activate this row
Activate this row
Activate this row
Activate this row
Activate this row
Activate this row
Activate this row
3

Confirm the decision boundary

Preserve the response exactly and keep insurance availability, client acceptance, contract effect, and package status separate.

Separate availability from acceptance

1

Preserve

Keep the original requirement and exact proposed difference visible.

2

Route

Send policy availability to the issuer and the exception decision to the authorized client owner.

3

Control

Record the written result, conditions, effective period, package version, and next checkpoint.

Read: How to request an exception · What to record · Alternative evidence decisions