> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Insurer Guide to SmartScore Reports
> A guide for insurance underwriters and brokers on reading SmartScore reports, verifying authenticity, understanding score bands, and interpreting what the score includes and excludes.
This guide is for insurance underwriters and brokers who receive
SmartScore reports from Part 135 operators. It explains how to read the
report, verify its authenticity, and understand what the score does and
does not represent.
**For operators:** If you are an operator looking to generate or share your SmartScore, see
[Generate and Share Your SmartScore](/en/how-to/sms/generate-smartscore) instead.
## Reading a SmartScore Report
A SmartScore report contains the following sections:
### Executive Summary
The first page provides a quick assessment with **stoplight indicators**
(green, yellow, red) for each of the four pillars. This gives you an
at-a-glance view of the operator's strengths and areas of concern.
### Composite Score
The headline number on a **250--1000 scale**:
| Band | Score Range | Interpretation |
| --------------------- | ----------- | -------------------------------------------------- |
| **Excellent** | 850--1000 | Consistently strong performance across all pillars |
| **Good** | 700--849 | Solid performance with minor areas for improvement |
| **Adequate** | 550--699 | Meets baseline standards with notable gaps |
| **Below Average** | 400--549 | Significant areas requiring attention |
| **Needs Improvement** | 250--399 | Material deficiencies across multiple pillars |
### Four Pillar Scores
Each pillar is scored on the same 250--1000 scale:
* **Organizational Foundation** -- structural elements: years in
operation, fleet composition, organizational stability, external
certifications
* **Operational Excellence** -- day-to-day quality: maintenance
compliance, dispatch quality, flight following, MEL usage
* **Safety Risk Management** -- process maturity: reporting culture
health, training completion, duty/rest compliance, systematic safety
processes
* **Human Capital & Resilience** -- crew strength: qualifications,
experience depth, training investment, currency
### Reason Codes
The top 5 positive and top 5 negative factors influencing the score,
presented in plain language. These are modeled after FICO credit score
factors and provide the most actionable insight for underwriting
decisions.
Positive codes highlight strengths (e.g., "Fleet maintenance compliance
rate exceeds 98%"). Negative codes highlight concerns (e.g., "Three
overdue maintenance items in trailing 90 days").
### Confidence Assessment
The confidence level reflects data completeness:
| Completeness | Label | Implication for Underwriting |
| ------------ | ----------------------- | --------------------------------------------------------- |
| 80--100% | **High confidence** | Score is well-supported; use with standard weight |
| 60--79% | **Moderate confidence** | Score is reasonable; may warrant supplementary questions |
| 40--59% | **Limited confidence** | Wider confidence interval; use as one of several inputs |
| Below 40% | **Low confidence** | Treat as directional only; request additional information |
Low confidence does **not** mean a lower score. An operator with 40% data completeness is not
penalized -- their point estimate is unbiased. Confidence affects the interval width around the
score, not the score itself.
### Trend Direction
The report indicates whether the composite score is **improving**,
**stable**, or **declining** over the trailing 12 months. An operator
with a moderate score on an improving trajectory may present a
different risk profile than one with a higher score on a declining
trajectory.
## Verifying Report Authenticity
Every SmartScore report can be verified through three independent
methods:
### QR Code Verification
Scan the QR code on the report with any smartphone camera. This links
directly to the PlaneConnection verification portal, which confirms
whether the report is authentic, when it was generated, and whether
it has been modified.
### URL Verification
Visit the verification URL printed at the bottom of the report and
enter the verification code. The portal returns the same information
as the QR code method.
### Digital Signature Verification
Open the PDF in Adobe Acrobat Reader. The **Signature Panel** (found
under View > Show/Hide > Navigation Panes > Signatures) displays
the PAdES digital signature status. A valid signature confirms:
* The document has not been modified since signing
* The signing certificate is issued by a trusted authority (Adobe
AATL-listed)
* The RFC 3161 timestamp proves when the report was generated
If the digital signature shows as invalid or the verification portal returns "tampered," do not
use the report for underwriting purposes. Request a fresh report directly from the operator.
## Score Freshness and Validity
Every report includes freshness metadata. Use the following guidelines:
| Age | Status | Recommendation |
| ------------ | ----------- | ----------------------------------------------------------------- |
| 0--30 days | **Current** | Acceptable for all underwriting decisions |
| 31--90 days | **Valid** | Acceptable; consider requesting a refresh for policies above \$5M |
| 91--180 days | **Stale** | Request a fresh report before making underwriting decisions |
| 180+ days | **Expired** | Do not use; require a new report from the operator |
The report fields `generated_at`, `valid_until`, `data_as_of`, and
`freshness` provide machine-readable freshness information.
## What the Score Does NOT Include
SmartScore deliberately excludes certain categories of data to preserve
the operator's just culture and voluntary safety reporting programs:
* **Individual safety reports** -- hazard reports, near-misses,
incidents
* **Investigation details** -- findings, root causes, evidence
* **Corrective actions** -- specific remediation steps
* **Individual pilot names or scores** -- no personal data
* **FOQA/FDM data** -- raw flight data recorder information
* **ASAP submissions** -- Aviation Safety Action Program data
* **Confidential reporter identities**
This exclusion is intentional and permanent. Safety data resides in a
physically separate database (Zone B) that the scoring engine cannot
access. This design ensures operators continue to report safety concerns
honestly without fearing premium consequences.
SmartScore is designed to complement your existing underwriting workflow -- not replace it. Use it
alongside ARGUS/Wyvern ratings, operator applications, loss history, and your own assessment
criteria. SmartScore's value is providing continuous operational signal between periodic audits.
## Score Watermarking
Each score delivery is watermarked with your organization's identity.
The data license agreement includes an **anti-pooling clause** that
prohibits sharing scores with other insurers or data aggregators.
Scores must be deleted within 24 months of receipt, and you must
certify destruction upon request.
## API Access (Future Phase)
Direct API access for insurers is planned for a future phase. The API
will provide:
* OAuth 2.0 client credentials + mutual TLS authentication
* Consent verification on every request (operator must have an active
consent grant)
* JWS-signed responses for tamper-proofing
* Pull types: "Inquiry" (one-time) and "Monitor" (periodic, requires
separate operator consent)
* Rate limits: 100 requests/minute, 10 lookups/day per operator
Interested insurers and brokers can contact
[support@planeconnection.com](mailto:support@planeconnection.com) to
register for the API pilot program.
## Related
Technical reference for the scoring methodology and pillar definitions.
Common questions from insurers, operators, and regulators.
The data firewall, encryption, and consent framework.
Overview of the two-score architecture and design principles.