Managing Changes Over Time

Businesses evolve. Systems change. New opportunities arise. When changes affect your WeatherIt distribution, early communication is essential.

Changes That Require Notification

Partners must notify WeatherIt if there are material changes to:

flowchart TB
 subgraph Changes["Notify WeatherIt About"]
 direction TB
 A["Booking<br/>Systems"]
 B["Sales<br/>Channels"]
 C["Customer Communication<br/>Methods"]
 D["Business Models<br/>Affecting Distribution"]
 end

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

Specific Examples

Change Type	Examples
Booking systems	New booking platform, system upgrade, migration
Sales channels	New website, app launch, call centre opening
Customer communications	New email templates, SMS notifications, in-app messaging
Business model	New product lines, market expansion, acquisition

Why Early Notification Matters

Early notification ensures:

flowchart LR
 A[Early<br/>Notification] --> B{Benefits}
 B --> C[Product Configuration<br/>Remains Accurate]
 B --> D[Customer Experience<br/>Stays Consistent]
 B --> E[Regulatory Obligations<br/>Are Satisfied]

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

Product Configuration

Trigger configurations align with your booking structure
Coverage windows match your event/booking timing
Location data flows correctly

Customer Experience

Customers see consistent information
Journeys work smoothly
No unexpected gaps or errors

Regulatory Compliance

Distribution practices stay within approved parameters
Marketing remains compliant
Governance requirements are met

Avoiding Surprises
Changes implemented without notification can cause operational surprises, trigger misalignment, and customer confusion. Early communication avoids these issues.

The Notification Process

When you're planning changes:

flowchart LR
 A[Change<br/>Planned] --> B[Notify<br/>WeatherIt]
 B --> C[Joint<br/>Assessment]
 C --> D[Adjustments<br/>Made]
 D --> E[Change<br/>Implemented]

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

Step-by-Step

Step	Action
1	Identify changes that may affect WeatherIt distribution
2	Notify WeatherIt through your partnership contact
3	Discuss potential impacts and requirements
4	Coordinate any necessary adjustments
5	Implement with aligned timing

When to Notify

The right time to notify is:

Timing	Situation
Immediately	Urgent changes affecting live distribution
Early planning stage	Major system or business changes
Before implementation	Any change that might affect customer journeys
After unexpected issues	Problems discovered post-change

Earlier is Better
It's always better to notify too early than too late. If you're unsure whether a change is relevant, ask.

Common Questions

"What if the change is minor?"

If you're unsure, ask. It's better to mention something that turns out to be irrelevant than to miss something important.

"What if the change is urgent?"

Contact WeatherIt immediately. Emergency changes can be accommodated, but communication is essential.

"What if we've already made the change?"

Notify WeatherIt as soon as you realise the change may be relevant. We can assess impact and make any necessary adjustments.

Early notification avoids operational surprises. A quick conversation can prevent significant issues later.