The core exception record

Do not copy sensitive source material into the log. A short reference such as “Insurance Exhibit V04 §7.2” is usually more useful than an entire contract paragraph. Keep the actual source in the organization’s approved record system, with access controls appropriate to the document.

Use statuses that describe events

• Draft—not submitted: the proposal is being prepared and has not been sent.
• Submitted: the request was sent through the approved route; receipt may still be unknown.
• Under review: the authorized organization is evaluating the request.
• More information requested: a specific input is required before a decision.
• Accepted in writing: an authorized written source records acceptance and its conditions.
• Declined in writing: an authorized source records that the proposal is not accepted.
• Withdrawn or superseded: the request no longer controls because it was withdrawn or replaced.

A portal label should be copied exactly before it is mapped to a log status. “Complete,” “uploaded,” or “received” may describe transmission rather than substantive review. Do not record “accepted in writing” unless the source supports that conclusion for the exact exception item.

Six controls that prevent exception drift

1. Atomic rows

One row should cover one decision. If a client accepts a temporary timing alternative but declines a lower limit, two rows preserve the different outcomes. A bundled “insurance exception” hides that distinction.

2. Source version

Record the exact source version and date. If the client later revises its insurance exhibit, preserve the old exception against the old baseline and determine whether a new decision is required.

3. Authority label

Record the named function and source, not only an email address. “Client risk manager response dated…” is more durable than an isolated personal inbox. Verify internally whether the responder has authority for the type of decision.

4. Effective period

An exception may apply only before mobilization, until renewal, to one location, for one trade, or through a stated date. Capture beginning, end, project phase, and scope. An empty period should be treated as a clarification question, not automatically as perpetual approval.

5. Conditions

Conditions might require specified alternative evidence, a higher limit at renewal, notification of project changes, a subcontractor document, or a follow-up review. Preserve conditions exactly and turn each operational condition into a task.

6. Package link

Identify which submission version implements the decision and what supporting records accompany it. Acceptance of an exception does not mean an unrelated package defect has been accepted.

Decision matrix example

These are workflow examples, not statements that any client should accept a particular alternative. The authorized parties must evaluate the actual requirement, policy, evidence, risk, contract, and project.

Automated warnings to include

• An accepted or declined row lacks a response date.
• An accepted row lacks a supporting decision source.
• The decision authority is “licensed agent” for client acceptance.
• A limit or endorsement availability statement has no issuer involvement.
• The response date precedes the request date.
• An effective end date precedes the start date.
• The next review falls after the exception expires.
• “Coverage guaranteed,” “fully compliant,” or similar conclusion language appears.
• The same normalized baseline appears twice with different final statuses.
• A row is marked accepted while insurance availability remains unconfirmed and the record does not explain the condition.

Maintain the log through the lifecycle

Before submission

Confirm the baseline, requester, decision owner, factual constraint, available evidence, and deadline. Keep the status draft until the request is actually sent.

During review

Record the sent date and route, then preserve requests for additional information as separate actions. Do not modify the proposal silently after submission; create a revision or note the changed terms.

At decision

Capture the exact response, date, source, scope, effective period, conditions, and responsible function. If the decision is partial, split accepted and declined components into separate records.

At package preparation

Map the decision to the alternative evidence and final filenames. Compare the issued evidence with the proposal. Keep the client decision source in the package record when the approved process requires it, but do not alter the issued documents.

At renewal or project change

Recheck whether the decision remains effective. A policy renewal, new phase, new location, changed operations, revised contract, or additional party may require new evidence or a new exception decision.

At closeout

Preserve the record according to organizational policy. Mark the exception expired, completed, withdrawn, or superseded without deleting the original chronology.

What the log must not claim

The record must not state that coverage exists, a claim will be paid, the contractor is legally compliant, a contract was amended, or a certificate changes the policy unless an authorized source independently establishes the relevant fact. Even then, the log should link to that source rather than become the legal or insurance instrument itself.

The Texas Department of Insurance explains that certificate information cannot be used to amend, extend, or alter policy coverage under its rules. That boundary is a useful reason to keep the insurance evidence, client exception, and contract process in separate columns.

Frequently asked questions

Should declined requests stay in the log?

Yes. They explain why a package, escalation, policy change, or project decision followed and prevent the same unsupported proposal from being treated as new.

Can one exception cover multiple projects?

Only if the authorized source clearly says so. Otherwise use project-specific rows because scope, dates, parties, and requirements can differ.

What if acceptance has no expiry date?

Record the field as not stated and seek clarification when duration matters. Do not invent “permanent.”

Can I attach documents to the browser tool?

No. Use short labels only; preserve documents in the approved record system.

Who updates the log?

Assign an administrative owner, but keep decision authority with the appropriate client, issuer, or qualified reviewer.

Sources and scope

• Texas Department of Insurance: certificates FAQ
• King County: insurance requirements and evidence process
• U.S. National Archives: consistent names, dates, and version control

The log design is original administrative guidance. Retention, authority, contractual effect, and insurance conclusions depend on applicable sources and authorized professionals.