Local Impact Planner — High-Benefit Local Investment Priorities

{{ title }} The location name for this plan (what the generator returned or inferred).

🔗 Plan link: {{ brandedLinkUrl }} not provided • Saved on this device: {{ new Date(lastUpdated).toLocaleString() }} The “plan link” is the stable key used to reopen the same plan via the URL. The timestamp shows when this device last saved it.

🎯 Ranked investment opportunities These are the “what to fund first” options. They’re ranked by expected social return and may be gently re-ordered on this device based on what you open.

This card summarizes one intervention: why it fits locally, what levers enable it, key blockers + mitigations, expected timeframe, and what to measure. Clicking the card stores a “view” on this device to personalize ordering.

Domain: {{ o.domain }} The policy/program area this intervention belongs to (e.g., health, housing, energy, education). • {{ o.bcr_from_framework }} A benefit–cost style indicator or ranking label from the underlying framework. Use it as directional guidance, then validate locally.

Why this fits {{ title }}:

Local anchors and context cues that explain why this intervention is plausible and high-leverage in this specific place.

{{ r }}

Core levers:

The main mechanisms that make this work (policy levers, program design choices, operational moves).

{{ c }}

Enablers:

What needs to be true for this to go smoothly (institutions, data, procurement, staffing, partnerships).

{{ e }}

Blockers & mitigations:

Likely failure modes and practical ways to reduce risk (sequencing, pilots, governance, comms, contracting, safeguards).

{{ b.blocker }}: {{ b.mitigation }}

Timeframe: {{ o.timeframe }} • Footprint: {{ o.implementation_footprint }} “Footprint” is the rough implementation scope (e.g., citywide, corridor-based, targeted to a subgroup, phased rollout).

Monitor via: {{ o.monitoring_metrics.join("; ") }} Suggested indicators to track progress and catch issues early (pick a small set you can measure reliably).

What to do next: choose 1–2 top cards, validate assumptions with local stakeholders, then use the 100-day list to start moving.

🗓️ First 100 days Concrete actions that can be started or completed within roughly 100 days. Treat this as your launch checklist.

Focus on decisions, scoping, pilots, procurement prep, and “definition of done” so execution doesn’t stall later.

Task	Owner	Dependency	Done when…
{{ t.task }}	{{ t.owner }}	{{ t.dependency }}	{{ t.definition_of_done }}

How to use: start with the top 3 tasks, assign an owner, and agree on the “done when…” line in one meeting.

📈 12–24 month roadmap Quarter-by-quarter milestones and decision gates over the next 12–24 months (what must be true before scaling).

Use this to sequence work: pilot → evaluate → scale (with explicit gates so you can pause, adapt, or expand responsibly).

Quarter	Milestone	Decision gate
{{ r.quarter }}	{{ r.milestone }}	{{ r.decision_gate }}

Decision gates are your guardrails: if a gate condition isn’t met, adjust scope, improve delivery capacity, or revisit the ranking.

💰 Budget scenarios How the plan changes under different funding envelopes: minimal, moderate, or donor-backed.

These are framing options for budget conversations (not line-item accounting). Use them to align on ambition and constraints.

Shoestring

Moderate

Donor-backed

🤝 Delivery & stakeholders Who leads, who delivers, how communities are engaged, and how procurement is coordinated.

This is your “who does what” starting map. Use it to identify missing roles early.

Government leads: {{ delivery.gov_leads.join(", ") }} The public agencies or offices best positioned to own outcomes and coordinate implementation.

Delivery partners: {{ delivery.delivery_partners.join(", ") }} Organizations that can execute pieces of the plan (operators, NGOs, universities, utilities, private sector, etc.).

Community engagement: {{ delivery.community_engagement }}

Procurement & coordination: {{ delivery.procurement_coordination }}

Tip: if procurement is unclear, start with a lightweight pilot contract while you design the scaled pathway.

⚠️ Risks & mitigations Key execution risks and how they can be mitigated, phased, or governed.

A plan that acknowledges risk is easier to fund, approve, and deliver. Use mitigations as “pre-mortem” actions.

{{ r.risk }}: {{ r.mitigation }}

Practice: pick the top 2 risks and assign owners + early warning signals this week.

🧩 Assumptions & framework references Key assumptions behind the plan, plus references back to the benefit–cost framework used to shape the ranking.

Treat assumptions as “things to verify.” If one is wrong, update the ranking rather than forcing the plan.

Assumptions:

{{ a }}

Framework references:

Intervention	Project / label	BCR / rank
{{ f.intervention }}	{{ f.project_or_label }}	{{ f.bcr_or_rank }}

How to read this: it’s a provenance trail—use it to sanity-check why an item appears and how it’s positioned.

Generates a print-ready PDF with your snapshot, rankings, and the two action tables.

Uses your device share sheet when available, otherwise copies the link to your clipboard.

Permalink: Click to copy. Opening this link auto-loads the same plan. (copied on click)

{{ title }} mdi-help-circle-outline The location name for this plan (what the generator returned or inferred).

🎯 Ranked investment opportunities mdi-help-circle-outline These are the “what to fund first” options. They’re ranked by expected social return and may be gently re-ordered on this device based on what you open.

{{ o.intervention }}

🗓️ First 100 days mdi-help-circle-outline Concrete actions that can be started or completed within roughly 100 days. Treat this as your launch checklist.

📈 12–24 month roadmap mdi-help-circle-outline Quarter-by-quarter milestones and decision gates over the next 12–24 months (what must be true before scaling).

💰 Budget scenarios mdi-help-circle-outline How the plan changes under different funding envelopes: minimal, moderate, or donor-backed.