Mid-project revision

What to Do When a Client Changes Insurance Requirements Mid-Project

A mid-project request can affect schedule, evidence, cost, contractual obligations, and professional review. Slow the change down long enough to identify the controlling source, exact differences, effective timing, and responsible parties.

Reviewed September 2026 · Educational information, not insurance or legal advice

Do not promise immediate compliance. The contractor can acknowledge and organize a revised request, but the client, licensed agent, insurer, and legal professionals control different parts of the answer.

First actions after the revised request

Preserve the message or document exactly as received.
Identify the sender, project, source label, revision date, proposed effective date, and response deadline.
Ask whether the new source replaces the earlier requirement or adds to it.
Freeze the prior source and last submitted package.
Create an item-by-item comparison before requesting replacement evidence.
Record any immediate access, mobilization, payment, or scheduling consequence stated by the client.

A rushed forward to the agent can omit the earlier wording, affected entity, policy line, operations period, or deadline. A structured comparison gives the agent the actual written change and lets the contractor identify client and legal questions separately.

Questions to ask the client

Which document or message is the controlling revised requirement?
Does it replace the complete earlier version or only identified sections?
Which contractors, project phases, locations, entities, or operations are affected?
What is the effective date, and is there a separate evidence-delivery deadline?
Which exact limits, policy lines, endorsements, parties, or formats changed?
How should an unavailable or disputed requirement be escalated?
Does the client require a new full package or only changed evidence?
Which portal route and review status will document the response?

Make the revision visible

Compare the prior and revised request before changing the package.

Classify each item conservatively and create a copy-ready change brief for the proper owners.

Compare requirement versions

Route the impact to the right owner

Question	Current owner	Contractor action
What exactly changed and when does it apply?	Client	Request a current written clarification
What does the policy provide and what evidence can be issued?	Licensed agent or issuer	Send the exact revised request and affected entities or operations
What package, filename, portal, and schedule tasks change?	Contractor	Create a new controlled checklist, version, and deadline plan
Does the revision modify contractual duties or price?	Qualified legal/commercial professional	Preserve both versions and escalate through the approved process
Has the replacement evidence been accepted?	Client reviewer	Record the observable review status and remaining comments

The Texas Department of Insurance states for Texas certificates that a certificate cannot amend, extend, or alter coverage and may not contain false or misleading policy information. A contractor therefore should not attempt to solve a new client requirement by editing certificate wording or promising a policy result.

Consider five kinds of impact

Evidence impact

Determine whether the revision requires a corrected certificate, new endorsement evidence, a different entity schedule, or a changed portal category.

Policy or market impact

The agent should explain availability, timing, underwriting, premium, or policy-change questions within their authority. The comparison tool cannot predict those outcomes.

Contract and commercial impact

A mid-project change may raise questions about change orders, cost allocation, delay, or enforceability. Route them to authorized commercial and legal decision-makers.

Schedule impact

Separate the effective date from the evidence deadline. Build realistic client clarification, agent, review, package, delivery, and receipt milestones.

Record impact

Update the requirement change log, agent request, evidence checklist, filename manifest, resubmission log, and reviewer-response plan as applicable. Preserve prior versions.

Prepare the revised evidence cycle

Confirm the revised source and comparison matrix.
Send only the policy and evidence questions to the agent, with the written request.
Keep client, legal, and portal issues in separate owned queues.
When evidence arrives, compare it with every current requirement row.
Create a new package version and manifest.
Open every actual file and remove stale copies from the staging folder.
Submit through the approved route and preserve the permitted receipt.
Track submitted, received, under review, needs correction, and accepted separately.

Warning signs requiring escalation

The requested effective date predates the written revision.
The client cannot identify which version controls.
The wording asks the contractor to edit or certify insurance evidence.
The agent says the requested evidence cannot accurately be issued.
The change affects contractual price, indemnity, work suspension, or legal rights.
Different client representatives provide conflicting requirements.
The portal silently replaces or obscures earlier submissions.

Frequently asked questions

Must the contractor accept every mid-project change?

This guide cannot answer that legal or contractual question. Preserve the documents and seek appropriate professional advice.

Should the old COI package be deleted?

No. Preserve it according to the approved records policy and keep it distinguishable from the current working and submitted versions.

Can the new requirement apply before replacement evidence is available?

Confirm timing with the client and availability with the agent. Do not invent or backdate evidence.

Does client acceptance mean the revised requirement is covered?

No. Acceptance is a review event, not a coverage determination.

Sources and scope

The workflow is an administrative decision aid. It does not interpret a contract or policy, determine availability, or allocate costs.