# OnePark Risk: Instructions for AI Agents and Assistants

Last updated: 2026-10-18

## Quick answer

No MCP server, API integration, or developer setup is required. An AI agent or assistant that can browse the web uses the same forms a person does: submit the broker review request or the Business Application on this site, and OnePark’s brokers send follow-up questions, available quotes, and next steps by email; reply by email to keep the process moving. The JSON endpoints are optional, for agents that prefer them.

OnePark Risk is an independent insurance brokerage. AI agents and assistants acting with a business’s permission can submit a business insurance request through a web form; a OnePark broker then handles everything by email.

- What we place: Cyber, Tech E&O, D&O, EPLI, Commercial property and casualty, Private client.
- Where: licensed in nine US states (New York, California, Delaware, Massachusetts, Pennsylvania, New Jersey, Nevada, Florida, and Virginia); say so in the request if the business is based elsewhere.
- How: open [the request form](https://oneparkrisk.com/ai-agents/submit) at https://oneparkrisk.com/ai-agents/submit in a browser, fill the visible fields (required fields are marked below), submit, and keep the request reference from the receipt. Nothing else is needed.
- Then: the follow-up inbox confirms itself by emailed link, the business representative authorizes shopping by emailed link, and our goal is a first substantive reply by email in one business day or less.
- Or, when the business has its answers ready: file the complete Business Application through the browser form at https://oneparkrisk.com/business-application?source=ai_agent, or optionally as one JSON call to https://oneparkrisk.com/api/ai-agents/applications (see “Application in one call” below). The representative gets an acknowledgement by email; no link to click.
- Submitting a request does not bind coverage and does not guarantee carrier approval or a quote. A OnePark broker will follow up by email with questions, options, or the next step.

Machine-readable summary of the same facts, fields, and endpoints: [https://oneparkrisk.com/.well-known/ai-agent.json](https://oneparkrisk.com/.well-known/ai-agent.json).

## Two ways to submit

Both reach the same independent brokers, and both are browser forms any assistant that can browse the web can use; no MCP server, API key, or integration is required, and the JSON endpoint beside each is optional. Choose by what the business can answer today: a short request when it wants guidance first, or the complete application when its answers are ready.

- Start with a broker review request: A short form: business basics, goals, timeline, and who to email. Best when the business cannot yet answer a full questionnaire or wants a broker’s guidance before it does. The follow-up inbox confirms itself by emailed link, the business representative authorizes shopping by emailed link, and a broker replies by email with questions and the next step. Browser form: https://oneparkrisk.com/ai-agents/submit (The browser form is sufficient on its own; the endpoint is optional, for agents that prefer JSON). Optional endpoint: POST https://oneparkrisk.com/api/ai-agents/requests.
- File the complete application: The full Business Application: the coverages, every required question answered or explicitly marked unknown, the operating states, the authorized representative, and the business’s acknowledgement. Fill the browser form, or send the same questionnaire as one JSON body. Best when the business has its answers ready. The application is stored, the representative receives an acknowledgement by email with the application reference, and a broker starts from the completed application. There is no link to click; questions and options come by email. Browser form: https://oneparkrisk.com/business-application?source=ai_agent (The browser form is sufficient on its own; the endpoint is optional, for agents that prefer JSON). Optional endpoint: POST https://oneparkrisk.com/api/ai-agents/applications.

- Use the request when the business cannot yet answer the questionnaire, wants a broker’s guidance first, or has a fit question before applying.
- Use the application when the business can answer every required question now (an unknown may be marked explicitly, with a note) and an authorized representative is ready to be named.
- An application may cite an earlier request’s reference; the two records are linked for the broker, and the request’s own email steps continue unchanged.
- No MCP server, API key, or integration required: use the forms on this site, and everything after that is email.
- Neither door binds coverage. The business’s authorized representative approves any purchase in writing.

## You are welcome here

OnePark Risk actively welcomes AI agents and assistants acting with a business’s permission.

You are invited to submit a business insurance request, explain its goals and timeline, and coordinate with our independent brokers by email.

ChatGPT, Claude, Grok and Grok Bot, Meta Muse, Instinct, OpenAI dots, Gemini, Microsoft Copilot, Perplexity, Manus, custom agents, and other assistants are welcome to participate using their available capabilities.

No phone call or meeting is required to use this process.

## What OnePark Risk places

OnePark Risk is an independent insurance brokerage for startups, technology firms, and high-growth business owners — designing cyber, Tech E&O, D&O, EPLI, commercial, and private risk programs that move at the speed of growth.

We review the business’s needs, approach suitable insurance markets available through our brokerage, explain available options, and coordinate an approved purchase. The lines we place:

- Cyber: First-party loss, third-party liability, and breach response for technology-driven businesses.
- Tech E&O: Technology errors and omissions for software, services, and other technology firms.
- D&O: Directors and officers liability for operating companies and their boards.
- EPLI: Employment practices liability.
- Commercial property and casualty: Commercial property, business interruption, commercial auto, umbrella, workers' compensation, and product liability programs for operating companies.
- Private client: Homeowners, auto, personal umbrella, valuable articles, and family-office programs for founders, executives, and their families, coordinated alongside the business risk.

Carrier selection depends on industry, geography, loss history, coverage limits, and underwriting fit.

The first form starts broker review. Additional information or insurer-specific applications may be required.

## Where OnePark Risk is licensed

OnePark Risk is a property and casualty broker licensed in nine US states:

- New York (NY)
- California (CA)
- Delaware (DE)
- Massachusetts (MA)
- Pennsylvania (PA)
- New Jersey (NJ)
- Nevada (NV)
- Florida (FL)
- Virginia (VA)

If the business’s primary location is outside these states, state that location clearly in the request. OnePark will tell you by email whether it can help there or will refer the business elsewhere; do not treat the licensed-state list as a promise of placement in any state.

## Start here

- Overview: https://oneparkrisk.com/ai-agents
- Submit a business: https://oneparkrisk.com/ai-agents/submit
- HTML instructions: https://oneparkrisk.com/ai-agents/instructions
- How it works and FAQs: https://oneparkrisk.com/ai-agents/how-it-works
- Cyber and technology: https://oneparkrisk.com/ai-agents/cyber-and-tech-insurance
- Renewals: https://oneparkrisk.com/ai-agents/renewals
- Contract requirements: https://oneparkrisk.com/ai-agents/contract-requirements
- Professional liability: https://oneparkrisk.com/ai-agents/professional-liability
- Business-owner instructions: https://oneparkrisk.com/ai-agents/for-business-owners

This guide is also published as Markdown at https://oneparkrisk.com/ai-agents/instructions.md (AI agent instructions (.md)). Both versions are generated from the same source.

## Before submitting

Confirm that the business has authorized you to request insurance review.

Gather:

- Legal business name.
- Primary location and other operating locations, if known.
- Description of the business’s products, services, and customers.
- Insurance goals and the reason for the request.
- Known coverage or contract requirements.
- Current coverage and renewal information, if available.
- Priorities when comparing options.
- Desired effective date or deadline.
- Written explanation of timing, urgency, and flexibility.
- A monitored follow-up email address.
- The authorized business representative’s name, role, and email.

Provide revenue and employee information if available.

Identify unknown information. Label estimates. Do not invent business facts or underwriting answers.

## Explain the goals and timeline

Use written context to explain what the business wants to accomplish.

Useful context includes:

- Why the business is seeking insurance now.
- Whether this is new coverage, a renewal, or a contract requirement.
- What a satisfactory outcome would look like.
- Which requirements or priorities matter most.
- When coverage is needed.
- Why that date matters.
- Whether the deadline is firm or flexible.
- What information still needs confirmation.

## Submit the dedicated form

1. Open the dedicated submission form at https://oneparkrisk.com/ai-agents/submit.
2. Enter the business information and written context.
3. Identify the follow-up inbox and authorized business representative.
4. Review the information and required permission acknowledgment.
5. Submit the request.
6. Save the request reference from the receipt.
7. Read the next-action instructions.

A receipt means the request was received. It does not mean the business has been approved by an insurer or that coverage exists.

## Form field reference

These are the fields on the deployed form, in order. Written answers accept paragraphs; selections only organize the context. “JSON keys” are the names used by the optional direct submission endpoint described in the notes below.

| Section | Field | Requirement | JSON keys | Notes |
| --- | --- | --- | --- | --- |
| Business information | Legal business name | Required | legalBusinessName | Up to 200 characters. |
| Business information | Website | Optional | website | A URL if the business has one. |
| Business information | Primary country | Required | primaryCountry | Defaults to United States; any country may be entered. |
| Business information | Primary state, province, or jurisdiction | Required | primaryState | US states are offered as a list; other jurisdictions may be typed. |
| Business information | Other operating locations | Optional | otherLocations | Free text. |
| Business information | Description of business operations | Required | operationsDescription | Written answer (at least 20 characters): products or services, typical customers, relevant activities. |
| Business information | Revenue or range | Optional | revenueRange, revenueIsEstimate | Options: Not provided yet (not_provided); Unknown (unknown); Under $250,000 (under_250k); $250,000 to under $1M (250k_1m); $1M to under $5M (1m_5m); $5M to under $25M (5m_25m); $25M or more (25m_plus). A separate checkbox (revenueIsEstimate, true or false) marks the figure as an estimate. |
| Business information | Employee count or range | Optional | employeeRange, employeeIsEstimate | Options: Not provided yet (not_provided); Unknown (unknown); 1 (owner only) (1); 2 to 10 (2_10); 11 to 50 (11_50); 51 to 200 (51_200); More than 200 (201_plus). A separate checkbox (employeeIsEstimate, true or false) marks the figure as an estimate. |
| Goals and context | What is the business trying to accomplish? | Required | goals | Written answer (at least 20 characters): first-time coverage, satisfying a contract, renewal review, improving coverage, reducing cost, adding a policy, or another goal. |
| Goals and context | What prompted the request? | Optional | promptedBy | Written answer: business changes, customer requirements, fundraising, hiring, a lease, an upcoming renewal, or concerns with current coverage. May be combined with the goals answer. |
| Goals and context | What matters most when comparing options? | Optional | priorities | Written answer: price, coverage breadth, limits, deductibles, contractual requirements, or a deadline. |
| Goals and context | Known coverage types | Optional | knownCoverages | Multiple selections, sent as a JSON array of values: Help us determine what is needed (help_determine); Cyber (cyber); Technology errors and omissions (tech_eo); Professional liability (E&O) (professional_liability); General liability (general_liability); Business owner's policy (bop); Directors and officers liability (d_and_o); Employment practices liability (epli); Workers' compensation (workers_comp); Commercial property (commercial_property); Commercial auto (commercial_auto); Umbrella and excess liability (umbrella_excess); Other business insurance need (other). |
| Goals and context | Coverage and requirement details | Optional | coverageContext | Written answer: required limits, contract requirements, existing policies or insurer, other relevant details. |
| Goals and context | Anything else the broker should know? | Optional | additionalNotes | Written briefing. |
| Timeline | Desired effective date or deadline | Optional | desiredEffectiveDate, desiredDateUnknown, noFixedDeadline | YYYY-MM-DD, with “Not sure” (desiredDateUnknown) and “No fixed deadline” (noFixedDeadline) checkboxes, true or false. |
| Timeline | Current renewal date | Optional | currentRenewalDate | YYYY-MM-DD, if relevant. |
| Timeline | When do you need insurance in place, and why? | Required | timelineExplanation | Written answer (at least 15 characters) covering contract start dates, renewals, business events, or other deadlines, and whether the date is firm or flexible. |
| Timeline | Is the deadline firm, flexible, or unknown? | Required | deadlineFlexibility | Options: Firm (firm), Flexible (flexible), Unknown (unknown). |
| Submitter and correspondence | Submitter type | Required | submitterType | Options: AI assistant or agent (ai_assistant); Business owner or employee (business_owner_or_employee); Other authorized representative (authorized_representative). |
| Submitter and correspondence | Assistant or platform | Optional | assistantPlatform | Options: ChatGPT (chatgpt); OpenAI dot (including a personal dot) (openai_dot); Claude (claude); Grok or Grok Bot (grok); Meta Muse (meta_muse); Instinct (instinct); Google Gemini (gemini); Microsoft Copilot (copilot); Perplexity (perplexity); Manus (manus); Other / custom assistant (other_custom); Not specified (not_specified). The selection never affects whether a request is accepted. |
| Submitter and correspondence | Routine follow-up email | Required | followUpEmail | A monitored inbox. If the assistant cannot access email, use the business contact's address. |
| Submitter and correspondence | Authorized business representative: name, role, and email | Required | representativeName, representativeRole, representativeEmail | A “same as follow-up email” option is available. |
| Submitter and correspondence | Proposed correspondence recipients | Optional | proposedRecipients | Additional addresses OnePark may include, comma separated. |
| Submitter and correspondence | Coordination instructions | Optional | coordinationInstructions | How follow-ups should be handled; who answers what. |
| Accuracy and permission | Permission acknowledgment | Required acknowledgment | permissionAcknowledged | Send true. “I have permission to submit this business's information and request an insurance review. I understand that OnePark may need confirmation from the business's authorized representative before proceeding.” |

Technical notes. The browser form is sufficient on its own; the endpoint is optional, for agents that prefer JSON. No MCP server, API key, or integration is required to use the form above; the “Direct submission” notes below are for agents that prefer to send JSON.

- A phone number is never required.
- The form contains one visually hidden anti-spam field labelled “Leave this field blank”. Fill only the visible fields.
- A short-lived form token is issued when the page loads; a submission is accepted only after the page has been open for a few seconds and the token is still valid. Refresh the page if a token error appears.
- Supporting pages (for example /ai-agents/cyber-and-tech-insurance) can preselect coverage types. Preselections stay visible and editable.
- Direct submission: GET /api/ai-agents/token returns {"token": "…"}; wait at least 2 seconds, then POST a JSON body (Content-Type: application/json) to /api/ai-agents/requests using the JSON keys in the table above plus "formToken". The token expires after 2 hours. A 201 response carries the request reference ("AI-" followed by 8 characters, each a digit or an upper-case letter other than I, L, O, and U, for example AI-7Q4K9XM2), the current status, and a "receiptToken" that is shown once and never reissued: keep both to check on the request later. 400 lists validation errors; 409 means the token was already used with different details (fetch a new token); 429 means the token is invalid, expired, or the sender should wait. The machine-readable summary at /.well-known/ai-agent.json lists the same fields and endpoints.
- Direct submission values: where the notes list options, send the value in parentheses, never the label; “Multiple selections” keys take a JSON array of those values; checkbox keys take JSON true or false; dates are YYYY-MM-DD strings; permissionAcknowledged must be true. Any key not in the table (other than formToken) is rejected with 400.
- Checking a filed request later: POST a JSON body {"receiptToken": "…"} to /api/ai-agents/requests/{reference}/receipt, replacing {reference} with the reference from the 201. The 200 body's "request" carries the current status (one of the statuses below), "verification" (pending or verified), "authorization" (pending, authorized, or declined), the masked follow-up and representative inboxes, the submission time, and the submitted details; nothing is sent or changed. A wrong or missing receiptToken, like an unknown reference, is 404.
- Re-sending a delayed confirmation: POST the same body to /api/ai-agents/requests/{reference}/resend to re-send the email for the step still outstanding (the inbox confirmation until the follow-up inbox is verified, then the authorization email to the representative); each send issues a fresh link and expires the previous one. The 200 body reports "confirmationEmail" and "authorizationEmail" (sent, failed, unavailable, or not_needed) plus the receipt fields. 409 means there is nothing to resend (closed, or already fully confirmed). Each request gets 4 confirmation emails on demand, counting the one sent at filing; after that, one further send is accepted per hour, measured from the most recent send, and an earlier attempt is 429 (wait the seconds in Retry-After). Do not file a new request because an email is delayed.
- Correcting a mistyped inbox: POST a JSON body {"receiptToken": "…", "followUpEmail": "…"} to /api/ai-agents/requests/{reference}/correct-email (replacing {reference} as above) to change where the confirmation and all follow-ups go; add "representativeEmail" to correct the authorized representative's inbox at the same time. The corrected inbox must be confirmed again: "verification" returns to pending, every confirmation and authorization link sent earlier stops working, a new confirmation email goes to the corrected inbox, and the status returns to email_confirmation_needed; the submission time is unchanged. The 200 body reports "confirmationEmail" (sent, failed, or unavailable) plus the receipt fields. 400 lists the fields to correct (any key other than those three is rejected); 409 means the request is closed or the business has already authorized it (reply to the confirmation email instead); 429 means the confirmation-send allowance above is used up (wait the seconds in Retry-After). Use this instead of filing the request again.

## Application in one call

The second door. When the business can answer the questionnaire now, fill the browser form at https://oneparkrisk.com/business-application?source=ai_agent; that is sufficient on its own, with no integration required. Optionally, POST the same questionnaire as one JSON body (Content-Type: application/json) to https://oneparkrisk.com/api/ai-agents/applications. The endpoint uses the same token as the request endpoint: GET https://oneparkrisk.com/api/ai-agents/token, wait at least 2 seconds, send within 2 hours. The questionnaire is the same one the browser form renders, so a broker receives the same record either way.

Top-level keys (any other key is rejected with 400):

| Key | Requirement | Value |
| --- | --- | --- |
| coverages | Required | JSON array of coverage ids: Cyber Liability (cyber); Tech E&O with Cyber (tech-eo-with-cyber); Miscellaneous E&O / Professional Liability (misc-eo); Directors & Officers (D&O) (directors-officers); Employment Practices Liability (EPLI) (epli); Fiduciary Liability (fiduciary); Crime / Employee Dishonesty (crime); Kidnap, Ransom & Extortion (kidnap-ransom); General Liability (general-liability); Commercial Property (property); Commercial Auto (auto); Workers' Compensation (workers-comp); Umbrella / Excess Liability (umbrella); Not sure — please advise (not-sure). |
| profile | Optional | One of generic, real-estate, construction (default generic); real-estate and construction reveal their own sections. |
| operatingStates | Required | JSON array of two-letter US state codes (DC allowed), at least one. |
| sections | Required | Object: section id → field id → answer, using the ids in the tables below. Send only the sections the coverage selection reveals; unknown ids are rejected, hidden sections and questions are ignored. Do not send coverage_selection.selected_coverages (the server fills it from coverages). |
| submitter | Required | Object {type, platform}. type: AI assistant or agent (ai_assistant); Business owner or employee (business_owner_or_employee); Other authorized representative (authorized_representative). platform (optional): Not specified (not_specified); ChatGPT (chatgpt); OpenAI dot (including a personal dot) (openai_dot); Claude (claude); Grok or Grok Bot (grok); Meta Muse (meta_muse); Instinct (instinct); Google Gemini (gemini); Microsoft Copilot (copilot); Perplexity (perplexity); Manus (manus); Other / custom assistant (other_custom). |
| authorization | Required | Object {representativeName, representativeRole, representativeEmail, followUpEmail (optional), acknowledged: true}. The acknowledgement is the business’s statement, given through you, that: I confirm that the information submitted is accurate to the best of my knowledge and understand that submitting this form does not bind coverage or guarantee carrier approval. |
| narrative | Optional | Free text for the broker, up to 8000 characters; stored as the application’s additional notes. |
| attachments | Optional | JSON array of documents already uploaded through the steps under “Attaching documents” below, up to 5 entries, each {url, filename, size, mimeType (optional), category}. category is one of "Existing policies", "Declarations pages", "Current applications", "Contract insurance requirements", "Certificates of insurance", "Security questionnaire or vendor-risk request", "Financial statements", "Loss runs", "Claims details", "Cap table or ownership summary", "Employee handbook", "Other". |
| requestReference | Optional | The AI- reference of an earlier broker review request for the same business; the two records are linked. |
| attribution | Optional | Captured by the page; direct callers may omit it. |
| formToken | Required | The token from GET https://oneparkrisk.com/api/ai-agents/token. |

Answer values: text: A string, up to 500 characters. email: A valid email address. tel: A phone number as a string, up to 500 characters. url: A URL as a string, up to 500 characters. number: A number, sent as a string or a JSON number. currency: An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. percent: A percentage, sent as a string or a JSON number. date: A date as a string; YYYY-MM-DD preferred. textarea: Free text, up to 8000 characters. radio: Exactly one of the published options, sent verbatim. select: Exactly one of the published options, sent verbatim. triage: Exactly one of the published options, sent verbatim; when the answer starts with "Yes" or is "Not sure", add the detailsKey with free text. checkbox-group: A JSON array of the published options, each sent verbatim. address: The full address as free text, up to 8000 characters; the headquarters address must name the state.

A question the business genuinely cannot answer takes {"unknown": true, "note": "…"} (note optional, up to 500 characters) instead of a value. Do not invent answers; a marked unknown is better than a guess, and the broker sees every unknown listed at the top of the notification.

What makes a body an application (otherwise 400 with code not_an_application and a missing list, and nothing is stored or emailed):

- At least one coverage id. When the only coverage is "not-sure", coverage_selection.primary_concern must describe what prompted the application in at least 40 characters.
- business_information.legal_business_name, a headquarters_address that names a US state or DC, industry or business_description, annual_revenue or total_employees, and primary_contact_email, each as a real answer (not an unknown).
- Every required question of every section the coverage selection and profile reveal, answered or explicitly marked {"unknown": true, "note": "…"}; conditional questions count only while their showWhen rule matches.
- Option values exactly as published (labels are the values); unknown section ids and field ids are rejected; sections and questions the selection hides are ignored.
- operatingStates (two-letter codes, at least one), submitter, and authorization with acknowledged: true.

Attaching documents (optional). When you already hold the business’s loss runs, current policies, declarations pages, financial statements, or other supporting files, upload each one first and reference it in the body, so the broker has them with the application instead of requesting them by email. The upload step is the same one the browser form uses, with the same limits: up to 5 files, 10 MB each.

1. POST a JSON body {"name": "<filename>", "size": <bytes>, "contentType": "<MIME type>"} to https://oneparkrisk.com/api/uploads/request-url (no token needed). The declared size must be at most 10 MB (10485760 bytes), the filename must end in one of .pdf, .doc, .docx, .xls, .xlsx, .ppt, .pptx, .txt, .png, .jpg, .jpeg, .gif, .webp, .heic, and the content type must start with one of application/pdf, application/msword, application/vnd.openxmlformats-officedocument, application/vnd.ms-excel, application/vnd.ms-powerpoint, text/plain, image/. A 201 carries uploadURL and objectPath; 400 means the metadata was refused.
2. PUT the file's bytes to uploadURL with the same Content-Type header, within 15 minutes of the 201. The bytes go straight to storage and never pass through the application endpoint.
3. In the application body, add one entry per file under attachments: {"url": "<objectPath>", "filename": "<name>", "size": <bytes>, "mimeType": "<MIME type, optional>", "category": "<one of the categories>"}. Up to 5 files per application, each referenced once. Categories: "Existing policies", "Declarations pages", "Current applications", "Contract insurance requirements", "Certificates of insurance", "Security questionnaire or vendor-risk request", "Financial statements", "Loss runs", "Claims details", "Cap table or ownership summary", "Employee handbook", "Other".
4. The server confirms every referenced upload exists and holds at most 10 MB before anything is stored; a missing, unfinished, or oversized upload is a 400 with code validation naming the attachments entry, and nothing is stored or emailed.

Responses: 201 saved, with applicationId, reference ("AP-" followed by 8 characters, each a digit or an upper-case letter other than I, L, O, and U, for example AP-7Q4K9XM2), completeness (percent, answeredRequired, totalRequired, the unknown list, and the advisor flags), attachments (each stored document’s filename, category, and size), acknowledgementEmail and notification (sent, failed, or unavailable). An identical retry with the same token returns 201 with replayed: true and the same reference. 400 with code validation lists malformed or unrecognized keys, including an attachments entry whose upload is missing or over the limit; 400 with code not_an_application lists what is missing under missing; 409 means the token was already used with different answers (fetch a new token); 429 means the token is invalid, expired, or the sender should wait.

After a 201: the authorized representative (and the follow-up inbox, when different) receives an acknowledgement email with the application reference. There is no link to click. A broker reads the application and follows up by email; the representative replies to that email to answer questions, or to withdraw the application if it was not authorized.

Filing an application does not bind coverage and does not guarantee carrier approval or a quote. A OnePark broker reads the application and follows up by email with questions, options, or the next step.

The questionnaire, section by section. Each section lists which coverage ids reveal it; “not-sure” reveals every coverage-gated section.

**Coverages of interest** (section id `coverage_selection`; appears in every application). Which lines should we put in front of carriers? The rest of the application adapts to what you select.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| primary_concern | What's driving this conversation? (Optional) | Optional | Free text, up to 8000 characters. A renewal date, a customer contract, an investor request — anything we should plan around. |

**Business information** (section id `business_information`; appears in every application). Tell us about the company being insured.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| legal_business_name | Legal business name | Required | A string, up to 500 characters. |
| dba | Doing business as (if different) | Optional | A string, up to 500 characters. |
| website | Website | Optional | A URL as a string, up to 500 characters. |
| year_founded | Year founded | Optional | A number, sent as a string or a JSON number. |
| corporate_structure | Corporate structure | Required | One of: Corporation \| Partnership \| Sole proprietorship \| Joint venture \| Limited liability company \| Limited liability partnership \| Professional association \| Professional corporation \| Trust \| Other |
| corporate_structure_other | Please describe the organization structure | Optional | Free text, up to 8000 characters. Only while corporate_structure is "Other". |
| headquarters_address | Headquarters address | Required | The full address as free text, up to 8000 characters; the headquarters address must name the state. |
| states_of_operation | Other states or countries of operation | Optional | Free text, up to 8000 characters. |
| industry | Industry / NAICS description | Required | A string, up to 500 characters. |
| business_description | Brief description of operations | Required | Free text, up to 8000 characters. |
| annual_revenue | Most recent annual revenue | Required | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| projected_revenue | Projected revenue next 12 months | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| total_employees | Total employees (W-2 + contractors) | Required | A number, sent as a string or a JSON number. |
| top_customer_concentration | Largest customer as % of revenue | Optional | A percentage, sent as a string or a JSON number. Used for advisor follow-up if any single customer exceeds 50%. |
| primary_contact_name | Primary contact name | Required | A string, up to 500 characters. |
| primary_contact_title | Primary contact title | Optional | A string, up to 500 characters. |
| primary_contact_email | Primary contact email | Required | A valid email address. |
| primary_contact_phone | Primary contact phone | Optional | A phone number as a string, up to 500 characters. |

**Eligibility acknowledgements** (section id `eligibility_acknowledgements`; appears in every application). Carriers ask these up front. They do not disqualify you on their own.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| eligibility_categories | Does the company operate in any of the following categories? | Required | Array of: Adult entertainment, gambling, or cannabis-related operations \| Cryptocurrency exchange or token issuance \| Crowdfunding platform \| Firearms manufacturing or distribution \| Payday lending or debt collection services \| Off-shore operations or sanctioned jurisdictions \| None of the above |
| eligibility_details | If selected above, please describe | Optional | Free text, up to 8000 characters. Only while eligibility_categories selects anything other than "None of the above". |

**Property portfolio & operations** (section id `real_estate_risk`; appears in every application; profile real-estate only). Asked on the Real Estate application. Approximate figures are fine — an advisor confirms details before anything goes to carriers.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| property_types | Which property types are in the portfolio? Select all that apply. | Required | Array of: Apartments / multifamily \| Office \| Retail \| Industrial / warehouse \| Mixed-use \| Hospitality / short-term rental \| Senior or student housing \| Vacant land or vacant buildings \| Other |
| location_count | Number of locations / buildings | Required | A number, sent as a string or a JSON number. |
| unit_count | Total number of units or tenant spaces (if applicable) | Optional | A number, sent as a string or a JSON number. |
| occupancy_profile | Occupancy profile | Required | One of: Fully owner-occupied \| Fully leased to tenants \| Mix of owner-occupied and leased \| Partially or fully vacant \| Not sure |
| vacancy_percent | Approximate vacancy rate across the portfolio (%) | Optional | A percentage, sent as a string or a JSON number. Vacancy above 20–30% changes which carriers can consider the risk. |
| total_insured_value | Total insured value across buildings and contents | Required | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| annual_rental_revenue | Annual rental / operating revenue | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| oldest_building_year | Year built of the oldest building (approximate) | Optional | A number, sent as a string or a JSON number. |
| major_systems_updated | Have roofs, wiring, plumbing, and heating been updated in the last 25 years across the portfolio? | Optional | One of: Yes \| No \| Not sure |
| catastrophe_exposures | Do any locations have the following exposures? Select all that apply. | Required | Array of: Coastal wind / named storm \| Flood zone (FEMA A or V) \| Wildfire-prone area \| Earthquake-prone area \| None of these apply \| Not sure |
| lender_or_lease_requirements | Do lenders or leases impose specific insurance requirements you must satisfy? | Optional | One of: Yes \| No \| Not sure Add "lender_or_lease_requirements_details" (free text) when the answer starts with Yes or is Not sure. |
| property_program_in_force | Do you currently have a property / liability program in force for these locations? | Required | One of: Yes \| No \| Not sure |
| property_program_carrier | Current carrier(s) and expiration date | Optional | A string, up to 500 characters. Only while property_program_in_force is "Yes". |
| property_losses_past_5_years | Any property or liability losses in the last 5 years? | Required | One of: Yes \| No \| Not sure Add "property_losses_past_5_years_details" (free text) when the answer starts with Yes or is Not sure. |
| real_estate_coverage_interests | Which coverages should we include in the program? Select all that apply. | Required | Array of: Commercial property \| General liability / premises liability \| Lessor's risk \| Umbrella / excess liability \| Flood or earthquake \| Equipment breakdown \| Ordinance or law \| Loss of rents / business income \| Environmental / pollution \| Not sure — please advise |

**Trades, projects & operations** (section id `construction_risk`; appears in every application; profile construction only). Asked on the Construction & Contractor application. Approximate figures are fine — an advisor confirms details before anything goes to carriers.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| trades_performed | Which trades do you perform? Select all that apply. | Required | Array of: General contractor / construction management \| Electrical \| Plumbing / HVAC / mechanical \| Roofing \| Framing / carpentry \| Concrete / masonry \| Excavation / grading / sitework \| Painting / drywall / finishes \| Landscaping \| Specialty or artisan trade \| Other |
| operations_description | Describe your typical operations and the work you self-perform | Required | Free text, up to 8000 characters. |
| project_mix | Project mix | Required | One of: Mostly residential \| Mostly commercial \| Mix of residential and commercial \| Public / government projects \| Not sure |
| new_vs_remodel | New construction vs. remodel / service work | Optional | One of: Mostly new construction (ground-up) \| Mostly remodel / renovation / service work \| Roughly even mix \| Not sure |
| typical_project_value | Typical project value | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| largest_project_value | Largest project value in the next 12 months | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| annual_revenue_construction | Annual revenue (most recent completed year) | Required | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| annual_payroll | Annual payroll (field and office) | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| field_employee_count | Number of field employees | Optional | A number, sent as a string or a JSON number. |
| uses_subcontractors | Do you use subcontractors? | Required | One of: Yes \| No \| Not sure |
| subcontracted_percent | Approximate percentage of work subcontracted (%) | Optional | A percentage, sent as a string or a JSON number. Only while uses_subcontractors is "Yes". |
| sub_agreements_in_place | Do you collect certificates of insurance and use written subcontracts with hold-harmless language? | Optional | One of: Yes \| No \| Not sure Only while uses_subcontractors is "Yes". |
| hazardous_operations | Do your operations include any of the following? Select all that apply. | Required | Array of: Roofing work \| Structural work above three stories \| Excavation deeper than 10 feet \| Demolition \| Work involving cranes \| Residential condominiums or tract housing \| None of these apply \| Not sure |
| owns_equipment_or_vehicles | Do you own contractor's equipment or business vehicles? | Optional | One of: Yes \| No \| Not sure |
| equipment_vehicle_values | Approximate total value of owned equipment and vehicles | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. Only while owns_equipment_or_vehicles is "Yes". |
| bonding_required | Do any of your projects require surety bonds? | Optional | One of: Yes \| No \| Not sure |
| design_or_pollution_exposure | Do you provide design services, or perform work with pollution exposure (tanks, remediation, hazardous materials)? | Optional | One of: Yes \| No \| Not sure Add "design_or_pollution_exposure_details" (free text) when the answer starts with Yes or is Not sure. |
| construction_program_in_force | Do you currently have a liability / workers' comp program in force? | Required | One of: Yes \| No \| Not sure |
| construction_program_carrier | Current carrier(s) and expiration date | Optional | A string, up to 500 characters. Only while construction_program_in_force is "Yes". |
| construction_losses_past_5_years | Any claims or losses in the last 5 years (including workers' comp)? | Required | One of: Yes \| No \| Not sure Add "construction_losses_past_5_years_details" (free text) when the answer starts with Yes or is Not sure. |
| construction_coverage_interests | Which coverages should we include in the program? Select all that apply. | Required | Array of: General liability \| Workers' compensation \| Commercial auto \| Builder's risk / installation floater \| Inland marine / contractor's equipment \| Umbrella / excess liability \| Contractor's pollution liability \| Contractor's professional liability \| Surety bonds \| Not sure — please advise |

**Cyber liability** (section id `cyber_liability`; appears in coverages cyber, tech-eo-with-cyber (or not-sure)). Asked when Cyber Liability or Tech E&O with Cyber is selected.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| cyber_in_force | Do you currently have a cyber policy in force? | Required | One of: Yes \| No \| Not sure |
| cyber_carrier | Current carrier and limit | Optional | A string, up to 500 characters. Only while cyber_in_force is "Yes". |
| cyber_renewal_date | Current policy renewal date | Optional | A date as a string; YYYY-MM-DD preferred. Only while cyber_in_force is "Yes". |
| sensitive_records_count | Approximate number of sensitive records held (PII / PHI / payment) | Optional | A number, sent as a string or a JSON number. Counts of 100,000+ are flagged for advisor review. |
| annual_cyber_revenue | Annual revenue from operations covered by this policy | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| security_controls | Which security controls are in place today? Select all that apply. | Required | Array of: Multi-factor authentication for remote network access \| Multi-factor authentication for email \| Multi-factor authentication for privileged accounts \| Endpoint detection and response (EDR) \| Email filtering and anti-phishing \| Encrypted backups stored offline or immutable \| Documented incident response plan \| Employee security awareness training \| Vulnerability or patch management program \| Vendor risk management program \| Penetration testing in the last 12 months \| None of the above |
| cyber_incidents | In the last 3 years, has the company experienced any of the following? Select all that apply. | Required | Array of: Cyber security incident, breach, or unauthorized access \| Ransomware or extortion event \| Privacy regulation inquiry, complaint, or proceeding \| Class action or demand involving privacy or data security \| Wire transfer fraud or business email compromise loss \| None of the above \| Not sure |
| cyber_incident_details | Please describe the incident(s) | Optional | Free text, up to 8000 characters. Only while cyber_incidents selects anything other than "None of the above", "Not sure". |
| cyber_cancelled_or_nonrenewed | Has any cyber insurer cancelled or non-renewed coverage in the last 36 months? | Required | One of: Yes, within the last 36 months \| Yes, within the last 24 months \| No \| Not sure Add "cyber_cancelled_or_nonrenewed_details" (free text) when the answer starts with Yes or is Not sure. |

**Cyber supplemental** (section id `cyber_supplemental`; appears in coverages cyber, tech-eo-with-cyber (or not-sure)). Additional underwriting questions for Cyber and Tech E&O with Cyber.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| uses_third_party_processors | Do you rely on third-party payment processors or hosted infrastructure? | Optional | One of: Yes \| No \| Not sure |
| third_party_processors_list | Which third parties? | Optional | Free text, up to 8000 characters. Only while uses_third_party_processors is "Yes". |
| wire_transfer_verification | Is dual-control wire transfer verification in place? | Optional | One of: Yes \| No \| Not sure |
| phishing_training_frequency | Phishing / security awareness training frequency | Optional | One of: Quarterly \| Annually \| Less than annually \| None |
| data_retention_policy | Documented data retention policy? | Optional | One of: Yes \| No \| Not sure |

**Tech E&O with Cyber** (section id `tech_eo_with_cyber`; appears in coverages tech-eo-with-cyber (or not-sure)). Asked when Tech E&O with Cyber is selected.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| tech_services_description | Describe the technology services or products you sell | Required | Free text, up to 8000 characters. |
| primary_revenue_source | What is your primary source of revenue? | Optional | One of: SaaS subscription \| Software license \| Professional services / consulting \| Managed services \| Hardware \| Marketplace / platform fees \| Other |
| uses_ai_ml | Do your products use AI or machine learning? | Optional | One of: Yes \| No \| Not sure |
| ai_ml_description | Describe the AI / ML use, including training data sources | Optional | Free text, up to 8000 characters. Only while uses_ai_ml is "Yes". |
| open_source_use | Do products incorporate open-source code? | Optional | One of: Yes \| No \| Not sure |
| ip_dispute_history | Any IP, trademark, or copyright disputes in the last 5 years? | Optional | One of: Yes \| No \| Not sure Add "ip_dispute_history_details" (free text) when the answer starts with Yes or is Not sure. |
| tech_eo_in_force | Do you have a Tech E&O / Professional Liability policy in force today? | Optional | One of: Yes \| No \| Not sure |
| tech_eo_carrier | Current carrier and limit | Optional | A string, up to 500 characters. Only while tech_eo_in_force is "Yes". |

**Miscellaneous E&O** (section id `misc_eo`; appears in coverages misc-eo (or not-sure)). Asked when Miscellaneous E&O is selected.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| professional_services_description | Describe the professional services rendered | Required | Free text, up to 8000 characters. |
| fee_structure | How are fees structured? | Optional | A string, up to 500 characters. |
| engagement_letters_used | Are written engagement letters used with all clients? | Optional | One of: Yes \| No \| Not sure |
| subcontractors_used | Are subcontractors used to deliver services? | Optional | One of: Yes \| No \| Not sure |
| misc_eo_in_force | Do you have an E&O policy in force today? | Optional | One of: Yes \| No \| Not sure |
| misc_eo_claims_5yr | Any E&O claims, demands, or known circumstances in the last 5 years? | Optional | One of: Yes \| No \| Not sure Add "misc_eo_claims_5yr_details" (free text) when the answer starts with Yes or is Not sure. |

**Miscellaneous E&O supplemental** (section id `misc_eo_supplemental`; appears in coverages misc-eo (or not-sure)).

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| international_clients_pct | Approximate % of revenue from international clients | Optional | A percentage, sent as a string or a JSON number. |
| largest_engagement_value | Largest single engagement value in the last 12 months | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| regulated_industry_clients | Do you serve clients in regulated industries (healthcare, finance, government)? | Optional | One of: Yes \| No \| Not sure |

**Management liability** (section id `management_liability`; appears in coverages directors-officers, epli, fiduciary, crime, kidnap-ransom (or not-sure)). Asked when D&O, EPLI, Fiduciary, Crime, or Kidnap & Ransom is selected.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| desired_effective_date | Desired coverage effective date | Required | A date as a string; YYYY-MM-DD preferred. |
| desired_expiration_date | Desired expiration date (if known) | Optional | A date as a string; YYYY-MM-DD preferred. |
| merger_acquisition_history | Any merger, acquisition, consolidation, or similar transaction in the past 24 months or planned in the next 12? | Required | One of: Yes, within the past 24 months \| Yes, within the past 18 months \| Yes, within the past 12 months \| Yes, within the next 12 months \| No \| Not sure Add "merger_acquisition_history_details" (free text) when the answer starts with Yes or is Not sure. |
| financial_restructuring_history | Any financial restructuring, reorganization, bankruptcy filing, or debt-service discussions in the past 24 months or anticipated in the next 12? | Required | One of: Yes, within the past 24 months \| Yes, within the past 18 months \| Yes, within the past 12 months \| Yes, within the next 12 months \| No \| Not sure Add "financial_restructuring_history_details" (free text) when the answer starts with Yes or is Not sure. |
| claims_investigations_5yr | In the last 5 years, has the applicant or any subsidiary experienced any of the following? Select all that apply. | Required | Array of: Notice of claims or potential claims \| Losses or expenses that may fall within the scope of requested coverage \| Formal or informal civil investigation, inquiry, or proceeding \| Formal or informal criminal investigation, inquiry, or proceeding \| Formal or informal administrative investigation, inquiry, or proceeding \| State or federal regulatory agency inquiry or proceeding \| None of the above \| Not sure |
| claims_investigations_details | Please briefly describe the matter(s) | Optional | Free text, up to 8000 characters. Only while claims_investigations_5yr selects anything other than "None of the above", "Not sure". |
| potential_claims_awareness | Is anyone aware of any fact, circumstance, or situation that may give rise to a claim? | Required | One of: Yes \| No \| Not sure Add "potential_claims_awareness_details" (free text) when the answer starts with Yes or is Not sure. |
| prior_cancellation_36mo | Has any insurer cancelled or refused to renew any D&O, EPLI, fiduciary, crime, K&R, cyber, or similar insurance within the past 36 months? | Required | One of: Yes, within the last 36 months \| Yes, within the last 24 months \| No \| Not sure Add "prior_cancellation_36mo_details" (free text) when the answer starts with Yes or is Not sure. |
| ebit | Earnings before interest and taxes (most recent FY) | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. You may upload financial statements instead if easier. |
| net_income | Net income after taxes | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| current_liabilities | Current liabilities | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| long_term_debt | Long-term debt | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| total_liabilities | Total liabilities | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| current_assets | Current assets | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| total_assets | Total assets | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| cash_flow_from_operations | Cash flow from operations | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |

**Private D&O** (section id `private_d_and_o`; appears in coverages directors-officers (or not-sure)). Asked when Directors & Officers coverage is selected.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| do_in_force | Do you currently have a D&O policy in force? | Required | One of: Yes \| No \| Not sure |
| private_placement_history | Any private placement or third-party investment in the past 24 months or planned in the next 18? | Required | One of: Yes, within the past 24 months \| Yes, within the past 18 months \| Yes, within the past 12 months \| Yes, within the next 12 months \| Yes, within the next 18 months \| No \| Not sure Add "private_placement_history_details" (free text) when the answer starts with Yes or is Not sure. |
| publicly_traded_or_planned | Publicly traded today or anticipating becoming publicly traded? | Required | One of: Yes, within the past 24 months \| Yes, currently \| Yes, within the next 12 months \| Yes, within the next 18 months \| No \| Not sure Add "publicly_traded_or_planned_details" (free text) when the answer starts with Yes or is Not sure. |
| debt_due_18mo | Any debt coming due in the next 18 months? | Optional | One of: Yes \| No \| Not sure |
| covenant_breach | Any breach or violation of debt covenants or material contracts in the past 18 months or expected in the next 12? | Optional | One of: Yes, within the past 18 months \| Yes, within the past 12 months \| Yes, currently \| Yes, within the next 12 months \| No \| Not sure Add "covenant_breach_details" (free text) when the answer starts with Yes or is Not sure. |
| esop_in_place | Does the organization have an Employee Stock Ownership Plan? | Optional | One of: Yes \| No \| Not sure |
| controlled_by_other_entity | Does another entity own or control the organization? | Optional | One of: Yes \| No \| Not sure Add "controlled_by_other_entity_details" (free text) when the answer starts with Yes or is Not sure. |
| directors_officers_ownership_pct | What % of the organization is owned by directors and/or officers? | Optional | A percentage, sent as a string or a JSON number. |
| ownership_change_history | Any change in ownership, asset transfers, or distributions in the past 36 months or expected in the next 12? | Optional | One of: Yes, within the past 36 months \| Yes, within the past 24 months \| Yes, within the past 12 months \| Yes, within the next 12 months \| No \| Not sure Add "ownership_change_history_details" (free text) when the answer starts with Yes or is Not sure. |
| senior_management_change | Change in senior management or board in the past 12 months or anticipated in the next 12? | Optional | One of: Yes, within the past 12 months \| Yes, within the next 12 months \| No \| Not sure Add "senior_management_change_details" (free text) when the answer starts with Yes or is Not sure. |
| operations_change | Change in operations in the past 12 months? | Optional | One of: Yes \| No \| Not sure Add "operations_change_details" (free text) when the answer starts with Yes or is Not sure. |
| government_revenue_pct | What % of revenue comes from government sources? | Optional | A percentage, sent as a string or a JSON number. |

**Employment Practices Liability** (section id `epli`; appears in coverages epli (or not-sure)). Asked when EPLI is selected.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| epli_in_force | Do you currently have an EPLI policy in force? | Required | One of: Yes \| No \| Not sure |
| eeoc_proceeding | Has the company been involved in an EEOC or similar administrative proceeding? | Required | One of: Yes, within the last 3 years \| Yes, within the last 5 years \| No \| Not sure Add "eeoc_proceeding_details" (free text) when the answer starts with Yes or is Not sure. |
| ft_employees_excl_union | Full-time employees, excluding union employees | Required | A number, sent as a string or a JSON number. |
| ft_union_employees | Union employees, full-time | Optional | A number, sent as a string or a JSON number. |
| foreign_employees | Foreign employees | Optional | A number, sent as a string or a JSON number. |
| volunteers | Volunteers | Optional | A number, sent as a string or a JSON number. |
| pt_employees_excl_union | Part-time employees, excluding union employees | Optional | A number, sent as a string or a JSON number. |
| pt_union_employees | Union employees, part-time | Optional | A number, sent as a string or a JSON number. |
| independent_contractors | Independent contractors | Optional | A number, sent as a string or a JSON number. |
| ca_employees | Does the company have employees in California? | Required | One of: Yes \| No \| Not sure |
| high_comp_count | Number of employees with total compensation over $150,000 | Optional | A number, sent as a string or a JSON number. |
| employment_application_used | Does the company have an employment application? | Optional | One of: Yes \| No \| Not sure |
| employee_handbook_distributed | Does the company have an employee handbook and distribute it to all employees? | Optional | One of: Yes \| No \| Not sure |
| hr_department | Does the company have an HR department? | Optional | One of: Yes \| No \| Not sure |
| written_policies | Which written policies, guidelines, procedures, or training does the company have? Select all that apply. | Required | Array of: Anti-harassment, including sexual harassment \| Anti-discrimination \| Equal employment opportunity \| Employee at-will \| None of the above \| Not sure |
| layoff_history | Any downsizing, layoffs, RIF, or office closing in the past 18 months or anticipated in the next 12? | Required | One of: Yes, in the past 18 months \| Yes, in the past 12 months \| Yes, in the next 12 months \| No \| Not sure Add "layoff_history_details" (free text) when the answer starts with Yes or is Not sure. |

**Management liability supplemental** (section id `management_liability_supplemental`; appears in coverages directors-officers, epli, fiduciary, crime, kidnap-ransom (or not-sure)). Additional underwriting questions. Skip any that aren't applicable.

| Field id | Question | Required | Answer |
| --- | --- | --- | --- |
| executive_hires_from_competitor | Hired (or expecting to hire) more than one individual from a single competitor in the past or next year, outside of M&A? | Optional | One of: Yes \| No \| Not sure Add "executive_hires_from_competitor_details" (free text) when the answer starts with Yes or is Not sure. |
| total_capital_raised | Total capital raised to date | Optional | An amount in US dollars, sent as a string (for example "2400000" or "$2.4M") or a JSON number. |
| family_shareholder_pct | % of shares held by shareholders related by family to a director/officer (but not themselves D/O) | Optional | A percentage, sent as a string or a JSON number. |
| do_shareholder_pct | % of shares held by directors, officers, or entities with direct board representation | Optional | A percentage, sent as a string or a JSON number. |
| shareholder_count | How many individuals or entities own shares in the company? | Optional | A number, sent as a string or a JSON number. |
| non_do_20pct_owner | Any individual/entity with more than 20% ownership who is not a director or officer? | Optional | One of: Yes \| No \| Not sure Add "non_do_20pct_owner_details" (free text) when the answer starts with Yes or is Not sure. |
| executive_terminations | Any terminations of executive officers in the past 12 months or anticipated in the next 12? | Optional | One of: Yes \| No \| Not sure Add "executive_terminations_details" (free text) when the answer starts with Yes or is Not sure. |
| nonprofit_to_forprofit_conversion | Converted (or planning to convert) from not-for-profit to for-profit? | Optional | One of: Yes, in the past 18 months \| Yes, in the next 12 months \| No \| Not sure Add "nonprofit_to_forprofit_conversion_details" (free text) when the answer starts with Yes or is Not sure. |
| total_locations | Total locations | Optional | A number, sent as a string or a JSON number. |
| top_states_by_employees | Top three states by employee count | Optional | A string, up to 500 characters. Rows keyed by state, employee_count. |
| employed_lawyers_count | How many employed lawyers does the company have? | Optional | A number, sent as a string or a JSON number. |
| market_share_over_20pct | Does the company control more than 20% market share in any geography? | Optional | One of: Yes \| No \| Not sure |
| non_board_10pct_shareholders | Any shareholders without board representation who own 10% or more of the company? | Optional | One of: Yes \| No \| Not sure |
| flsa_classification_review | Has the company reviewed FLSA exempt/non-exempt classifications in the last 12 months? | Optional | One of: Yes \| No \| Not sure |
| earnout_obligation_500k | Any earn-out or contingent payment obligation in the next 24 months exceeding $500,000? | Optional | One of: Yes \| No \| Not sure Add "earnout_obligation_500k_details" (free text) when the answer starts with Yes or is Not sure. |
| litigation_history_3yr | Litigation, arbitration, administrative or criminal proceedings against any insured person in the last 3 years? | Optional | One of: Yes \| No \| Not sure Add "litigation_history_3yr_details" (free text) when the answer starts with Yes or is Not sure. |
| commercial_crime_losses_3yr | Any commercial crime losses in the last 3 years? | Optional | One of: Yes \| No \| Not sure Add "commercial_crime_losses_3yr_details" (free text) when the answer starts with Yes or is Not sure. |
| financial_flags | Regarding the company's financials, select all that apply | Optional | Array of: Long-term liabilities exceed 75% of total assets \| More than 50% of total long-term liabilities will mature within the next 18 months \| In any year within the last five years, the company derived more than 10% of revenue or funding from federal, state, local, foreign, or quasi-governmental sources \| None of these apply \| Not sure |
| ownership_flags | Select all that apply (ownership / bankruptcy) | Optional | Array of: Any person or entity who owns or controls 50% or more of the outstanding securities anticipates filing in the next 12 months for personal or corporate bankruptcy \| Any person or entity who owns or controls 50% or more of the outstanding securities has filed within the last 24 months for personal or corporate bankruptcy \| More than 10% of the outstanding securities, voting rights, or controlling interests are directly or indirectly owned by a person or entity not under the control of a current or former director or officer \| None of these apply \| Not sure |
| operations_flags | Does the company directly or indirectly do any of the following? Select all that apply. | Optional | Array of: Render services for others for a fee or other consideration \| Act as a general partner, manager, or managing member in any partnership or LLC \| Have any insurance operations \| Perform, engage in, facilitate, or promote downloading, sharing, or streaming copyrighted media content \| Use automatic telephone dialing, unsolicited mobile phone texting, multiple-recipient email transmission, or a similar communication system in advertising, marketing, or sales \| None of these apply \| Not sure |
| manufactures_or_sells_goods | Does the company manufacture, produce, package, sell, market, or distribute goods or products? | Optional | One of: Yes \| No \| Not sure |
| officer_turnover_25pct | Have more than 25% of officers or management voluntarily left or been terminated in the last 18 months? | Optional | One of: Yes \| No \| Not sure Add "officer_turnover_25pct_details" (free text) when the answer starts with Yes or is Not sure. |

## Confirm the inbox and business authorization

Complete the inbox-verification step using the access and permissions available to you.

Inbox verification confirms where correspondence should go. The confirmation email contains a request-specific link that expires; opening the link shows a confirmation page, and an explicit “Confirm email address” action completes the step.

The business’s authorized representative may also need to confirm that OnePark can shop for the business and communicate with the designated recipients. The authorization email contains its own link and an explicit “Authorize insurance shopping” action, alongside “Correct details” and “Decline request”.

These are separate decisions. Neither approves an insurance purchase.

## What happens after submission

The receipt shows the request reference and the current status. The follow-up inbox receives a confirmation email with a request-specific link; the business’s authorized representative receives an authorization email with its own link. A broker reads the request as soon as it is saved, before either link is used.

We will review the submission and may ask for additional information.

Our goal is a first substantive response by email in one business day or less.

This is not a promise that quotes, underwriting, or coverage will be completed within that period.

Reply in the existing request conversation and preserve the request reference.

When questions are numbered, answer using the same numbering.

Distinguish confirmed facts, estimates, unknowns, and answers requiring business confirmation.

## Request statuses

Every email from OnePark states the current status and the next action. The statuses used throughout the process are:

| Status | Meaning |
| --- | --- |
| Email confirmation needed | The request exists; the correspondence inbox needs verification. |
| Business authorization needed | Shopping authorization or recipient approval is outstanding. |
| Broker review | OnePark is reviewing the request. |
| Information needed | A specific answer or document is outstanding. |
| Shopping coverage | Appropriate market submissions have occurred. |
| Options ready | Actual quotes or indications are available. |
| Approval needed | The business must approve a specific next step. |
| Bind request submitted | Binding has been requested; confirmation is pending. |
| Coverage bound | Binding has been confirmed, with effective terms and any conditions identified. |
| Policy delivered | Final policy documents have been supplied. |
| Unable to place / withdrawn / closed | The request is no longer active. OnePark explains the reason and any available next action. |

The original submission time is recorded once and never reset by confirmation steps.

## Documents

Use the secure links supplied when sensitive documents are requested.

Identify existing policies, contracts, or other relevant documents even if they are not available at the time of the first submission.

When filing the complete application in one call, documents you already hold can travel with it: see “Attaching documents” under Application in one call.

## Review the available options

Help the business review the broker’s actual options and explanation.

Include:

- Insurer.
- Coverage and limits.
- Deductibles or retentions.
- Premium and disclosed charges.
- Proposed dates.
- Important exclusions or conditions.
- Remaining requirements.
- Quote expiration.
- Relevant documents.

Do not treat a preliminary indication as a confirmed policy.

## Purchase approval and coverage confirmation

The authorized business representative approves the specific coverage purchase and completes required attestations, signatures, and payment steps.

OnePark will confirm when coverage has been bound and identify the applicable effective date, terms, and any remaining conditions.

Submitting information, verifying an inbox, selecting an option, or making a payment does not by itself establish that coverage is bound.

## If you cannot complete a step

If you cannot browse, submit the form, or access email, give the business contact:

- The relevant OnePark link.
- The information you have prepared.
- The request reference, if already submitted.
- The exact remaining action.

Do not claim to have completed a step you could not perform.

## Corrections and duplicate submissions

Use the existing request reference when adding information or correcting the request.

Use the resend and correct-email controls on the receipt page when appropriate, or call the same two endpoints directly as described under the form field reference above. Correcting the follow-up address sends a new confirmation email and requires the new inbox to be confirmed.

Do not create a duplicate request because an email is delayed.

For additional coverage within the same shopping engagement, reply to the existing conversation and ask the broker to include it.

## Supported workflow

The supported process is:

- Web form for the initial request (or the Business Application form when the answers are ready).
- Email for confirmation, questions, answers, recommendations, and coordination.
- Secure links for documents, signatures, and payment when needed.

No MCP server, API integration, or developer setup is required. An AI agent or assistant that can browse the web uses the same forms a person does: submit the broker review request or the Business Application on this site, and OnePark’s brokers send follow-up questions, available quotes, and next steps by email; reply by email to keep the process moving. The JSON endpoints are optional, for agents that prefer them.

Use only the capabilities actually available to you and authorized by the business.

## What a submission does not do

Submitting a request does not bind coverage and does not guarantee carrier approval or a quote. A OnePark broker will follow up by email with questions, options, or the next step.

Submitting a request does not purchase or bind insurance. Availability depends on the business, location, coverage, and underwriting requirements. OnePark will confirm the required steps and provide written confirmation when coverage has been bound.