Find the right starting point.
A scoped diagnostic for one important domain, workflow or AI use case.
- Evidence-backed baseline
- Prioritised gaps and owners
- 30 / 60 / 90-day roadmap
CANADIAN DATA GOVERNANCE CONSULTINGYour data.
Your data.
Understood.
Under control.
We help organisations turn scattered information into clear ownership, reliable decisions and a stronger foundation for AI.
Strategy is the starting point. Working processes, usable evidence and an internal team that can carry them forward are the deliverables.
ASSESS → IMPLEMENT → OPERATE
Practical work. Defined scope. No black-box scores.
A decision has an accountable owner.
A named role, a documented decision right and a clear route for resolving issues.
Select a control to explore its purpose. The engraving is a visual metaphor; no client systems are connected.
BUSINESS-LED OWNERSHIPIMPLEMENTATION, NOT JUST POLICYCANADIAN CONTEXTBUILT TO BE MAINTAINED
A BETTER PLACE TO BEGINWhat brought
What brought
you here?
You do not need to start with a programme name. Start with the thing your team cannot confidently answer.
A PRACTICAL STARTING POINT
Data quality & trusted reporting
Agree the definitions, test the critical fields and assign the work needed to make the numbers explainable.
Explore this serviceWHAT WE HELP YOU BUILDLess ambiguity.
Less ambiguity.
More working capability.
From the first diagnostic to the routines that keep governance alive. Every service has a defined output, a client role and a boundary.
Explore all servicesData governance diagnostic
Find the gaps worth fixing first.
Governance operating model
Give every important decision an owner.
Data inventory & lineage
Know what you have. Know where it goes.
Data quality & trusted reporting
Make important numbers explainable.
Privacy & data lifecycle operations
Turn privacy requirements into working routines.
AI data readiness
Prepare the information your AI will depend on.
Vendor & third-party data review
Understand the data relationship before you sign.
Fractional governance support
Keep governance moving after the project.
THREE WAYS TO WORK TOGETHERStart small.
Start small.
Make it operational.
A clear commercial path from “where do we begin?” to a maintained capability. Scope and fees are agreed before work starts.
Put the controls to work.
A defined delivery project, built around an agreed outcome and acceptance criteria.
- Ownership and decision workflows
- Inventory, quality or lifecycle pilot
- Documentation and internal handoff
Keep the work moving.
Fractional support to maintain the programme and develop internal capability.
- Stewardship and issue reviews
- Sponsor briefings and decisions
- Ongoing roadmap refinement
Engagements are subject to scope, capability and availability. No promised compliance outcome or mandatory software purchase.
THE WORK SHOULD BE VISIBLESee what you
See what you
actually get.
Registers, decisions and roadmaps your team can use. These are illustrative examples—not client work or performance claims.
ILLUSTRATIVE · NO CLIENT DATA
| ASSET | ACCOUNTABLE ROLE | SOURCE | REVIEW STATUS |
|---|---|---|---|
| Customer master | Customer operations | CRM | Owner assigned |
| Monthly revenue | Finance lead | Reporting model | Definition to review |
| AI knowledge base | Use-case owner | Approved documents | Permissions to confirm |
Useful governance makes the unknowns visible. It does not turn an unanswered question into a green checkmark.
PUT YOUR CURRENT STATE IN CONTEXTSix dimensions.
Six dimensions.
A clearer next step.
Our 18-question self-assessment shows what you have in place, what remains unknown and where to focus first.
No login. No email gate. Answers are processed in your browser and are not sent to our server.
Take the readiness assessmentCONTEXT CHANGES THE WORKBuilt around
Built around
your organisation.
Choose an entry point close to your business. These are engagement scenarios, not a list of claimed clients.
FIELD NOTESUseful before
Useful before
we ever meet.
Original implementation guides, practical tools and source-linked context.
Explore the resource library
Your first 90 days of data governance
Start with one business decision. Build the smallest working system around it. Expand only after the first cycle teaches you something.
Read the field noteOwner, steward or custodian: who decides?
The point of a role model is not to invent more titles. It is to stop important questions disappearing between business and technical teams.
Read the field noteAI-ready data is more than clean data
A tidy document collection can still be the wrong collection for an AI system to use.
Read the field noteClear answers.
Clear boundaries.
What does a first engagement look like?
We start by agreeing the problem, sponsor, domain, available evidence and boundaries. A diagnostic can establish a baseline before you commit to implementation. Exact scope, team, fees and acceptance criteria are agreed in writing.
Do we need a data catalogue or a new software platform?
Not necessarily. The first problem may be unclear ownership, conflicting definitions or an untested handoff. We define the operating need before considering software. Tool integrations and implementation access are separately scoped.
Is the online assessment an audit or certification?
No. It is a self-reported planning exercise. It does not inspect systems, verify answers, assess all applicable requirements or establish legal compliance. Unknown answers remain visible in the results.
Can you guarantee compliance or certify our organisation?
No. We provide operational consulting and implementation support. Legal advice, formal assurance, certification and specialist testing require the appropriate separately engaged professionals.
Will you need unrestricted access to our data?
No. Discovery begins with a business brief, system descriptions, metadata and redacted examples. Any later access, processing, security arrangements and retention terms must be agreed before information is transferred.
How does this connect to AIGovernance.ca?
DataGovernance.ca focuses on the information foundations: ownership, definitions, quality, permissions, lineage and lifecycle. AIGovernance.ca is the connected AI-governance resource. An AI engagement may need both workstreams, with its actual scope agreed in advance.
ONE CHANGE. A TRACEABLE RESPONSE.Follow the decision.
Follow the decision.
Not just the data.
Explore a fictional reporting workflow. Change the scenario to see which decisions and evidence need attention. This is an explanatory model, not connected monitoring.
01SourceOwner + version
02TransformRules + period
03ReportDefinition + use
04DecisionAuthority + record
WHAT NEEDS TO HAPPEN
A source field is renamed.
The source owner explains the change. The custodian checks the transformation and downstream report. The business owner decides whether the meaning is unchanged before the next use.
- Keep as evidence
- Source version, field mapping, affected outputs and the test record.
- Do not assume
- A refreshed dashboard does not prove that the mapping or meaning is still correct.
NEW / THE VISUAL FIELDGUIDEMake the complex
Make the complex
easier to explain.
Ownership, lineage, quality and lifecycle—made concrete through twelve visual explanations, practical questions and connected service scopes.
Explore the visual fieldguideSTART WITH A CONVERSATION
Make your next data decision a clearer one.
Tell us what is not working. We will discuss a sensible starting scope.
FROM THE WORKING DESKGood governance.
Good governance.
In everyday practice.
Practical field notes for the decisions between the strategy and the finished process.
Make the business case without inventing the return.
Start with an observable operational problem. Separate the cost of repeated work from the cash your organisation could actually save.
Read the field noteOne metric. One meaning. A useful glossary workshop.
A glossary becomes useful when it resolves a real disagreement and connects the agreed meaning to the calculation, owner and permitted use.
Read the field noteA small data change can have a long shadow.
Renamed fields, revised definitions and access changes need an understandable route from request to impact review, approval, testing and handoff.
Read the field noteA governance meeting should finish with decisions.
Build a review rhythm around exceptions, unresolved questions and evidence of how the process is working—not a growing collection of status slides.
Read the field noteA SMALLER, CLEARER FIRST STEPBring a problem.
Bring a problem.
Leave with a brief.
Choose one decision, name the people involved and set an evidence boundary before anyone asks for your data.
Prepare your project brief01
Choose the decision
Name the report, workflow or use case that needs to work better.
02
Set the boundary
Identify the owner, allowed evidence and important exclusions.
03
Define useful completion
Agree what a colleague should be able to repeat or verify.