Broadband Grant Application Drafter

Converts project facts (applicant info, service area, technology choice, deployment timeline, cost estimates) into a structured grant application narrative for federal and state broadband funding programs. Outputs a DRAFT for applicant, engineering, and legal counsel review before submission.

intent

Use this skill when an ISP, rural electric cooperative, municipality, tribal organization, or broadband office is drafting a grant application narrative for federal or state broadband funding. The skill walks you through structured intake (one question at a time) to collect applicant qualifications, service area definition, technology selection, deployment timeline, costs, and affordability commitments. It assembles these facts into a DRAFT narrative document labeled for review before any submission. Deploy this when you need to generate application text that aligns with BEAD, USDA ReConnect, E-Rate, FCC Emergency Connectivity Fund, or state broadband office program requirements.

inputs

Program eligibility and requirement rules (referenced by name)

• BEAD (Broadband Equity Access Deployment): fiber-first deployment, NTIA Fabric location definitions, state subgrantee workflow
• USDA ReConnect (Round 4+): rural service areas under 400,000 people, unserved confirmation (less than 25/3 Mbps), applicant entity types
• E-Rate: eligible schools and libraries only, connectivity and equipment funding (not infrastructure build-out)
• FCC Emergency Connectivity Fund: eligible schools and libraries, temporary funding window
• State broadband programs: vary by state; requires lookup of state office program terms

Applicant-provided data

• Legal entity name and type (ISP, cooperative, municipality, tribal government, non-profit)
• State of incorporation or organization
• FCC Registration Number (FRN) and current SAM.gov registration status (verify before draft assembly)
• Years of broadband deployment experience and prior federal/state grant history
• Current service territory (states and counties)
• Geographic area to be served (county, census tract names, or specific communities)
• Number of locations to be served (unserved/underserved confirmation method and data source)
• Proposed technology (FTTP, FWA, hybrid fiber-wireless, cable, or other)
• Planned download/upload speeds and scalability to 1 Gbps symmetric
• Deployment phase structure and milestone timeline
• Permitting and workforce strategy
• Total project capital cost and cost breakdown by category
• Operating cost estimate (Year 1 O&M)
• Matching funds amount, source, and commitment status
• Grant amount requested
• Subscriber pricing plan and low-income affordability program (ACP successor, Lifeline, or state equivalent)
• Digital equity and adoption barrier analysis

External connections and registrations

• SAM.gov registration (System for Award Management): applicant must have active registration and current DUNS number; required for all federal funding; check status at https://sam.gov
• FCC Registration Number (FRN): required for BEAD and ReConnect applicants; verify current registration
• NTIA Fabric (BEAD): applicant must confirm unserved/underserved location status against the National Telecommunications and Information Administration's broadband serviceable location fabric; access via https://broadbandmap.fcc.gov or state broadband office portal
• FCC National Broadband Map: alternative data source for confirming broadband availability; https://broadbandmap.fcc.gov
• State broadband office: for subgrantee applications under BEAD or state-specific programs, coordination with state office on eligibility, timelines, and submission portal

Environment and context assumptions

• Applicant has not yet submitted to any grant portal; this skill produces draft narrative only
• No government system integration or form filing occurs within this skill
• Applicant has capacity to provide engineering, cost, and affordability data (in-house or via consultant)
• Network is greenfield or underserved expansion (not maintenance of existing network)

procedure

1. Identify the grant program

   • Input: Ask the user which grant program applies (BEAD, USDA ReConnect Round 4+, E-Rate, FCC Emergency Connectivity Fund, or state program name and state)
   • Input: Capture application deadline
   • Input: Confirm whether this is a direct federal application or subgrantee application to a state broadband office
   • Output: State the program's key eligibility rules explicitly (entity types, location definitions, technology requirements, funding scope). Flag any eligibility questions the applicant must confirm before proceeding.
   • Decision: If applicant entity type does not match program eligibility, stop and escalate; do not proceed to narrative draft until eligibility is confirmed.

