The pipeline
Every address moves through a status pipeline. Update the status every time you touch a record — the tracker is only useful if it reflects reality.
An unanswered record falls back to follow-up needed and re-enters the path. Declined and not applicable are terminal.
| Status | Means | Your next action |
|---|---|---|
| not_started | Nobody has looked at this address | Research the current occupant |
| researching | Identifying the occupant and contact information | Fill in the occupant and contact fields |
| contacted | First outreach sent | Set first_contact_date, log the channel in the notes |
| awaiting_response | Waiting on a reply | Set next_follow_up_date, roughly two weeks out |
| follow_up_needed | The follow-up date passed with no reply | Send the follow-up, then re-date it |
| interested | Positive response, not yet committed | Send the plaque details, arrange the next step |
| approved | The occupant agreed to a plaque | Hand off to plaque production |
| declined | The occupant said no | Log the reason in the notes. Do not contact them again |
| not_applicable | Building demolished, vacant, or no viable contact | Log why, so nobody repeats the search |
Interest level — high, medium, low, none, unknown — is separate from status. Use it to prioritise follow-ups.
Research workflow
Use Research Mode — the button in the tracker header — to step through not_started records one at a time. For each address:
Find out who is there now
Look the address up on Google Maps or OpenStreetMap. Who occupies it today?Describe the occupant
Fill incurrent_occupant_name,current_occupant_type— business, residential, office, public, vacant or demolished — andproperty_type.Find a way to reach them
contact_email,contact_phone,contact_website, and a namedcontact_personwherever one can be found.Record where it came from
Setdata_sourceto one of google_maps, osm, manual_research, site_visit, phone_call or website.Move the status
researchingwhile the record is incomplete,contactedonce outreach has actually been sent.
Contact guidelines
- Lead with the mission: memory, education, neighbourhood history.
- Be concrete about the plaque: size, placement, and the cost to them — which is none.
- Two follow-ups, then stop: one after about two weeks, a second after about four, and no more unless they respond.
- Log every interaction in
outreach_notes, with a date prefix. - A declined is final. Respect it.
2026-08-09: Called, spoke with office manager, sending info PDF.Data hygiene
- Dates go in date fields in ISO format —
YYYY-MM-DD. - Notes are append-only. Never delete history; add new lines on top.
- Export a CSV backup — the Export button, or
/api/outreach/export— before any bulk edit. - Never commit personal contact data to the public repo beyond what the tracker’s data store already holds.
Weekly rhythm
Small consistent batches beat heroic sprints. Five to ten addresses in a session is a good week.
Check the stats bar
Open the tracker. Thefollow_up_neededcount is your queue.Clear the follow-ups first
Then continue research onnot_startedrecords.Report back
Note blockers or interesting responses on the project task board — see the task tracking guide.
Where the code lives
The tracker lives at /admin/outreach. Both the page and the underlying /api/outreach endpoints are password-gated server-side — ask the maintainer for access.
| Piece | Path |
|---|---|
| UI | src/app/admin/outreach/page.tsx and src/app/components/outreach/ |
| API | src/app/api/outreach/ — data and CSV export |
| Data model | src/lib/types/outreach.ts |
| Source list | Outreach/Jewish Business Outreach - For Json.csv |