Change Management Policy

01 Purpose

Big Bull Technologies, LLC (“Big Bull Technologies,” “BBT,” “we,” “our,” or “us”) is committed to delivering improvements to Before the Call (“B4C”) in a controlled, reliable, and secure manner.

This Change Management Policy explains our approach to planning, reviewing, testing, approving, deploying, and monitoring changes to the platform.

Our goal is to continuously improve the Services while minimizing unnecessary disruption to Customers.

02 Our Philosophy

Change is an essential part of maintaining and improving software.

Every change — whether it introduces a new feature, improves performance, enhances security, or resolves a defect — should be implemented thoughtfully and responsibly.

03 Scope

This policy applies to changes affecting Before the Call, including but not limited to:

• Application features
• Mobile applications
• Web applications
• Infrastructure
• Databases
• APIs
• Security controls
• Authentication
• Administrative workflows
• Artificial Intelligence features
• Integrations
• Platform configuration

04 Types of Changes

Changes may include:

05 Planning and Review

Before significant changes are deployed, Big Bull Technologies may perform activities such as:

• Requirements review
• Technical design review
• Security review
• Risk assessment
• Testing
• Validation
• Documentation updates

The level of review depends on the complexity and potential impact of the change.

06 Testing

Reasonable testing is performed before changes are introduced into production. Testing activities may include:

• Functional testing
• Integration testing
• User interface validation
• Security testing
• Performance testing
• Regression testing
• Compatibility testing
• Mobile platform testing

Testing approaches evolve as the platform matures.

07 Deployment

Platform updates are deployed using operational procedures intended to reduce disruption and maintain service reliability. Deployment approaches may include:

• Staged rollouts
• Incremental releases
• Infrastructure updates
• Configuration changes
• Emergency deployments when necessary

Deployment methods may change as the platform evolves.

08 Customer Communication

When practical, Customers may be informed about significant changes through:

• Release notes
• Platform notifications
• Email
• Website announcements
• Help Center updates
• Other appropriate communication channels

Minor maintenance updates may not require advance notification.

09 Rollback Procedures

If a deployed change creates unexpected issues, Big Bull Technologies may:

• Roll back the affected deployment
• Restore previous configurations
• Apply corrective updates
• Implement temporary mitigations
• Delay additional releases until the issue is resolved

The appropriate response depends on the nature of the issue.

10 Emergency Changes

Certain situations require immediate action to protect Customers or restore platform availability. Examples include:

• Critical security vulnerabilities
• Service outages
• Infrastructure failures
• Data protection concerns
• Authentication issues

Emergency changes may be deployed without advance notice when reasonably necessary. Where practical, Customers will be informed after deployment.

11 Continuous Improvement

Following significant deployments, Big Bull Technologies may review:

• Deployment success
• Customer feedback
• Platform performance
• Error monitoring
• Support trends
• Lessons learned

These reviews help improve future development and deployment practices.

12 Customer Responsibilities

Customers are encouraged to:

• Install available application updates
• Review release notes
• Report unexpected behavior
• Keep supported devices and browsers current
• Notify Big Bull Technologies of suspected issues

Customer feedback plays an important role in improving the platform.

13 Relationship to Other Policies

This policy should be read together with:

• OPS-001 — Service Availability Policy
• OPS-002 — Business Continuity Policy
• OPS-003 — Disaster Recovery Overview
• OPS-006 — Maintenance & Updates Policy
• TRU-001 — Security Overview

14 Changes to This Policy

Big Bull Technologies may update this Change Management Policy periodically.

Material changes will become effective on the published Effective Date after reasonable notice has been provided through the Services, our website, email, or another appropriate communication method.

15 Contact

Questions regarding this Change Management Policy may be directed to Big Bull Technologies.

Big Bull Technologies, LLC
Email: ashlea@bigbulltech.io

16 Revision History