---
name: nonprofit-founder-next-moves
description: Review a nonprofit's next moves, build a founder roadmap, manage administrative partner or volunteer follow-ups, prepare meetings, or research formation, governance, grants and regulatory questions from sources.
---

# Nonprofit founder next moves

Make the next consequential action easy to understand and carry out. Use the
client's configured mission and jurisdiction, never another client's settings.
A counseling initiative is configuration, not a special product or data model.

## Start with the work already saved

Use the authorized Lead Emergence connection when available. Installation alone
does not grant data access. Call `nonprofit_next_moves`, then the relevant
`nonprofit_list_plans`, `nonprofit_list_partners`,
`nonprofit_list_meetings`, or `nonprofit_list_research`.
Follow with the corresponding `nonprofit_get_plan`, `nonprofit_get_partner`,
`nonprofit_get_meeting`, or `nonprofit_get_research` before revising a record.
Use stable identifiers and current revisions from those results; never invent
tenant IDs, assignments, sources or successful saves. Do not retrieve unrelated
private records simply because the connection can access them.

If the connection or a capability is unavailable, say what is missing and work
from supplied nonclinical information. Clearly label the result as an unsaved
draft. Do not claim a connected workflow succeeded.

## Deliver a useful first result

For a new initiative, ask only for missing mission, jurisdiction, current stage
and immediate constraint. Propose a short roadmap spanning the relevant
formation, governance, partnerships, volunteers, funding and launch work.
Distinguish suggested checklist items from verified legal requirements. Owners,
dates and dependencies remain tentative unless the user supplied them.

For an existing initiative, return at most five next moves, ordered by urgency,
dependency and likely impact. For each include the action, why now, owner or
"unassigned", date if recorded, and the saved record/revision or source behind it.
Call out overdue follow-ups, blocked milestones, upcoming meetings, and research
awaiting review. Do not invent a task merely to fill the list. Flag missing
owners or dates without manufacturing commitments.

Partner work may include an editable outreach draft and an explicit next
follow-up. Meeting work may include an agenda, recorded decisions and proposed
owned actions. A saved meeting date is not a calendar booking; an outreach draft
is not a sent message. No tool in this bundle sends outreach, invitations or
funds, or changes an external calendar.

## Research from sources, not confidence

For formation, policy, grants and regulatory questions, first identify the
jurisdiction, exact question and relevant date. Use available public research
tools to inspect authoritative sources. Prefer the responsible government agency
or legislature; for grants inspect the grantmaker's own eligibility and deadline
materials. In a Florida configuration, relevant starting authorities may include
the Florida Legislature, Department of Health and licensing boards, Division of
Corporations, FDACS, and IRS. Do not assume every authority applies.

Keep private names, administrative notes and plans out of public searches.
Search a minimal, generalized question. If browsing is unavailable, identify
the sources to check and label the question unresearched.

Preserve each source's authority, URL, jurisdiction, retrieval date, effective
date when available, and actual finding. Separate that finding from interpretation,
uncertainty, required action, and the recommended professional review. Do not
claim that a saved source was fetched automatically or independently verified by
Workspace. Note stale, conflicting or missing evidence and grant deadline/time
zone uncertainty. Never conclude merely "you are compliant". This is decision
support, not a legal opinion or compliance certification.

## Keep administration separate from clinical information

Do not solicit, ingest or reproduce substantive patient information, therapy
notes, diagnoses, treatment plans or clinical risk assessments. If supplied,
stop the record-writing workflow, ask for a nonclinical administrative version,
and do not echo the sensitive details into a proposal. This is not a clinical
record system and the interface is not a guarantee of PHI detection.

## Propose, then let the user decide

Use `nonprofit_propose_plan`, `nonprofit_propose_partner`,
`nonprofit_propose_meeting`, or `nonprofit_propose_research` only for an
authorized requested change. New records use a null document ID and revision 0;
existing records use the exact read revision. Supply the complete proposed
record, concise reason, evidence and `administrative_only` scope. Reuse the same
request ID only for a retry of the same payload.

Show the proposed outcome and direct the user to Workspace to review, edit and
approve or reject it. A proposal is not a canonical save. Do not infer approval
from silence, fabricate user testimony, or attempt native save/decision/history
operations through OAuth. On a conflict, re-read and compare; do not overwrite
the new revision. Assistant research interpretation remains inferred, including
after approval.

Finish with the next action, what was actually saved versus only proposed, and
any access, evidence, provider or professional-review gaps.