# LoopLedger sample data package

LoopLedger has 2 buyer-ready CSV template(s), 3 mapped source group(s), and 10 checks for moving from seeded demo data to a first tenant dry import.

Product: LoopLedger
Tenant: Northstar Referral Guild
Production domain: referral-network.ideas-realized.com
Canonical page: /demo-library/referral-network
Preview screen: Matchmaker (matcher) - relationship matching and referral capture
Preview URL: https://referral-network.ideas-realized.com?screen=matcher
JSON manifest: /demo-library/referral-network/sample-data-package.json

## Counts
- CSV templates: 2
- Sample rows: 4
- Source groups: 3
- Mapped fields: 10
- Required fields: 7
- Validation gates: 3
- Acceptance checks: 10

## Cutover
Run a dry import into the tenant preview, reconcile duplicates with the chapter admin, then open logging for one meeting cycle before enabling sponsor reporting.

## Privacy Note
Referral notes should exclude sensitive deal details unless the network has explicit member consent and a data-retention policy.

## Source Maps

### 1. Member roster
System: Chapter spreadsheet or association CRM export
Owner: Chapter admin
Cadence: One seed import plus monthly refresh
Status: ready
Records: 80 to 250 member records

| Source field | Target field | Required | Validation |
| --- | --- | --- | --- |
| member_name | Member.displayName | Yes | Must be unique with email inside the tenant. |
| email | Member.email | Yes | Valid email format and no duplicate active member. |
| business_category | Member.category | Yes | Unmapped categories require admin review. |
| membership_status | Member.status | Yes | Only active and sponsor records can receive referral tasks. |

### 2. Referral history
System: Spreadsheet, form export, or CRM activity report
Owner: Referral chair
Cadence: Optional historical import before pilot kickoff
Status: template
Records: 50 to 500 referral records

| Source field | Target field | Required | Validation |
| --- | --- | --- | --- |
| source_member_email | Referral.sourceMemberId | Yes | Source member must exist in the roster import. |
| recipient_member_email | Referral.recipientMemberId | Yes | Recipient member must exist and cannot equal source member. |
| referral_date | Referral.createdAt | Yes | Reject future dates and dates before chapter launch unless approved. |
| outcome | Referral.status | No | Unknown outcomes import as needs-review. |

### 3. Sponsor reporting fields
System: Board report spreadsheet
Owner: Executive director
Cadence: Quarterly reporting export
Status: optional
Records: 10 to 30 sponsor-visible metrics

| Source field | Target field | Required | Validation |
| --- | --- | --- | --- |
| sponsor_segment | Report.segment | No | Sponsor-visible rows cannot include private notes. |
| estimated_value | Referral.estimatedValue | No | Values above threshold require admin review before reporting. |

## CSV Templates

### 1. Member roster import
Download: /demo-library/referral-network/import-templates/member-roster
File: referral-network-member-roster.csv
Source system: Chamber roster export or CRM contact list
Owner: Chapter admin
Cadence: Initial import, then monthly refresh

Seeds the member directory, category filters, chapter assignment, and sponsor-safe profile fields.

| Column | Required | Example | Description |
| --- | --- | --- | --- |
| member_id | Yes | MEM-1042 | Stable member identifier from the roster source. |
| member_name | Yes | Maya Patel | Public member name shown in the directory. |
| company | Yes | Patel Accounting Group | Member company or practice name. |
| category | Yes | Accounting | Referral category used for directory filtering. |
| chapter | Yes | North Bay Growth Circle | Chapter, cohort, or market group. |
| email | Yes | maya@example.com | Member email used for invite and reminder workflows. |
| sponsor_visible | No | yes | Whether aggregate activity can appear in sponsor exports. |

