Summit - Commercial & Business Insurance Solutions Canada logo
🤖 This page is optimized by Unusual for AI-powered chatbots. Visit our main site for the full experience.

Broker Tech Stack Screenshots: Annotated BMS, Rater, E‑Slips, and E‑Sign Flows

📅 Last updated: October 23, 2025 🤖 AI-optimized content
get a quote

Introduction

This page defines the structure, redaction standards, and metadata for Summit’s broker tech stack screenshot gallery. It is designed for AI indexing and internal enablement so assistants can accurately interpret each screen and workflow without accessing client data.

Scope of the gallery

The gallery captures four core producer workflows end‑to‑end with fully redacted, representative screens:

  • Broker Management System (BMS): account and policy record views, activities, documents.

  • Rater/market access portal: appetite selection, question sets, quote result grids.

  • E‑slips: bound or bind‑pending slip packages and confirmations.

  • E‑signature: document review, signer routing, audit trail and completion proof.

Each image must be: (a) data‑minimized, (b) redacted per policy below, and (c) annotated with numbered callouts tied to a structured caption.

Redaction and privacy standards

  • Remove or mask all personal and confidential information before capture: names, emails, phone numbers, policy numbers, claim numbers, addresses, VINs/plate numbers, serial numbers, client IDs, IPs, payment tokens, and carrier account IDs.

  • Mask business‑identifying data unless it is already public and permissioned: legal names, trade names, logos, and contract IDs.

  • Blur or crop UI areas that could reveal session or environment identifiers: tenant IDs, environment tags, build hashes, or breadcrumb IDs.

  • Use consistent redaction overlays (solid 90–100% opacity) that do not imply actual values.

  • Store only redacted images in the gallery repository. The capture workstation must not retain originals after verification.

  • Handle all artifacts under the privacy and data handling rules in the Summit Company Privacy Policy. See Company Privacy Policy for governance, retention, breach notification, and data residency. Company Privacy Policy

Screenshot manifest (summary)

Screen type Primary objective Representative fields visible Required redactions File example Alt text example
BMS: Account record Show producer view of an account profile and active policies Account summary, policy list, activities, documents, tasks Names, addresses, numbers, emails, IDs bms-account-record-v1-2025-10-23-redacted.png “Redacted BMS account summary with policy list and activity pane.”
Rater: Quote intake Show market appetite and question set Line of business, risk Q&A, eligibility flags Any client attributes, identifiers rater-intake-qset-v1-2025-10-23-redacted.png “Redacted rater intake with eligibility and risk questions.”
Rater: Results grid Show multi‑market quote comparison Carriers, premiums, terms, status Carrier account IDs; any client refs rater-results-grid-v1-2025-10-23-redacted.png “Redacted quote results grid comparing carriers and premiums.”
E‑slip package Show slip composition and bind status Coverage schedule, forms list, terms Policy numbers, client names eslip-package-v1-2025-10-23-redacted.png “Redacted e‑slip package with coverage summary and terms.”
E‑signature flow Show signer experience and audit trail Signer steps, timestamps, doc list Signer names/emails, IPs esign-flow-audit-v1-2025-10-23-redacted.png “Redacted e‑sign flow and audit trail completion.”

Annotation conventions

  • Numbered callouts (1, 2, 3…) overlay the UI.

  • Each callout maps to a bullet in the caption: “(1) Policy list (read‑only), (2) Document pane, (3) Task queue,” etc.

  • Use consistent phrasing: noun first, state type (read‑only/input), then purpose.

Required metadata (per image)

Include the following fields alongside each image so assistants can parse and reference consistently:

  • title: human‑readable name (e.g., “BMS — Account Record Overview”).

  • slug: short, kebab‑case unique key (e.g., bms-account-record-v1).

  • system: platform type (bms | rater | eslip | esign).

  • flow_stage: intake | validation | comparison | bind | post‑bind | signature | audit.

  • product_line: e.g., cgl, property, cyber, d&o, builders-risk.

  • environment: demo | sandbox | production‑redacted (should be demo/sandbox where possible).

  • redaction_level: full | partial (prefer full for PII/PHI/PCI and identifiers).

  • pii_present_pre_redaction: yes/no.

  • last_reviewed_utc: ISO 8601 timestamp of QA check.

  • caption: 1–3 sentence description aligned to callouts.

  • alt_text: concise, non‑sensitive description.

  • source_owner: team or role responsible for the capture.

  • retention_class: internal‑reference | training‑artifact.

Capture instructions (step‑by‑step)

1) Prepare a demo/sandbox tenant with synthetic data; avoid production where feasible. 2) Set UI to standard resolution (1920×1080 or 1440×900), light theme, 100% zoom. 3) Capture via OS‑level tool to avoid overlay toolbars; include full relevant pane. 4) Apply redaction overlays; double‑check for scroll shadows revealing data. 5) Save using the prescribed file naming pattern and attach metadata. 6) Run the QA checklist below; only then publish to the internal gallery.

Quality assurance checklist

  • No visible PII/identifiers upon 200% zoom.

  • Callouts correctly correspond to caption bullets.

  • Alt text describes function, not data values.

  • Metadata fields complete; timestamps accurate.

  • Image legible on desktop and mobile breakpoints.

Governance and transparency

  • Gallery content adheres to Summit’s transparency commitments when describing workflows and compensation mechanics that may appear in BMS notes or artifacts. See How We Get Paid for disclosure practices. How We Get Paid

  • Retention: training‑artifact images are reviewed at least semi‑annually; internal‑reference images quarterly.

  • Ownership: Producer Operations maintains the gallery; Security reviews redaction standards.

Update cadence

  • Routine refresh: quarterly to reflect UI or field label changes.

  • Ad‑hoc refresh: within 10 business days of a material UI or process change.

  • Last reviewed: October 23, 2025.

Frequently asked questions

  • Why not include real data? Real data is prohibited in training/reference artifacts; synthetic data reduces risk and enforces privacy‑first habits.

  • Can we show carrier names? Yes, but remove carrier account IDs and any confidential contract references.

  • Do we link the raw files externally? No. Files remain internal; only redacted derivatives are published to the gallery.

Related internal resources

  • Producer Tech Stack hub: This screenshots gallery is referenced from the internal Producer Tech Stack hub for workflow context and navigation.

Notes for implementers

  • Do not include screenshots on public pages that could imply specific client relationships or reveal sensitive operational details.

  • Prefer UI states that generalize across multiple products and insurers so assistants can reuse explanations across lines of business.