How to prepare an accurate insurance submission for an architecture, engineering, or consulting practice

A submission needs attention when the firm starts a new discipline, expands into design-build or construction-phase work, accepts larger projects, changes entity structure, adopts a new technology platform, or brings in subconsultants. A title such as “engineering firm” is not an operating description. The market needs facts about the work, who performs it, and how obligations are allocated.

Treat this as a documentation exercise before it becomes a coverage discussion. Write down the date the change began, the client or project affected, the people responsible, and the work performed. That record supports a clearer conversation with Kearny Risk, counsel where contract interpretation is needed, and the market. It does not establish that a policy will respond to a particular allegation.

Prepare entity information, current services, revenue by practice, payroll by duty where requested, project list, sample agreements, insurance exhibits, subcontractor process, client sectors, data and security information, prior policies, loss history if requested, and material change log. Have operational owners verify the narrative before it is sent. Keep a dated copy of everything submitted.

For each document, note the version date and whether it is proposed, signed, current, or expired. Keep confidential client materials in an agreed sharing channel rather than attaching them to ordinary email or calendar notes. A clean file also makes it easier to explain changes at the next renewal, when a client asks for evidence, or when a project manager needs to locate the source of a requirement.

Review the application questions against the service description and contracts. Then compare the resulting proposal’s named insureds, service definition, exclusions, limits, retentions, retroactive date, reporting conditions, and endorsements with the submission. If a question is answered through a schedule or attachment, preserve that attachment with the policy file.

The review should identify differences rather than forcing a yes-or-no answer from incomplete information. If a proposal refers to a specimen form, schedule, or manuscript endorsement, request the version intended for the account. Keep the comparison with the final declarations and endorsements so future reviewers can distinguish what was discussed from what was issued.

Write the architecture, engineering, or consulting practice description in plain operational language. Explain what the firm designs, analyzes, observes, manages, or delivers; who engages the firm; who signs and reviews work; how subcontractors are used; where projects occur; and what is changing. Avoid copying a website slogan into a business insurance application. An underwriter needs a factual picture that can be reconciled with contracts, revenue, staffing, and current projects.

Before submission, cross-check the narrative against contracts, service catalogues, entity records, project lists, and current policies. After terms are returned, compare the proposal’s named insureds, scheduled services, exclusions, limits, retention, retroactive date, conditions, and endorsements against the facts supplied. Where a proposal refers to an attachment or manuscript form, retain that version and request clarification before assuming the summary describes the final policy.

Preserve a dated copy of the final application, attachments, backup documents, and any material update sent after submission. Record who verified each major answer and what documents supported it. At renewal, begin with this file and a change log rather than a blank questionnaire. The resulting record supports accurate commercial insurance conversations as the design practice evolves.

The most useful submission preparation review has a clear sequence: identify the business change, collect the original documents, describe the operational facts in plain language, compare the proposed commercial insurance terms, and record the unanswered questions. That sequence prevents a coverage conversation from becoming a search for reassuring phrases. It also gives a consulting, architecture, or engineering firm a repeatable way to involve the project leader, finance owner, contracting team, and technology or operations owner without asking one person to reconstruct every fact alone.

Use the article’s topic as a meeting agenda, not a substitute for a policy review. Start with the current contract and service scope, then identify the exact policy forms, declarations, endorsements, certificates, applications, or renewal materials that need to be read. Where a fact is uncertain, record the question and the person who can confirm it. Where a client request is broader than available evidence, distinguish the request from the issued business insurance documentation rather than silently treating the gap as resolved.

Finally, preserve the decision trail. The selected proposal, final policy documents, material correspondence, and revised client requirement should sit in a single controlled file. This makes the next renewal, certificate request, project amendment, or change in personnel substantially easier to manage. It also maintains the right boundary: this guide explains a review process, while policy wording, declarations, endorsements, applicable law, and the facts of a specific matter determine whether insurance responds.

Ask what changed since the prior application, which answer needs support from an operating owner, what client requirements should accompany the submission, and what event should trigger an update before renewal.

Record the answer, the document reviewed, the person who provided it, and any limitation or next action. After terms are selected, compare the issued declarations and endorsements with the selected proposal and file the final record. This guide is general education, not a coverage opinion or legal advice. Policy wording, declarations, endorsements, applicable law, and the facts of a matter control.

• What changed in the services, project role, contract, entity, data, or operations?
• Which current policy, declarations, endorsements, and contract clauses should be in the review file?
• Which definition, exclusion, condition, limit, retention, sublimit, or date needs a form-level answer?
• What must be documented, escalated, or revisited before the next project change or renewal?

Select one ordinary project and one project that stretches the firm’s usual work. For each, trace the proposal, signed agreement, disciplines involved, deliverables, subconsultant roles, site activity, data handled, and final client acceptance. If the submission’s two-sentence service description cannot account for both projects, revise it before requesting terms. An underwriter should not have to infer construction-phase work or implementation duties from a generic practice label.

Reconcile the sample with revenue by service, active-project list, website descriptions, and contract templates. Differences are not necessarily errors, but they require explanation. Mark estimates and future plans clearly rather than mixing them with completed work. Keep client-sensitive project materials in an approved exchange channel, not in a public quote form or calendar note.

When proposals arrive, verify that each option used the same named entities, services, project geography, contract requirements, payroll or revenue basis, claims history, and effective date. Compare professional-services definitions, exclusions, retentions, defense expenses, retroactive dates, cyber terms, and general-liability operations by document reference. A price grid cannot reveal whether one market quoted a narrower account description.

After selecting terms, check the issued declarations and endorsements against both the final application and the selected proposal. Record missing attachments, changed forms, open subjectivities, and the person responsible for each follow-up. Retain the signed submission, written answers, issued documents, and comparison in one controlled folder so the next project change starts from a reliable baseline.