Sample rows:
| member_id |member_name |company |category |chapter |email |sponsor_visible |
| --- |--- |--- |--- |--- |--- |--- |
| MEM-1042 |Maya Patel |Patel Accounting Group |Accounting |North Bay Growth Circle |maya@example.com |yes |
| MEM-1188 |Evan Brooks |Brooks Commercial Lending |Commercial lending |North Bay Growth Circle |evan@example.com |yes |

Acceptance checks:
- Every row has a stable member_id and email.
- Category values are normalized before public filters are enabled.
- Sponsor visibility is approved before sponsor exports are generated.

### 2. Referral activity import
Download: /demo-library/referral-network/import-templates/referral-log
File: referral-network-referral-log.csv
Source system: Spreadsheet referral log or CRM activity export
Owner: Chapter coordinator
Cadence: One-time backfill, then weekly upload during pilot

Backfills referral records, status history, attributed value, and follow-up owners.

| Column | Required | Example | Description |
| --- | --- | --- | --- |
| referral_id | Yes | REF-2406-018 | Stable referral or activity identifier. |
| from_member_id | Yes | MEM-1042 | Member who gave the referral. |
| to_member_id | Yes | MEM-1188 | Member who received the referral. |
| client_name | Yes | Harbor Renovation LLC | Client or opportunity label approved for internal use. |
| estimated_value | No | 18000 | Optional value for internal reporting. |
| status | Yes | Accepted | Current referral status. |
| follow_up_due | No | 2026-07-08 | Next follow-up date in ISO format. |

Sample rows:
| referral_id |from_member_id |to_member_id |client_name |estimated_value |status |follow_up_due |
| --- |--- |--- |--- |--- |--- |--- |
| REF-2406-018 |MEM-1042 |MEM-1188 |Harbor Renovation LLC |18000 |Accepted |2026-07-08 |
| REF-2406-022 |MEM-1188 |MEM-1042 |Solano Dental Partners |7200 |New |2026-07-03 |

Acceptance checks:
- from_member_id and to_member_id match imported roster records.
- Private notes are excluded from the import file.
- Status values map to the live referral workflow.

## Validation Gates
- Roster duplicate review (blocking): Duplicate emails or member names prevent referral attribution. Resolution: Chapter admin merges or removes duplicates before pilot launch.
- Category taxonomy approval (warning): Unmapped business categories weaken member search and referral matching. Resolution: Approve a chapter category list during setup.
- Private note policy (blocking): Historical referral notes may contain sensitive deal details. Resolution: Import only summary notes until retention and consent rules are approved.

## Acceptance Checklist
- Member roster import: Every row has a stable member_id and email.
- Member roster import: Category values are normalized before public filters are enabled.
- Member roster import: Sponsor visibility is approved before sponsor exports are generated.
- Referral activity import: from_member_id and to_member_id match imported roster records.
- Referral activity import: Private notes are excluded from the import file.
- Referral activity import: Status values map to the live referral workflow.
- Roster duplicate review: Chapter admin merges or removes duplicates before pilot launch.
- Category taxonomy approval: Approve a chapter category list during setup.
- Private note policy: Import only summary notes until retention and consent rules are approved.
- Open Matchmaker after dry import and verify relationship matching and referral capture.

## Handoff Routes
- Sample data package: /demo-library/referral-network/sample-data-package - Markdown handoff with CSV templates, seed rows, validation gates, and cutover notes.
- Sample data package JSON: /demo-library/referral-network/sample-data-package.json - Machine-readable sample-data manifest for implementation automation.
- Production data contract JSON: /demo-library/referral-network/data-contract.json - Entity, source, event, API-shaped route, and boundary contract for production planning.
- Implementation JSON: /demo-library/referral-network/implementation.json - Full setup spec with routes, productization fields, tenant defaults, and security notes.
- Implementation intake: /implementation-intake/referral-network-implementation-intake - Buyer source-system, domain, access, and asset collection workflow.
- Live app proof screen: https://referral-network.ideas-realized.com?screen=matcher - Matchmaker: relationship matching and referral capture