Wealth-Tech PRD Test-Data Section Template
The cheapest place to fix a coverage gap is in the PRD. The most expensive place is production. This template is the test-data section that should appear in every wealth-tech PRD — pre-filled with the structurally important questions, with inline guidance product managers can lean on the first time they answer them.
What you walk away with
~10 min · 4 slots · 22 blocks- A pre-built PRD section that forces the team to declare archetype + edge-case requirements before engineering kickoff.
- Inline guidance for each prompt, so the PM doesn't need to consult the test-data team to answer.
- A clear cross-walk to the Wealth Data Sets that fulfill the declared requirements.
Variables
Live document preview
Test Data Requirements — [FEATURE_NAME]
Owners: Product: [PRODUCT_OWNER] · Engineering: [ENGINEERING_LEAD] · Target: [TARGET_RELEASE]
Fill this in before engineering kickoff. Every code path the feature will take needs at least one synthetic household that exercises it. If you can't name the household, you don't have a test plan — you have a hope.
1. Code paths
[List the code paths the feature will take. Be granular — 'happy path' is one path; 'happy path with senior client' is a different path.]
- [CODE_PATH_1]
- [CODE_PATH_2]
- [CODE_PATH_3]
2. Edge cases
Edge cases = the structurally tricky cases the feature must handle defensibly. For tax features, list wash-sale variants, lot-selection methods, term-boundary cases. For compliance features, list senior clients, ITIN filers, dual citizens. Pull from the Edge-Case Test-Coverage Audit Checklist for the canonical list.
- [EDGE_CASE_1] — required because [REASON]
- [EDGE_CASE_2] — required because [REASON]
- [EDGE_CASE_3] — required because [REASON]
3. Required archetypes
For each code path × edge case intersection, name a synthetic archetype that exercises it. If the archetype doesn't exist in the firm's current corpus, declare the gap so engineering can request it (or so the PM can engage WealthSchema for the bundle that ships it).
- Archetype A: [DESCRIPTION] — exercises [CODE_PATHS]
- Archetype B: [DESCRIPTION] — exercises [CODE_PATHS]
Gaps in current corpus: [LIST_OR_NONE]
4. Recommended Wealth Data Set bundle
Per the corpus sizing for this feature: [RECOMMENDED_BUNDLE]. Run the Which Wealth Data Set wizard if unsure.
If the team is sourcing the corpus from WealthSchema/WealthSynth, link the dataset page here. If sourcing in-house, link the in-house corpus version pin.
5. Coverage gate
Pre-launch sign-off: the Pre-Launch Test-Data Sign-Off must be completed and signed by Engineering / QA / Compliance / Product before the feature ships. The corpus version + archetypes used + code-path coverage are recorded in the sign-off.
- Coverage matrix populated and reviewed
- Edge-case archetypes added to regression suite
- Pre-launch sign-off signed
6. Compliance scope
- Reg BI applicability: [YES_NO_NA] — if yes, link to populated Reg BI Evidence-Field Worksheet
- AML applicability: [YES_NO_NA] — if yes, link to populated AML Typology Mapping Worksheet
- GLBA applicability: [YES_NO_NA] — if yes, link to populated GLBA Data Inventory Worksheet
- Form ADV impact: [YES_NO_NA] — if yes, item / part affected
Run the 'Which Compliance Workstream Does This Feature Trigger?' wizard. The output of that wizard goes here as a paragraph.
Unfilled slots show as [VARIABLE_NAME] so the partial document still reads. Filling in the form on the left substitutes them inline.
What to do with this
Paste this section into the firm's PRD template (Notion / Confluence / Linear / Aha! / Productboard / wherever). Make it required for every feature that touches data, calculations, or recommendations. Reviewed in PRD review along with the rest of the spec; archetypes and edge cases get scoped before engineering kickoff.
FAQ
Does every feature need this section?
Every feature that touches data, calculations, or recommendations should have it. Features that are purely UI (button colors, layout changes) don't need it — but err on the side of including it. The cost of completing the section is 15 minutes; the cost of skipping it and shipping a bug is much higher.
Who fills it in?
PM. Engineering and compliance review and challenge in PRD review. The PM owns the section; engineering owns the implementation; compliance owns the regulator-scope determination.