Azimuth Sightline

Policy Review Instrument · Sightline Standard

● Live · Compass-Connected

Why “Sightline”?

A sightline is the navigator’s unobstructed line from eye to mark — nothing in the way, nothing assumed, just what’s actually there. Azimuth Sightline reads a policy the same way: straight through the declarations, endorsements, and schedules to what the coverage actually says — deductibles normalized to dollars, the endorsements that cost money flagged, and never a guessed value where a verified one belongs.

Take the sight — drop the policy here

Dec page, full policy, endorsement schedule, SOV — drop what you have. Sightline reads the declarations right here in your browser and fills the fields below. Confirm what it sighted, then decide: start a file, or review only.

Drop the policy PDF here — or click to choose
PDF / images · up to ~20 MB per file · nothing leaves your device until you choose

Named insured

Carrier

Property / loss address

State (2-letter)

Policy number

Policy period — effective

Policy period — expiration

Building / Coverage A limit

AOP deductible

Wind / Hail deductible

Claim # (if the carrier issued one)

Date of loss

Peril

Start the file creates the claim in Claim Compass — register row, all 14 stages, Command Deck queue, hourly watch — and files the policy to it. Review only files the policy to the Policy Reviews inbox for the Sightline reading, no claim created.

The public sight — lead engine

Policyholders can run their own policy through the free Sightline Policy Check — they drop the policy, get an automated review downloaded straight to their device (“This is an automated review. Still talk to your public adjuster.”), and every drop logs to the backend’s Sightline Intake tab with the policy filed to Drive and an email ping to Ron. Share the link anywhere: azimuthapps.com/tools/sightline-check.html

What the reading covers

The full Azimuth Sightline standard: TIV built correctly (building + BPP, rents excluded, source cited) · cost per $100 of value cross-checked against the printed rate · both deductibles captured separately — the highest applicable wind/hail (normalized from % to dollars, minimums noted) and the peril deductible labeled with its peril · per-building / per-coverage deductible clauses · admitted vs. surplus lines · towers kept to one row per risk with every layer’s carrier, limit, and attachment · and the coverage-quality flags that cost money: cosmetic damage restrictions (and how far they actually reach), ACV roof endorsements, and roof-surface exclusions.

Data discipline is the backbone: a confirmed zero is written as 0% — that’s a finding, usually the recovery argument. An unknown is a labeled REVIEW with its reason. Nothing is ever guessed into a cell.

The peril decides the reading. Selecting a peril above doesn’t just label the file — it selects the rule set that runs and suppresses the schedules that have nothing to do with the loss. A hail file does not carry an earthquake paragraph.

Peril lens	Checks that run
Wind and hail	11 — cosmetic restriction reach, ACV roof, roof-surface exclusion, matching, RFG→DMO, and the wind/hail deductible normalized to dollars
Hurricane / named storm	11 — the wind and hail set, read against the named-storm trigger and its own deductible
Water — non-weather	6 — sudden-and-accidental wording, seepage exclusion, the repair-of-the-cause carve-out
Fire	6 — smoke and soot reach, ordinance or law, the standard fire policy question
Freeze / burst pipe	4 — heat-maintenance and vacancy conditions, the ones that decide the claim silently
General review	6 — all-perils pre-loss reading: every deductible and sublimit in the policy

Five distinct rule sets, 33 checks. Every individual check returns one of four plain-English flags — the board reads a finding without decoding a number. The file as a whole carries the Red / Yellow / Green opportunity score on the internal document.

Needs work Open item In your favour For awareness

The state authority packs

Sightline reads a policy in any state. What is built state by state is the authority pack — the statutes, regulations and bulletins the review actually cites, each one read to primary source and quoted verbatim. A review never cites a state it has not been built for.

State	Pack status
Illinois	48 of 55 fields established — 44 verified verbatim to statute or regulation and 4 verified absent (confirming a state has no such rule is itself a finding, and often the argument). 6 fields still in research, 1 flagged do-not-assert.
In build	The 55-field checklist is the same in every state, so each new pack is a research run, not a rebuild. Packs are added in the order the work demands them.

The do-not-assert list is the point. Where the law is genuinely unsettled, the review says so and names the open question — rather than asserting a rule that a carrier’s counsel can knock down. A cite that cannot be defended costs more than a gap that was disclosed.

What ships — two documents from one reading

Shared — the board’s copy

What the policy pays, in plain language
Deductible and sublimit schedules, every figure cited to the page it was read from
Per-unit deductible allocation — what the association’s deductible actually costs each unit owner
Who-can-do-what matrix — association, unit owner, management, adjuster: who may do what, and who may not
Duties in the event of loss, with the deadline for each one
Inspection evidence and the first-mover position
Association and board law for the governing state
Open items, next steps, and the bottom line

Internal — never leaves the office

The Sightline opportunity score — Red / Yellow / Green, with the reason it sits where it sits and exactly what would move it
The coverage position and how far it can be pushed
The review ledger — every finding and how it was verified
The state primer for the governing law
Provenance for every figure on the shared document

The section gate

15 required sections on the shared document, 10 on the internal one
The build fails if any section is missing — a review cannot ship incomplete because it happened to look finished

Build discipline: 48 standing rulings govern how a Sightline document is assembled — each one written after a real defect was caught in a document that was about to go to a board. No finding travels without its verification. No figure appears without the document and line it came from.

How the full reading runs

Drop the policy above — start the file or file it for review. Either way it lands in Drive, named and claimed.

Open Claude and say: “Run the Sightline on [insured name]” — Claude reads the policy against the Sightline standard (the one-tap prompt above appears after your drop). The deployment interview runs first: peril, type of insured, pre- or post-loss, governing state, how the deductible applies and who provided the documents. Nothing is inferred from the file names.

Two documents save back to the claim’s Drive folder — the shared board copy and the internal position, which carries the Red/Yellow/Green opportunity score, the deductible & sublimit schedules with citations, the coverage-quality flags and the recommended next steps. Each document is gated against its required section list before it is written.

AZIMUTH SIGHTLINE (POLICY REVIEW STANDARD) IS A PROPRIETARY METHODOLOGY OF AZIMUTH RISK GROUP, LLC, LICENSED TO AZIMUTH OPERATING ENTITIES. OUTPUT IS TECHNICAL POLICY ANALYSIS FOR LICENSED-ADJUSTER REVIEW — NOT LEGAL ADVICE AND NOT A FINAL COVERAGE DETERMINATION.