2. Collect applicant profile

   • Input: Capture legal entity name, type (ISP, co-op, municipality, tribal government, non-profit)
   • Input: Capture state of incorporation or organization
   • Input: Capture FCC Registration Number (FRN)
   • Input: Verify SAM.gov registration status; ask user to confirm registration is current and provide DUNS number
   • Input: Capture years of broadband deployment experience
   • Input: Capture any prior federal or state broadband grants received (program name, award amount, completion status)
   • Input: Capture current service territory (states and counties currently served)
   • Output: Applicant profile summary for narrative Section 1
   • Decision: If SAM.gov registration is not current or FRN is not provided, flag as blocker; do not proceed to draft until verified.

3. Define service area

   • Input: Capture geographic area to be served (county name(s), census tract(s), or specific community name(s) and state)
   • Input: Capture total number of locations to be served (use program-specific definition: BEAD uses NTIA Fabric locations; ReConnect uses addressable locations in unserved areas; E-Rate uses eligible school/library count)
   • Input: Confirm unserved/underserved status: ask which data source was used to determine eligibility (NTIA Fabric, FCC National Broadband Map, state challenge data, or independent broadband speed test survey)
   • Input: Capture current maximum download and upload speeds available at the proposed service area locations
   • Input: Identify any anchor institutions in the service area (schools, libraries, healthcare facilities, public safety)
   • Output: Service area definition with unserved/underserved confirmation summary
   • Decision: If unserved/underserved status has not been confirmed against a program-required data source, flag as a prerequisite blocker; provide guidance on which data source the program requires and ask user to complete verification before proceeding to draft.

4. Select technology

   • Input: Capture proposed technology type (fiber-to-the-premises FTTP, fixed wireless access FWA, hybrid fiber-wireless, cable, or other)
   • Input: Capture planned broadband speeds to be delivered (download and upload); confirm against program minimums (typically 100/20 Mbps for BEAD and ReConnect; higher for E-Rate)
   • Input: Confirm scalability: can the network be upgraded to 1 Gbps symmetric download/upload without replacing core infrastructure?
   • Input: Capture last-mile topology (individual fiber drops, shared backbone with distribution to CPE, wireless to fixed outdoor antenna, etc.) and middle-mile access plan (dedicated fiber, dark fiber lease, wireless backhaul, carrier fiber purchase, etc.)
   • Output: Technology summary for narrative Section 3
   • Decision: For BEAD applications, confirm that fiber is proposed. If alternative technology is proposed, require applicant to provide specific technical justification (e.g., "fiber deployment on this terrain exceeds cost per location threshold; FWA alternative deployed with documented speed parity" with engineering documentation). Do not draft alternative-technology justification without this basis.
   • Edge case: If technology selection creates cost per location significantly above typical range for region/technology type (flagged in step 6), raise question now; may require technology adjustment.

5. Capture deployment plan

   • Input: Capture phase structure (number of deployment phases, geography covered per phase, and sequencing rationale)
   • Input: Capture milestone schedule with target dates: engineering complete, permits obtained, construction start, 25% locations activated, 50% locations activated, 100% locations activated, project closeout
   • Input: Capture permitting strategy: make-ready process (overhead utility coordination), pole attachment strategy, right-of-way (ROW) coordination, tribal land permitting if applicable
   • Input: Capture workforce plan: in-house construction crew versus contracted third-party, workforce development commitments if required by program
   • Output: Deployment plan narrative and milestone table for Section 4
   • Edge case: If deployment timeline extends beyond program grant period (typically 5 years from award), flag as risk and ask for contingency narrative or timeline compression plan.

