Testing
AuraScore 83/100

Grant Allocation Platform Migration Integrity Matrix

Design a structured data reconciliation and validation matrix for nonprofit grant management migrations.

Use this template when migrating historical grant files, donor ledgers, and disbursement records from legacy relational databases into modern platforms. It ensures data fidelity, audit compliance, and schema alignment.

Template

Role: Principal Data Quality & Migration Test Engineer specializing in nonprofit financial systems and grant management architectures.

Context

  • Non-profit organization: {{nonprofit_entity}}
  • Legacy datastore source: {{legacy_database_source}}
  • Target grant platform: {{target_grant_platform}}
  • Critical record types: {{critical_record_types}}
  • Compliance and retention rules: {{regulatory_retention_rules}}
  • Statistical sampling threshold: {{sampling_threshold}}

Task

Construct a data migration validation and reconciliation test matrix that validates schema integrity, financial calculations, audit trail preservation, and edge-case handling during the transition of {{critical_record_types}} for {{nonprofit_entity}}.

Method

  1. Extract structural schema attributes, keys, and foreign constraints from {{legacy_database_source}}.
  2. Map source fields to {{target_grant_platform}} data models, noting transformational business logic.
  3. Define data integrity checks for {{critical_record_types}} covering completeness, truncation, and precision.
  4. Formulate reconciliation test vectors for grant funding balances, historical disbursals, and donor attributions.
  5. Incorporate audit trail validation rules to satisfy {{regulatory_retention_rules}}.
  6. Establish sampling criteria reflecting {{sampling_threshold}} across historical batches.
  7. Compile testing stages into a pre-cutover and post-cutover verification matrix.

Constraints

  • MUST include quantitative reconciliation checks (record counts, hash sums, and monetary totals).
  • MUST NOT omit boundary and null-handling scenarios for historic or archived data.
  • Every row must detail the specific SQL query logic or script assertion required.
  • Output must maintain a standardized tabular matrix structure with zero conversational filler.

Output format

  1. Migration Scope Overview (Data volume, source/target specs)
  2. Data Reconciliation & Integrity Matrix (Markdown table with columns: Entity Type, Field/Constraint, Validation Rule, Source Query/Assertion, Target Validation Logic, Error Tolerance Threshold, Cutover Gate Status)
  3. Rollback & Remediation Action Table

Self-review

  • Does the matrix verify data retention compliance with {{regulatory_retention_rules}}?
  • Are mathematical and currency conversions explicitly validated?
  • Is the sample size aligned with {{sampling_threshold}}?
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-testing
public-sector-nonprofit
data-migration
data-integrity
nonprofit