Recognize the allegation without trying to label it
A client may raise a concern in a meeting, email, invoice dispute, demand letter, or formal complaint. AIA risk-management guidance emphasizes a quick response and attention to the policy’s claim-reporting requirements. The firm should not decide from the client’s tone whether the issue is “only a question” or “already a claim.” Preserve the communication and check the policy definition of claim and any provisions for reporting circumstances.
Create an initial issue record with the project, client entity, date first received, person who received it, exact words used, requested remedy, work at issue, and any deadline. Keep the original message. If the concern arrived verbally, make a dated account of who was present and what was said, clearly marked as the firm’s record rather than a quotation. Assign an internal owner for the next steps.
Separate immediate safety or project-stabilization needs from the insurance question. A condition requiring urgent attention should be escalated under the project’s operational procedures. That action does not settle whether the firm was responsible or whether a policy responds.
Freeze the versions that show what work was actually done
Collect the executed engagement agreement, amendments, statements of work, project schedule, client instructions, assumptions, drawings, models, calculations, review comments, submittals, field reports, and change orders relevant to the allegation. Preserve versions and transmission dates. A current final drawing may not show what the team sent before a disputed decision or what the client approved at the time.
Document who authored, checked, approved, and transmitted the material. If a subconsultant supplied a calculation or drawing, keep the relevant agreement and handoff records. Do not overwrite annotations or consolidate differing versions into a new “clean” file. A concise index can point reviewers to the original documents without changing them.
Where site conditions matter, preserve dated photographs and observation notes with location and context. AIA guidance on site photography recommends using images to support specific field-report points. An unlabeled photo or later recollection is less useful than a contemporaneous record tied to the project issue.
Build a timeline from source documents
The timeline should start with the original scope and relevant design decision, then show client input, internal review, issued deliverables, field observations, revisions, and the first allegation. For every event, cite an email, drawing revision, meeting minute, report, or other original record. Mark uncertain dates and missing documents instead of inventing continuity between entries.
Keep contract obligations distinct from technical facts. A drawing may show what was designed, while the agreement may identify who had authority to approve a change or inspect a condition. The timeline is a factual aid for claims and counsel review, not a final interpretation of standard of care, responsibility, or policy coverage.
If multiple entities participated, maintain a participant map. The owner, architect, engineer, specialty consultant, contractor, fabricator, and city reviewer may have different roles in the project record. A vague reference to “the design team” can hide which entity performed or approved the disputed task.
Check notice, consent, and counsel provisions promptly
Read the issued professional-liability policy and endorsements for the definition of claim, notice recipient, reporting time, known-circumstance provisions, consent requirements, defense arrangements, and any condition about admissions, settlement, or voluntary payments. AIA advises reporting in accordance with the policy and documenting notice in writing. The California Department of Insurance likewise advises timely reporting under commercial-policy duties.
Do not assume that telling a client, a project manager, or a certificate contact also notifies the insurer. Record the actual notice channel, date, materials sent, acknowledgment, claim reference, and person who confirmed receipt. If more than one policy or period may be relevant, raise that question with the account and claims contacts rather than choosing a period from memory.
Legal strategy, preservation duties, privilege, and response to a formal demand require appropriate counsel. The insurance record should identify those questions early, not attempt to answer them with a generic website checklist.
Control the client response and ongoing project work
Select one person to coordinate client communication while technical staff preserve records and continue necessary work under approved direction. An initial response can acknowledge receipt and state the process for review without making an unsupported admission, promising reimbursement, or stating that insurance will pay. Keep each proposed response with the issue file and involve the appropriate claims or legal adviser.
If the client asks the firm to correct work, continue services, or change the contract, document the request and decision separately from the allegation. A project fix may be operationally urgent but can create additional scope, cost, or consent questions. The firm should not erase the original condition or revise a document without maintaining the version history.
Track deadlines for project decisions, client responses, notice, and document production in one log. Assign an owner to each item. This reduces the risk that a design team focuses on a technical correction while a contractual or policy reporting task is left unresolved.
Keep a claim diary and a project-change record
The claim diary should record each material contact: date, participants, channel, question, documents supplied, written answer, and next action. Store insurer and counsel communications with appropriate access controls. Keep the project file and claim file linked but distinct so ordinary project staff do not accidentally treat a claims assessment as an approved scope revision.
After the immediate issue is managed, compare the allegation with the firm’s current service inventory and renewal application. Did the work include a new discipline, site role, software process, or subcontractor relationship? If so, add a factual change note for the next account review. Do not rewrite a prior application or project record to make it appear that the new fact was known earlier.
Use the file to ask precise coverage-review questions
A concise closing packet can include the original allegation, project agreement, issue timeline, key deliverable versions, field records, notice proof, responses, and an open-item list. Ask which policy definitions, dates, retentions, defense terms, and endorsements require interpretation against the actual facts. A quote summary or certificate is not a substitute for those issued documents.
Policy wording, declarations, endorsements, contract terms, facts, and applicable law control. This guide is educational documentation guidance, not a legal opinion or claim determination. Its value is a reliable record and a disciplined path for asking the right questions while evidence is still available.
- Preserve the client’s original communication.
- Index contract, scope, drawing, model, and revision history.
- Make a source-backed timeline and participant map.
- Check the policy’s notice and consent instructions.
- Record notice and written acknowledgment.
- Control client communications and project changes.
- Keep a dated claim diary and open-item list.