Client Data Source Validation (Onboarding)

Client Data Source Validation (Onboarding)

1. 01

   Inventory every data source the client expects to see in the dashboard

   List all databases, APIs, spreadsheets, and third-party tools. Confirm each one is reachable from the BI platform and note any that require custom connectors or middleware.

2. 02

   Verify source credentials and access permissions with the client

   Request read-only credentials or API keys for each source. Test connectivity from the BI platform and document any access restrictions that could block scheduled refreshes.

3. 03

   Assess data freshness and update frequency for each source

   Ask the client how often each system updates (hourly, daily, weekly). Compare that to the reporting cadence promised in the retainer to set realistic refresh expectations.

4. 04

   Map source fields to the metrics and dimensions in the reporting spec

   Create a field-level mapping that ties each dashboard metric to its source column. Flag any metrics that require transformation or calculation before they can be displayed.

5. 05

   Run a trial data pull and validate row counts against source systems

   Pull a sample dataset from each source and compare record counts with the client's own queries. Discrepancies here signal permission gaps or API pagination issues that will corrupt later reports.

6. 06

   Document data quality rules and alert thresholds with the client

   Agree on what constitutes a data quality failure (missing values, stale timestamps, outlier spikes) and set up automated alerts in the BI platform so the agency is notified before the client sees a broken dashboard.

7. 07

   Confirm data residency and privacy requirements before loading client data

   Check whether any source contains personally identifiable information or regulated data. If the client operates under GDPR or sector-specific rules, verify the BI platform's hosting region and subprocessor list.