Overview

Solvren provides a structured process for governing revenue-impacting changes.

This guide explains how operators interact with the system during normal workflows.

Dashboard

The dashboard provides visibility into:

Changes awaiting approval
Changes assigned to you
Blocked or overdue changes
Operational alerts

Queues help teams prioritize reviews and identify bottlenecks.

Changes represent operational modifications that could impact revenue.

Examples include:

Pricing updates
Billing configuration changes
Lead routing changes
Revenue recognition adjustments

Each change follows a structured workflow to ensure coordination.

Every change moves through the following states:

Draft
Ready
In Review
Approved
Rejected
Archived

These states provide visibility into operational readiness.

Reviewers evaluate:

Risk analysis
Evidence completeness
Operational safeguards
Implementation plan

Reviewers can:

Approve
Request changes
Add comments

Solvren ensures critical safeguards are documented.

Evidence may include:

Rollback procedures
Testing documentation
Monitoring plans
Revenue validation strategies

Changes cannot be submitted until required evidence is provided.

Solvren notifies users when:

Changes require review
Evidence is missing
Approvals are completed
Changes become overdue

Notifications can be delivered via:

Email
Slack
In-app alerts

Solvren supports full-text search across:

Changes
Systems
Domains
Approvers

This allows teams to quickly locate historical decisions.

Every action is recorded in the audit log.

Tracked events include:

Change creation
Evidence updates
Approval decisions
Configuration changes

Audit history ensures accountability and traceability.