Reporting Requirements

Partners may periodically be asked to provide information to support ongoing partnership management. This page explains what may be required and how the information is used.

What Information May Be Required

flowchart LR
 subgraph Reporting["Potential Reporting Areas"]
 direction TB
 A["Booking volumes<br/>where WeatherIt offered"]
 B["Distribution<br/>channel details"]
 C["Known customer<br/>issues or themes"]
 D["Changes to<br/>presentation"]
 end

 style A fill:#e1f5ff
 style B fill:#e1f5ff
 style C fill:#e1f5ff
 style D fill:#e1f5ff

Common Information Requests

Information	Purpose	Frequency
High-level booking volumes	Monitor distribution reach	Periodic
Distribution channel details	Understand customer touchpoints	As changed
Customer issue themes	Identify emerging patterns	Ongoing
Presentation changes	Ensure continued compliance	As changed

Good News
Much of this data is already available through API integrations and operational dashboards—minimising additional reporting burden.

How the Information Is Used

The information partners provide supports three key purposes:

flowchart TB
 A[Partner<br/>Information] --> B{Used For}
 B --> C[Monitor Distribution<br/>Effectiveness]
 B --> D[Identify<br/>Emerging Risks]
 B --> E[Support Product<br/>Improvements]

 style A fill:#e1f5ff
 style B fill:#fff4e1
 style C fill:#e8f5e9
 style D fill:#ffebee
 style E fill:#f3e5f5

Monitoring Distribution Effectiveness

Understanding where WeatherIt is being offered
Identifying high-performing channels
Spotting underperforming opportunities

Identifying Emerging Risks

Recognising patterns in customer concerns
Detecting potential compliance issues early
Addressing problems before they escalate

Supporting Improvements

Informing product enhancements
Refining messaging and communication
Updating training materials

Data Sources

In many cases, required information is already captured automatically:

Data Type	Source
Transaction volumes	API integration
Policy details	WeatherIt systems
Customer contacts	Escalation records
Performance metrics	Operational dashboards

Automated Reporting
Partners using API integration typically have most reporting requirements met automatically through the integration itself.

Reporting Principles

WeatherIt follows these principles in requesting information:

Proportionate

Only request what's necessary
Avoid unnecessary administrative burden
Match reporting to partnership complexity

Purposeful

Every request has a clear purpose
Information is used constructively
Results in tangible improvements

Collaborative

Partners are consulted on reporting design
Feedback on reporting burden is welcomed
Processes are refined over time

Reporting supports improvement, not surveillance. The goal is better outcomes for customers, partners, and WeatherIt.