From scope note to findings pack

Data governance audits only help when evidence ties to owners and next actions. This is how Clouddatapro runs every engagement from Shau Kei Wan.

Quiet office corridor with soft morning light
  1. Frame the decision

    You describe the product, the data domains under pressure, and the audience for the findings — partner due diligence, internal board, or remediation planning. We reply with proposed scope and informational pricing.

  2. Inventory evidence paths

    We agree which systems, policies, and owners sit in scope. Access is typically read-only samples, configuration exports, and structured interviews — not uncontrolled production changes.

  3. Sample & compare

    Depending on the engagement we trace lineage, test retention jobs against policy, map transfers, or sample privileged access. Gaps are logged with severity and supporting artefacts.

  4. Deliver findings

    You receive the agreed pack — maps, tables, gap registers, and a walkthrough so compliance and engineering can challenge the reading before remediation starts.

  5. Clarify & close

    A short window for questions after delivery. Implementation of fixes stays with your team unless pairing was scoped upfront.