6. Build cost structure

   • Input: Capture total estimated project capital cost
   • Input: Calculate cost per passing (total capex ÷ total locations to be served); compare against typical cost per location for technology and region (FTTP typically $1,500 to $3,500 per location in rural areas; FWA $800 to $2,000)
   • Decision: If cost per location is outside typical range, ask applicant to confirm or provide justification narrative (e.g., "terrain is mountainous, requiring aerial deployment at premium cost"; "limited footprint increases per-location cost but is justified by anchor institution anchor tenant revenue")
   • Input: Capture cost breakdown by category: civil construction (trenching, aerial, conduit), materials (fiber, electronics, CPE), engineering and design, permitting and ROW, project management, contingency reserve (recommend 10-15%)
   • Input: Capture Year 1 operating and maintenance cost estimate
   • Input: Capture matching funds: amount, source (state, local, private partner, applicant cash), and current status (committed with signature, anticipated pending board approval, etc.)
   • Input: Capture total grant amount requested (total cost minus matching funds)
   • Output: Budget narrative and summary table for Section 5, labeled "PRELIMINARY ESTIMATES"
   • Edge case: If matching funds status is "anticipated," flag as condition precedent; applicant must obtain commitment before submission.
   • Edge case: If applicant requests 100% grant funding with no matching funds, flag program requirement (BEAD and ReConnect typically require or strongly encourage matching funds) and ask for matching funds strategy.

7. Document affordability and adoption plan

   • Input: Capture subscriber pricing plan: monthly rate for qualifying broadband service at program-required speeds (e.g., "99 locations will receive 100/20 Mbps service at $59.99/month for standard subscriber")
   • Input: Capture low-income affordability program: ask whether applicant will participate in ACP successor program (Affordable Connectivity Program), Lifeline, state equivalent program, or proprietary reduced-rate offering; capture rate and eligibility criteria for each
   • Input: Capture digital equity measures: device access programs (applicant provides CPE at discount or free to low-income subscribers?), digital literacy partnerships (library, school, community college partnerships for training?), community outreach plan (how will applicant inform residents of service availability and affordability options?)
   • Input: Capture adoption barrier analysis: identify populations in service area that face barriers beyond physical access (cost, device access, digital skills, language, accessibility needs); describe how project addresses each barrier
   • Output: Affordability and adoption narrative for Section 6
   • Edge case: If applicant proposes no low-income affordability program, flag program requirement (BEAD and most state programs mandate affordability plan) and require applicant to propose ACP or equivalent participation.

8. Assemble DRAFT narrative

   • Input: All data from steps 1-7
   • Process: Generate structured Markdown document with Executive Summary, Sections 1-6 (Applicant Qualifications, Project Area and Need, Technical Approach, Deployment Plan, Project Budget, Affordability and Adoption Plan), Open Items checklist, and Reviewer Sign-Off block
   • Output: DRAFT document labeled with program name, applicant name, application deadline, "DRAFT , Requires Applicant, Engineering, and Legal Counsel Review", and date prepared
   • Flag all information gaps with [INFORMATION NEEDED , DO NOT SUBMIT WITH THIS PLACEHOLDER]
   • Label all cost figures "PRELIMINARY ESTIMATES"
   • Include disclaimer: "This narrative is a DRAFT. Do not submit to any grant portal or share with the funding agency until all open items are resolved and all sign-offs are obtained."
   • Output location: Return as Markdown text file or formatted document; applicant is responsible for storage and version control
   • Edge case: If any blocker is unresolved (SAM.gov registration, unserved/underserved status, eligibility confirmation, BEAD fiber-first justification), insert [BLOCKER , CANNOT DRAFT UNTIL RESOLVED] and list all blockers at top of document; do not output full narrative until blockers are cleared.

decision points

Program eligibility verification (Step 1)

• If applicant entity type does not match program: Stop. Flag ineligibility. Ask applicant to confirm with program office before proceeding.
• If application deadline is within 2 weeks: Escalate urgency. Advise applicant that intake process must compress; some steps may require parallel work.
• If subgrantee application: Direct applicant to state broadband office program terms and submission portal; confirm state-specific data sources and timeline alignment with state consolidation deadline (BEAD).

SAM.gov and FRN verification (Step 2)

• If SAM.gov registration is not current: Blocker. Applicant must register or update at https://sam.gov before draft can be assembled. Do not proceed.
• If FRN is not provided: Blocker for BEAD and ReConnect. Applicant must obtain FRN from FCC or confirm with state office before draft can proceed.

Unserved/underserved confirmation (Step 3)

