How Governance, Check Ins and Change Control Work at Osher Digital

Strong project governance keeps delivery predictable and ensures that everyone stays aligned throughout an AI or automation project. This article explains how we structure communication, how decisions are made and how changes are managed so that projects run smoothly from start to finish.

Our Governance Approach

Our governance framework is designed to provide clarity, transparency and steady momentum. It focuses on three areas:

• Clear roles and responsibilities

• Regular and structured communication

• A simple and collaborative change control process

This approach keeps both teams informed and reduces the risk of surprises later in the project.

Roles and Responsibilities

Each project has a small group of people who keep things moving:

• Osher Digital project lead: Responsible for delivery, communication, technical decisions and timelines.

• Client project owner: Provides access, approvals and input on requirements.

• Client IT or technical contacts: Assist with credentials, system access and integration questions.

Having clear owners on both sides ensures that questions and decisions are resolved quickly.

How Check Ins Work

Check ins are used to keep the project aligned and to address issues before they impact progress. We typically structure check ins around:

• Status updates

• Review of completed work

• Risks, dependencies and access requirements

• Decisions required for the next stage

• Alignment on upcoming milestones

Check ins can occur weekly or fortnightly depending on the pace of the project. Additional check ins can be scheduled at any time if a decision or issue requires quick attention.

Day to Day Communication

Outside of scheduled meetings, communication is handled through:

• Email for everyday updates and information

• Microsoft Teams for calls, workshops and technical discussions

We aim to keep communication simple, direct and easy to track.

Issue and Risk Escalation

If a risk or blocking issue appears, we raise it immediately. Examples include:

• Delayed system access

• Credentials not yet approved

• Data quality issues

• Changes to client priorities

• Unexpected behaviour in third party APIs

Escalation is designed to unblock progress quickly and collaboratively.

How Change Control Works

Projects sometimes need adjustment as new information becomes available. We treat change control as a clear and transparent process rather than a barrier.

The process is simple:

1. Identify the required change
   This may be raised by either team.

2. Assess the impact
   We outline cost, time and technical implications.

3. Client approval
   The client confirms whether to proceed.

4. Implementation
   The approved change is scheduled and delivered.

This ensures that every change is understood, agreed and planned properly.

Keeping the Project on Track

Good governance is not about formalities. It is about maintaining steady progress. To support this, we:

• Confirm system access early

• Review documentation at the start

• Communicate clearly and often

• Keep scope defined and documented

• Raise concerns early

• Provide straightforward next steps

Our goal is to give you a predictable, transparent and stress free project experience.