Who This Is For

This article is for program managers, CDFIs, city development officials, and other teams that manage participant workspaces.

Use Interchange to request participant data for compliance, risk monitoring, portfolio review, and impact reporting.

How Interchange Fits Programs

Program Manager workspaces use packages and programs to define what data is needed from participants.

• Package: A template that lists required data types and compliance requirements.
• Program: The operating container for participants, packages, dates, and status.
• Participant: A workspace enrolled in a program.
• Interchange request: The request sent to the participant workspace for the required data.

When a program triggers participant data requests, Interchange creates requests for the active participants. The participant still controls approval.

Common Participant Data Requests

Program teams often request:

• ConStrat Score
• Financial Data
• Compliance Information
• Headcount
• Revenue
• Receivables and payables
• Debt and liabilities
• Profit margin
• Bonding capacity

Choose the data types that match the program's stated requirements.

Participant Workflow

1. The program defines required data in packages.
2. Participants are enrolled in the program.
3. The program sends Interchange requests.
4. Participants approve or reject the requests.
5. Approved requests become active connections.
6. Participant data appears in portfolio, risk, compliance, or impact workflows when available.

Portfolio Status

Participant views may show Interchange status:

• Pending: The participant has not approved yet.
• Active: The participant approved the request.
• Rejected: The participant declined the request.
• Cancelled: The request was stopped.

Use status to separate onboarding problems from data quality problems. A missing metric from a pending participant usually means the request is not approved yet.

Guidance For Program Teams

Before sending requests, tell participants what data you are requesting and why. Use official organization visibility in Interchange privacy settings so participants can recognize the request.

For regulated or public programs, keep the request scope aligned with program requirements and internal approval rules.