Phase control

Insurance Requirements by Project Phase: COI Evidence Workflow

Award, mobilization, active work, renewal, closeout, and completed operations can create different evidence checkpoints. Map the written phase instead of treating one accepted package as permanent or every future request as already due.

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

Project phases are administrative markers. They do not determine when coverage exists or how a claim will be handled. Use the policy, endorsements, applicable law, and licensed professional for coverage questions.

A practical evidence-phase map

Phase	Typical administrative question	Record to preserve	Do not assume
Bid or qualification	What evidence will be required if selected?	Current solicitation and exceptions	That preliminary evidence satisfies award
Award or contracting	Which terms and parties appear in the final agreement?	Executed source and dated clarification	That a bid exhibit remained unchanged
Pre-mobilization	What must be received before access or work?	Submission package and receipt	That upload equals acceptance
Active work	Have operations, trades, sites, parties, or dates changed?	Change log and current evidence	That initial acceptance covers every change
Renewal	Which policies or documents need refreshed evidence?	New issued package and renewal receipt	That old endorsements or dates remain sufficient
Closeout	Which work is complete and what remains open?	Completion record and unresolved items	That closeout ends every obligation
Post-completion checkpoint	Does the written agreement request later evidence?	Specific requirement, date, owner, and response	That a certificate itself changes policy terms

These phases are a planning framework, not universal contract rules. A client may combine them, use different names, or require evidence at another milestone. Record the exact phase language from the source and connect it to the requirement row.

King County’s DCHS guidance says proof of active insurance is needed before contract signing and service and should continue through the life of its contract. That is one public agency’s process, but it demonstrates why “before work” and “during the contract” are separate checkpoints. The specific agreement and client instructions still control each project.

Build a phase-aware COI evidence workflow

Define the trigger. Use an observable event such as award notice, signed contract, site access date, mobilization, policy expiration, substantial completion, or written client request.
Identify affected rows. Do not reopen every requirement if only one trade, location, or evidence item changed.
Confirm the source. Record the document or message and its date.
Assign scope. Choose project-wide, trade, location, phase, a combination, or unresolved.
Assign ownership. Separate client clarification from agent issuance, contractor facts, portal support, and legal review.
Set the next action. State what will be requested, compared, delivered, or confirmed.
Preserve the package version. A renewed or corrected file set becomes a new snapshot.
Record destination status. Keep preparation, submission, receipt, review, correction, and acceptance distinct.

Map by phase

Connect each evidence request to the milestone that activates it.

Build a private scope matrix and surface missing qualifiers, conflicting sources, and clarification ownership.

Map phase requirements

Control the transitions between phases

Bid to award

Compare the final agreement with the bid instructions. Mark added, changed, apparently removed, unchanged, and unclear items. Do not rely on the earlier checklist merely because the project name is the same.

Award to mobilization

Confirm the exact parties, work location, operations, trade, evidence recipient, and deadline. Ask the licensed agent what accurate issued evidence can be prepared. Preserve delivery and receipt separately.

Active work to renewal

Inventory policy expiration dates and the client’s evidence deadline. Determine which sites and trades remain active. Start the request early enough for clarification, issuance, internal comparison, delivery, and receipt.

Active work to closeout

Identify which operations actually ended, which corrections remain open, and whether any written post-completion evidence checkpoint exists. Do not convert a schedule milestone into a coverage conclusion.

Closeout to later checkpoint

Retain only the follow-up tasks supported by the written requirement and approved retention process. When the client asks for refreshed evidence, reconnect the request to the project, trade, location, phase, source, and current owner.

Ownership at each phase

Question	Primary owner	Useful input
Which phase or deadline applies?	Client or reviewer	Current written instruction
What policy-backed evidence can be issued?	Licensed agent or issuer	Exact requirement and project facts
What work, trade, site, and dates are accurate?	Contractor or vendor	Operations and project schedule
Why is an upload missing or rejected?	Portal or process owner	Timestamp, filename, category, error, reference
Which conflicting contract term controls?	Qualified legal or commercial reviewer	Both source versions and change history

Ownership can move as facts develop. An unclear phase begins with the client; once clarified, an evidence question may move to the agent; once evidence is issued, the contractor may review and deliver it; a technical failure moves to the portal owner. Keep each handoff visible.

Phase-based warning signs

A deadline predates the source that supposedly created it.
A pre-mobilization row has no mobilization date or client confirmation.
A renewal row copies an old package without checking active sites and trades.
A closeout row is marked project-wide while work continues at another location.
A post-completion request has no written source or owner.
An “accepted” portal status is used as a coverage conclusion.
Conflicting phase language is routed only to the agent even though the client must clarify the requirement.
The new package overwrites the prior submission history.

Recommended project record

For each phase event, preserve a neutral project reference, source label and date, requirement rows, scope qualifiers, owner, next action, planned due date, package version, delivery route, receipt, reviewer response, and unresolved questions. Keep confidential documents and issued evidence in the approved record system rather than copying them into a public browser tool.

The University of California’s certificate resources describe certificate workflows and renewal responsibilities in its own institutional setting. Together with public contract guidance, this supports a general control principle: evidence can require refreshed action at later dates, and the responsible office or issuer matters. It does not create a universal renewal schedule.

Frequently asked questions

Is mobilization the same as policy effective date?

No. Mobilization is a project event; the policy effective date is part of an insurance period. Compare them but keep them distinct.

Does an accepted pre-mobilization package cover the renewal phase?

It documents that review event. A later written request or expiring policy period may require updated evidence.

Should completed operations always be a separate phase row?

Use a separate row when the source identifies a later period, different evidence, different owner, or distinct next action. Ask the agent about the applicable policy evidence.

What if the project schedule changes?

Preserve the old and revised dates, identify affected requirement rows, and confirm changes with the appropriate client and insurance contacts.

Can the tool decide that a requirement ended?

No. It records user-entered source states and prompts. The contract and authorized reviewers determine the obligation.

Sources and scope

The phase framework is original administrative guidance. It does not determine policy coverage, legal obligations, or client acceptance.