This is the pre-production gate applied in engagements. Every unchecked box is a known failure mode from enterprise deployments. Work through it with the owner of each area — workspace admin, data owner, integration owner — before sign-off.
| # | Control | Owner / evidence |
|---|---|---|
| W1 | Administrator ownership defined (named primary and backup) | IT / SecurityRoster on file |
| W2 | Builder roles defined; build vs production access separated | Workspace adminPermission audit |
| W3 | User permissions documented and reviewed | Workspace adminAccess matrix |
| W4 | Production / testing strategy established (environments or conventions) | GTM EngineeringWritten convention |
| W5 | Naming conventions established for workflows and tables | GTM EngineeringConvention doc |
| D1 | Canonical CRM fields defined (which field is authoritative per attribute) | Data / RevOpsField map |
| D2 | Source-of-truth rules documented per enriched attribute | Data / RevOpsPrecedence doc |
| D3 | Normalization rules defined (formats, casing, country/phone standards) | Data / RevOpsRuleset |
| D4 | Duplicate handling documented (matching keys, merge policy) | Data / RevOpsPolicy |
| D5 | CRM write-back logic documented (which objects, which fields, when) | RevOpsWrite spec |
| P1 | Approved data providers documented with purpose per provider | RevOpsProvider register |
| P2 | Waterfall order established (which provider is tried, in what sequence) | GTM EngineeringWaterfall spec |
| P3 | Provider fallback logic established and tested | GTM EngineeringTest results |
| P4 | Credit / cost thresholds established per workflow | RevOpsBudget table |
| P5 | Vendor ownership defined (who manages the relationship, keys, billing) | RevOpsOwnership note |
| F1 | Workflow owner assigned by name | GTM EngineeringInventory entry |
| F2 | Test dataset established for pre-production validation | GTM EngineeringDataset |
| F3 | QA process established (sampling, expected-output review) | GTM EngineeringQA checklist |
| F4 | Error-handling behavior defined (retry, alert, degrade) | GTM EngineeringBehavior spec |
| F5 | Rollback procedure documented and rehearsed | GTM EngineeringRunbook |
| I1 | API ownership documented per integration | IT / SecurityRegister |
| I2 | Credentials securely managed (scoped, stored, rotated) | IT / SecurityKey inventory |
| I3 | CRM permissions reviewed for the integration user | IT / SecurityPermission set |
| I4 | Webhook behavior documented (payloads, auth, failure handling) | GTM EngineeringInterface doc |
| I5 | Downstream system dependencies mapped | IT / SecurityDependency map |
| G1 | Documentation requirements defined for every production workflow | GTM EngineeringStandard |
| G2 | Change-management process defined (review before production) | GTM EngineeringProcess doc |
| G3 | Workflow review process established (cadence, checklist) | GTM EngineeringCalendar + checklist |
| G4 | Monitoring responsibility assigned | OpsRoster |
| G5 | Incident response defined (who is called, what is the first step) | OpsRunbook |