• If applicant has not confirmed unserved/underserved status: Blocker. Provide guidance on required data source per program (BEAD requires NTIA Fabric; ReConnect accepts NTIA Fabric, FCC National Broadband Map, or state-validated data; E-Rate requires school/library eligibility verification). Ask applicant to confirm and return with findings before draft assembly.
• If current speeds available at locations exceed program definition of unserved (e.g., 100+ Mbps in claimed unserved BEAD area): Escalate. Confirm applicant has accurate speed data; if confirmed, location may not be eligible. Discuss impact on scope or ask for challenge/remediation process guidance from state office.

Technology selection (Step 4)

• For BEAD applications: If fiber is not proposed, require applicant to provide technical justification for alternative technology. Without documented justification, do not draft narrative; ask for engineering memo explaining why fiber is not viable and why alternative meets program speed/scalability requirements.
• If proposed speeds fall below program minimum: Escalate. Ask applicant to confirm technology selection meets program requirement (e.g., 100/20 Mbps for BEAD). If not, flag as scope change and request justification or technology revision.
• If cost per location is >30% above regional median for technology type: Flag. Ask applicant to confirm cost estimate or provide terrain/permitting justification. Cost outliers may trigger reviewer scrutiny or funding uncertainty.

Deployment timeline (Step 5)

• If project completion extends beyond grant period (typically 5 years from award): Flag as risk. Ask applicant whether timeline can be compressed or whether phased approach allows completion of majority within grant period. May require narrative addressing contract performance contingency.
• If critical path milestone (permits) is delayed or uncertain: Flag. Ask applicant for contingency timeline and explanation of permit dependencies (tribal, state, local).

Matching funds (Step 6)

• If applicant has no matching funds: Flag program requirement. Ask whether funds can be secured (state, local, private partner, applicant commitment). If not, narrative must justify 100% federal funding request and applicant risk of project non-completion.
• If matching funds status is "anticipated" (not committed): Flag as condition precedent. Narrative must note that grant award is contingent on matching funds commitment. Applicant must obtain board-approved resolution or signed funding agreement before submission.

Affordability program (Step 7)

• If applicant proposes no low-income affordability program: Blocker for BEAD; flag for most state programs. Require applicant to select and commit to ACP successor program, Lifeline, or equivalent. Do not draft narrative without affordability plan.
• If proposed low-income rate exceeds affordability threshold (typically $15-25/month for 100/20 Mbps or better after subsidies): Flag. Ask applicant whether ACP or state program will cover gap or whether applicant will lower rate.

Blocker resolution (Step 8)

• If any blocker remains unresolved at draft assembly, insert [BLOCKER] header at top of document and list all unresolved items with responsible party and required action. Do not output narrative sections that depend on blocker resolution; output only the Executive Summary with disclaimer and blocker list.

output contract

Deliverable format: Structured Markdown document with the following guaranteed sections:

# Broadband Grant Application Narrative ,  DRAFT

**Program:** [program name from Step 1]
**Applicant:** [legal entity name from Step 2]
**Application deadline:** [date from Step 1]
**Status:** DRAFT ,  Requires Applicant, Engineering, and Legal Counsel Review
**Prepared:** [current date]

---

## Executive Summary

[3, 5 sentence overview: who the applicant is, where the project is, how many locations will be served, what technology will be deployed, and what the total project cost and grant request are.]

## Section 1: Applicant Qualifications

[Narrative: legal entity type, incorporation state, FRN, years of experience, prior grant history, current service territory, technical capacity.]

## Section 2: Project Area and Need

[Narrative: geographic scope, number of unserved/underserved locations, current speed availability, data source and methodology used to confirm unserved/underserved status per program requirement, anchor institutions, unmet need.]

## Section 3: Technical Approach

[Narrative: technology selected, planned speeds, network architecture diagram or textual description, scalability to 1 Gbps symmetric, middle-mile access strategy.]

*For BEAD applications: explicit fiber-first confirmation OR alternative-technology exception justification with documented technical basis.*

## Section 4: Deployment Plan

[Narrative: phased deployment structure, milestone timeline, permitting strategy, workforce and