# Schemas and Reusable Templates

## 1. Opportunity record schema

Every opportunity in the pipeline must carry all fields. Records missing a verified pathway are labeled `relationship_target` or `unverified_lead` and never shown as actionable.

| Field | Type | Rule |
|---|---|---|
| `funder` | text | Legal or common name |
| `program` | text | Specific program, not the funder in general |
| `capital_layer` | enum | community, technology_inkind, local_institutional, public_city, public_state, public_federal, national_foundation, corporate, private_capital, international |
| `support_type` | enum | cash_grant, contract, subaward, product_credit, discount, equipment, training, implementation, visibility, sponsorship, pri_or_loan, fellowship |
| `mission_fit` | text plus 1 to 5 | Which mission areas and why |
| `population_fit` | text | Served population match |
| `geography_fit` | enum | nyc, nys, national, international, plus notes |
| `eligibility` | text | 501(c)(3), budget minimums, years operating, excluded types |
| `award_range` | text | As stated by funder or "not stated" |
| `route` | text | Portal, LOI, email, nomination |
| `cycle` | text | Annual, rolling, one-time |
| `next_deadline` | date or "rolling" or "not stated" | |
| `status` | enum | open, rolling, loi_required, invitation_only, employee_nominated, relationship_led, pass_through_only, daf_only, closed |
| `registrations_required` | list | SAM, SFS prequal, PASSPort, state charity registration |
| `documents_required` | list | |
| `match_required` | text | |
| `restrictions` | text | Program, capital, general operating |
| `reporting` | text | Frequency and form |
| `payment_timing` | enum | advance, milestone, reimbursement, unknown |
| `renewal` | text | Renewable, one-time, multiyear |
| `relationship_path` | text | Named contact type or intermediary |
| `source_url` | url | |
| `source_date` | date | Date shown on the page, or "undated" |
| `verified_date` | date | Last date a human confirmed the page |
| `confidence` | enum | high, medium, low |
| `fit_score` | 1 to 5 | |
| `effort_hours` | number | Estimated hours to a complete submission |
| `expected_value` | text | Probability-weighted estimate with stated assumptions, or "not estimated" |
| `readiness_gate_met` | boolean | From the diagnostic |
| `go_no_go` | enum | go, no_go, hold, with reason |
| `owner` | text | |
| `next_action` | text | |

Freshness rule: any record with `verified_date` older than 90 days is flagged and hidden from active views until re-verified.

## 2. Relationship record schema

| Field | Rule |
|---|---|
| `person_or_institution` | |
| `role` | program officer, donor, board connector, intermediary, elected official staff, vendor |
| `linked_opportunities` | record ids |
| `connector` | who can introduce, and their relationship |
| `warmth` | cold, aware, met, engaged, champion |
| `last_contact`, `next_step`, `owner` | |
| `notes` | facts only, no speculation about personal matters |

## 3. Go/no-go checklist

Answer all before application work begins.

1. Is the pathway verified within 90 days?
2. Are we eligible on every stated criterion?
3. Is the readiness gate for this layer met?
4. Does the opportunity fund work the board has already approved?
5. Can we carry the cash-flow profile (reimbursement lag, match) with current reserves?
6. Is the reporting burden proportional to the award?
7. Do we have, or can we get, a relationship touch before submitting?
8. Is total concurrent application load within the cap (three per organization per month in the pilot)?
9. What is the expected value against effort hours, and does it beat the next best use of the same hours?
10. What would we learn if declined?

## 4. Case-for-support components (Deliverable 6 of the module)

Maintain each as a versioned block so any application can be assembled from parts.

| Block | Length | Content |
|---|---|---|
| Mission statement | 1 sentence | Who, what change, where |
| Problem statement | 150 words | Need with two cited data points for the served population and geography |
| Organization history | 150 words | Founding, milestones, legal status, leadership |
| Program description | 250 words per program | Activities, participants, frequency, location, staff |
| Theory of change | 1 diagram plus 150 words | Inputs, activities, outputs, outcomes, evidence |
| Outcomes to date | 150 words plus table | Outputs and outcomes, method, time period |
| Beneficiary story | 120 words | Consent obtained, name changed if requested |
| Leadership and board | 60 words per person | |
| Budget narrative | 300 words | Line items, assumptions, indirect approach |
| Organizational budget | table | Current and prior year |
| Program budget | table | Unit cost per participant |
| Sustainability statement | 120 words | Revenue mix today and plan for diversification |
| Equity and community accountability | 120 words | Who leads, who decides, how participants shape the work |
| Evaluation plan | 150 words | Measures, instruments, schedule, who analyzes |
| Partnerships | 100 words | Formal and informal, with letters available |
| Standard attachments | folder | Determination letter, 990s, financials, board list, bylaws, COI policy, W-9, audit or review, letters of support |

## 5. Application calendar template

| Opportunity id | Funder and program | Deadline | Internal draft due | Reviewer | Submitter | Dependencies (registration, letter, budget) | Status |
|---|---|---|---|---|---|---|---|

Rule: internal draft is due seven days before the external deadline; registrations required are listed as dependencies with their own due dates at least 30 days before submission for federal, 21 days for state, 14 days for city and foundation.

## 6. Net-value worksheet for technology and in-kind offers

Net annual value = avoided cost − (implementation hours × loaded rate) − migration cost − added staffing − security and compliance cost − training − expected renewal or post-credit cost − exit cost amortized over expected use.

Record every input with its source. Where a credit expires, model the year after expiration explicitly.

## 7. Revenue-concentration and diversification tracker

| Source category | Trailing 12 months | Share | Restricted or unrestricted | Renewal likelihood | Next-layer target |
|---|---|---|---|---|---|

Trigger a diversification action when the largest source exceeds 40 percent or restricted revenue exceeds 70 percent.