GTG GOVERNANCE & MASTER DATA EXAMPLE / PUBLIC SAMPLE PLAYGROUND
One Client Identity. Every Decision Traceable.
Compare fictional CRM and billing client records. Choose a legal-name authority, decide how conflicts are handled, and assign a steward before preparing a master view.
Explore This Workflow
Select a step, change its settings, then run the example to see what changes. The workflow follows a fixed sequence. No login is needed. Changes reset when you reload or leave this page.
This public playground uses fictional data. Your changes affect this fictional example only.
Showing the result for the current connections and settings.
THE STARTING POINT
GTG Helps Two Teams Define a Shared Client Master
A fictional client’s CRM and billing teams disagree about Northstar’s legal name. A similar-looking legacy record has no verified ID.
- Identity rule
- Exact, verified client ID
- Legal-name authority
- BILLING
- Conflict policy
- Hold a conflicting master for steward review
- Situation
- One name conflict, one aligned client, one unverified identity
Illustrative GTG workflow with fictional data. Nothing is sent to GTG, a CRM, an email service, or a calendar.
Select a step to explore its role and settings. This walkthrough follows a fixed sequence.
SURVIVORSHIP / SELECTED CONTEXT
Apply Field Policy
Choose which system supplies the legal name and whether an explicit source policy may resolve a difference.
BILLING owns the legal-name field in the selected sample policy. A policy choice is not evidence of real business approval.
Configure Apply Field Policy
These settings apply to fictional sample data. Run the configured sample after a change.
1 master record(s) prepared; 2 case(s) remain with the operations data steward. Every proposed field retains its source reference.
- Source records
- 5
- Verified identities
- 2
- Masters prepared
- 1
- Cases held
- 2
THE BUSINESS OUTPUT
Client Master & Stewardship Register — Example
- Published master identities
- C-207 · Pinehurst Retail LLC
- Legal-name policy
- BILLING supplies the legal name; differences stay held.
- Other field owners
- CRM supplies the primary contact. Billing supplies the billing account. Neither is guessed from the name.
- Accountable role
- Operations data steward
Fictional source-authority and stewardship policies. No customer record is changed and no approval or task is submitted.
Master Record Decisions
Scroll horizontally to see all columns. Keyboard: focus the table, then use the arrow keys.
| Client identity | Published legal name | Status / decision | Steward |
|---|---|---|---|
| C-104 | Withheld pending review | Held. Legal names disagree. The selected hold policy requires steward review before publishing. | Operations data steward |
| C-207 | Pinehurst Retail LLC | Prepared. Sources agree on the legal name; field ownership is explicit. | Operations data steward |
Field Provenance — Proposed Values
Scroll horizontally to see all columns. Keyboard: focus the table, then use the arrow keys.
| Identity / field | Candidate value | Source record | Publication status |
|---|---|---|---|
| C-104 / Legal name | Northstar Field Services LLC | BILL-104 | Candidate only; master held |
| C-104 / Primary contact | avery@northstar.example | CRM-104 | Candidate only; master held |
| C-104 / Billing account | B-7104 | BILL-104 | Candidate only; master held |
| C-207 / Legal name | Pinehurst Retail LLC | BILL-207 | Prepared |
| C-207 / Primary contact | morgan@pinehurst.example | CRM-207 | Prepared |
| C-207 / Billing account | B-7207 | BILL-207 | Prepared |
Original Source Register
Scroll horizontally to see all columns. Keyboard: focus the table, then use the arrow keys.
| Source record | Verified client ID | Original legal name |
|---|---|---|
| CRM-104 | C-104 | Northstar Field Services |
| BILL-104 | C-104 | Northstar Field Services LLC |
| CRM-207 | C-207 | Pinehurst Retail LLC |
| BILL-207 | C-207 | Pinehurst Retail LLC |
| LEGACY-9 | Missing — not merged | Northstar Field Service |
What Needs Clarification
- LEGACY-9 · No verified client ID. The similar Northstar name is not merged; the steward must confirm its identity.
- C-104 · Legal names disagree. The selected hold policy requires steward review before publishing. Owner: Operations data steward.
Bring your own business problem, systems, and constraints into a GTG discovery conversation.
Build Your Discovery Brief