PROJECT PREPARATION

A better project starts with a clearer brief.

Use six prompts to define a practical data-governance engagement. Work privately, download the outline and keep approval with your own organisation.

An engraved observatory and council of records; a metaphor for ownership and decision rights.
CONCEPTUAL ENGRAVING / DATAGOVERNANCE.CA
YOUR LOCAL WORKING OUTLINE

Six prompts. One editable file.

Starting interest: Governance operating model. Download a Markdown outline and complete it in your own approved workspace. This page does not accept or send project information.

Get the project-brief outline ↗

Inquiry submission and email handoff remain disabled. Nothing is sent by using these planning resources.

DataGovernance.ca working methods · Original planning guidance. Examples are illustrative, not client results or a regulatory framework.

The decision we need to improve

Name the decision, report or workflow. Describe who uses it and what happens when the information is unclear. Choose one pilot domain rather than a whole-company transformation.

What is known and what is still a question

List the relevant systems, report definitions and available evidence. Distinguish an observed defect from a suspected gap. Record anything you cannot currently confirm. A public planning exercise does not verify these facts.

People and decision rights

Identify the sponsor role, accountable business owner, steward or coordinator and technical custodian. Record the decision each role can make and the questions requiring privacy, legal, security or other specialist input.

Access and exclusions

Define approved evidence, allowed access and information that must not be transferred. Start with metadata and fabricated or authorised redacted examples. Do not paste passwords, customer records or sensitive documents into this website or the downloadable brief.

Deliverables and acceptance evidence

Name the smallest useful outputs: for example, an approved definition, a source trace, a rule with an issue owner and a repeatable review. Write how an internal colleague will test the handoff. A delivered document and an operating process are different acceptance criteria.

Dependencies, costs and the next decision

Record internal availability, system dependencies, timing constraints and an approved planning budget if one exists. Keep estimates separate from quoted fees. Identify what would require pausing or changing scope. This brief is not a quote, service agreement or appointment.

PUT THE NOTE TO WORK

Start with one concrete example.

Use the related resources to prepare a bounded conversation. Keep confidential records in your approved internal environment.

Use the readiness assessment

Build a draft governance charter

Browse the six working templates

A SMALLER, CLEARER FIRST STEP

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 brief
01

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.