# Certification checklist (paste into a ticket)

Use one copy per asset. A certifier marks every line PASS, FAIL or N/A (with a reason). The asset is certified only if every applicable line is PASS. Values in square brackets (such as [two] periods or [10] runs) are example thresholds, not vendor figures: set your own once, write them in your certification policy, and then do not negotiate them per ticket.

**Asset name:**
**Type:** (Tableau workbooks have no certification badge: "certified" for a workbook means it sits in the production project and passes this list.) (Power BI semantic model / Power BI report / Tableau published data source / Tableau workbook)
**Location:** (workspace or project, full path)
**Author:**
**Certifier:** (must not be the author)
**Date:**

## 1. Ownership

- [ ] A row for this asset exists in the ownership register. PASS if the row exists and the link is in the ticket.
- [ ] Business owner, technical owner and backup are three named people (the backup is not the technical owner). PASS if all three are filled in.
- [ ] Each named person is an active employee or contractor. PASS if each name resolves in the company directory today.
- [ ] Each owner has confirmed in writing (reply, comment or sign-off in this ticket). PASS if three confirmations are attached.
- [ ] A contact is set on the asset itself (Power BI contact list, or Tableau description and owner). PASS if a consumer can see who to ask without opening the register.

## 2. Source and access

- [ ] The source of record is named in the asset description. PASS if one system and one table or view is named for each headline measure.
- [ ] The data owner has approved this use of the source. PASS if an approval is linked.
- [ ] The connection does not depend on one person's personal credentials. PASS if the credential is a service account or shared connection owned by a team.
- [ ] Access is granted through groups, not named individuals. PASS if the permission list shows groups only (list any exceptions here: ______).
- [ ] If row level security or user filters exist, they were tested as at least one user from each restricted group. PASS if the test user, the group and the expected row count are recorded.

## 3. Calculations and definitions

- [ ] Every headline metric has a metric definition card. PASS if every metric shown on the first page or first dashboard links to a card with owner and formula.
- [ ] Calculations were reviewed by a person other than the author. PASS if the reviewer's name and date are recorded and every calculated field or measure on the review list is ticked.
- [ ] No unexplained hard-coded values in calculations (dates, IDs, thresholds). PASS if each literal is either removed or documented on the card.
- [ ] Known exclusions are written on the card (test accounts, internal users, cancelled orders). PASS if the card has an exclusions entry, even if it says "none".

## 4. Reconciliation

- [ ] Headline numbers were reconciled to a known source of truth for at least [two] periods. PASS if the ticket lists the period, the source figure, the asset figure and the difference.
- [ ] The difference is within the tolerance agreed with the business owner. PASS if the tolerance is written down before the test and every difference is inside it.
- [ ] Filtering to all, to none and to a single value behaves sensibly on each dashboard or page. PASS if all three states were checked and no error or misleading blank appears.

## 5. Refresh and performance

- [ ] A refresh or extract schedule exists and matches the freshness the business owner needs. PASS if the schedule and the required freshness are both written down.
- [ ] Failure notifications go to a shared mailbox or channel, and to the technical owner and the backup. PASS if the notification list is attached.
- [ ] The last [10] scheduled runs are either successful or each failure has an explanation. PASS if the run history was reviewed and the result recorded.
- [ ] The main view or page loads within the target the certifier set before testing [for example, 5 seconds]. PASS if the measured time and the target are both recorded.

## 6. Release and location

- [ ] The asset is in the production workspace or project, published through the agreed path (pipeline, promotion step or approved publisher). PASS if the publisher and the date match the release record.
- [ ] No other asset with the same name and purpose exists in production. PASS if a search by name returns one result, or the duplicates are listed with a disposition.
- [ ] Description, certification notes and tags are filled in. PASS if all three are non-empty and the notes state what was checked and when.

## 7. Review date

- [ ] A next review date is set in the register and on the asset. PASS if the date is in the future and no later than [six months] from today.

## Result

**Outcome:** CERTIFIED / NOT CERTIFIED
**Failed lines (with required fix and owner):**
**Certified date:**
**Next review:**

## Revoking certification

Remove the badge and set the register to "N" if any of these happens: the owner leaves and no replacement is confirmed within [30 days]; a review date passes without a review; a reconciliation failure is found; the source of record changes. Record the reason in the register.