Overview

This guide demonstrates the full lifecycle of a change in Solvren.

By the end of this walkthrough you will have:

• created a change
• generated a coordination plan
• analyzed revenue risk
• submitted a change for approval

Step 1 — Create the Change Draft

Start by creating a new change.

Provide the basic information:

Title
Description
Systems involved
Change type
Domain

Example:

Title: Stripe pricing tier update
Systems: Stripe, HubSpot
Domain: Pricing
Change type: Pricing configuration

Solvren collects structured information that determines coordination and risk.

You will be asked to provide:

Rollout method
Customer impact
Backfill requirements
Implementation details
Expected outcome

This structured data allows the system to reason about potential failure modes.

Coordination Autopilot analyzes the change and generates:

Suggested approvers
Evidence requirements
Operational safeguards
Coordination tasks

You can apply these suggestions with one click.

This ensures governance requirements are applied consistently.

The Revenue Impact Report evaluates potential financial risk.

The report includes:

Risk score
Failure modes
Required safeguards
Executive summary

This report is used by reviewers to evaluate whether a change is safe to deploy.

Attach or complete the evidence required for the change.

Examples include:

Rollback plan
Monitoring plan
Test scenarios
Revenue validation

Evidence ensures the organization can safely recover if something goes wrong.

Once readiness requirements are satisfied, submit the change.

Reviewers will see:

Change summary
Revenue Impact Report
Evidence checklist
Coordination plan
Timeline

Approvers can then approve or request changes.

You have successfully completed the full Solvren change workflow.