NSF 26-508: TechAccess: AI-Ready America

NSF 26-508: TechAccess: AI-Ready America

TechAccess: AI-Ready America is a National Science Foundation solicitation that combines federal AI workforce policy with state-level readiness, workforce development, and practical AI adoption support. It is not a single project grant. It is a structured deployment program built around three components: State/Territory Coordination Hubs, a National Coordination Lead, and AI-Ready Catalyst Award competitions. The publicly posted solicitation is specifically identified as NSF 26-508, and it was posted on March 25, 2026.

This page focuses on the Coordination Hub competition in the published solicitation, which is the piece that opens directly to state, territory, and DC-level entities that can coordinate local AI readiness programs. If you are thinking about the National Coordination Lead or future Catalyst programs, this page gives you where to watch, but the core mechanics and materials below apply to the part of the program where most institutions will apply first.

Key details at a glance

What this opportunity is and what it is not

The solicitation is best understood as a capacity and coordination program, not a conventional research award.

It supports states and territories in building infrastructure for AI readiness across education systems, workforce pathways, small business support, and public services. The solicitation explicitly frames this as more than classroom AI literacy: it is designed to include community organizations, local governments, public-serving entities, and workforce and business ecosystems.

So, what does this mean in practical terms?

• It is not an ideal fit if your plan is a single lab prototype with little partnership mechanism.
• It is a strong fit if your team can convene a broad state-scale network and operationalize training, deployment support, and measurable AI adoption outcomes.
• It is not just grant money for research output; it is money to move toward statewide capability.
• It is not a grant where letters of support can replace evidence of operational readiness. The program expects explicit planning around coordination, partnerships, and execution.

If your organization is mostly asking, “Can we get a large grant to fund one AI experiment?” this is probably not that mechanism. If your organization asks, “Can we run a durable program to scale AI readiness and workforce outcomes across a territory?” it is likely aligned.

For applicants in 2026 and early 2027, this matters because the solicitation is staged in rounds and ties readiness milestones to national learning across states. It is not a one-shot competition where all applicants compete in one cycle only.

Why this is a 2026/2027 candidate

A lot of opportunities are still posted after their effective window has passed. This one has explicit future-cycle dates and therefore remains relevant to applicants targeting 2026 and 2027.

The published schedule is:

• Round 1 LOI: 2026-06-16; Round 1 full proposal: 2026-07-16
• Round 2 LOI: 2026-12-15; Round 2 full proposal: 2027-01-15
• Round 3 LOI: 2027-06-01; Round 3 full proposal: 2027-07-01

The 2026 posting date is recent, and these dates show multiple entry points. If your organization misses round 1, the program still keeps round 2 and 3 active. This is especially relevant for state systems that need a year to line up internal approvals, partner agreements, and evidence for AI readiness work.

The solicitation states support through three rounds and the possibility of one extra extension year for successful Coordination Hubs that demonstrate ongoing need as they transition from NSF support.

Who this is for (and who it is for less)

Because AI readiness spans many sectors, the best-fit organizations are those that can coordinate across boundaries.

Strong fit examples

• State or territorial entities that can convene higher education, workforce systems, and local industry around AI adoption goals.
• Public or quasi-public institutions with access to workforce programs, extension systems, or regional innovation networks.
• Organizations with prior experience in statewide coalition-building, training design, or sector-specific deployment.
• Teams that can show measurable pathways for small business support, workforce skilling, or public-sector modernization.

Weaker fit examples

• Applicants focused only on one research topic with no cross-sector implementation plan.
• Teams with no partner network and no mechanism to scale beyond one campus/one department.
• Proposers expecting to submit a standard grant-style project with no collaboration commitments.
• Organizations whose primary objective is branding and not statewide coordination outcomes.

Geographic scope

The stated mechanism covers states, the District of Columbia, and U.S. territories through a Coordination Hub model, so a regional or state-level anchor with clear statewide planning is essential. Purely national nonprofits without clear state/territory delivery logic will be harder to position.

Eligibility and proposal gates

The solicitation routes you to NSF rules and states that unaffiliated individuals are not eligible. That means you must route through an eligible proposing organization.

Core eligibility constraints

• Proposers must fall within NSF proposer categories in the PAPPG Chapter I.E.
• Unaffiliated individuals are not eligible.
• Who may serve as PI: no stated restrictions or limits in this solicitation.
• One proposal per institution is the limit for Coordination Hubs.
• Letters of intent are required before full proposal submission.

Practical implication of the one-proposal rule

Because one institution can submit only one Coordination Hub proposal, you cannot hedge with competing concepts from the same organization. This is an early strategic decision:

1. define one clear model,
2. ensure internal signoff,
3. align stakeholders before LOI submission.

If your organization cannot coordinate around one proposal, separate the concepts first internally and submit only the one with best partnership depth.

Funding structure and where the money goes

The explicit funding model matters because many teams overestimate flexibility.

• Each Coordination Hub award is around $1M per year.
• The default duration is up to 3 years.
• There is a possibility of one additional year if a strong transition case is made.
• Estimated total program budget across all hubs is $168M–$224M.

This is intentionally state-level funding for coordinated capacity, not a microgrant.

What you should budget for

The proposal should fund activities tied to the five responsibility areas named in the solicitation:

1. Statewide coordination and planning,
2. Workforce and training support,
3. AI adoption support with partner institutions,
4. partnerships in priority sectors, and
5. knowledge-sharing systems and scaling.

The solicitation also emphasizes practical learning paths, including project-based work and sector-specific AI skills support. That means a competitive plan should tie personnel costs and activities to actual deployment outputs, not simply administrative overhead.

What budget assumptions are not safe

• Do not assume voluntary committed cost sharing is allowed.
• Do not plan on unlimited indirect cost flexibility; proposals must follow NSF rules.
• Do not assume letters of support can substitute for required data and planning materials.

Application process and required materials

The process is simple to describe and easy to miss if not sequenced correctly:

Step 1: Prepare LOI package

The Letter of Intent is required.

What the solicitation requires in the LOI:

• proposal title format aligned to the program,
• full PI/co-PI and senior personnel details with affiliations,
• participating organizations list,
• one-page synopsis describing the proposed work.

You should not include extra narrative you are not asked to include. The NSF language explicitly says supplements are not to be treated as approval gates and sets a clear purpose: review planning, not pre-evaluation of a full proposal.

Step 2: Build full proposal components

After LOI acceptance, proposals are submitted via Research.gov or Grants.gov unless another method is specified.

Required proposal structure (as presented in the solicitation) is strict:

• Section 1 – Vision and Approach to Responsibilities
• Section 2 – Organizational Background, Team Expertise, and Partnership Rationale
• Section 3 – Current State of AI Planning and Coordination
• Section 4 – Work Plan, Milestones, and Performance Metrics
• Section 5 – Resource Mobilization and Leveraging Additional Support

Missing any of these is likely a serious compliance failure.

Mandatory supporting materials

The solicitation allows only permitted supplemental materials. Key required elements include:

• Letters of collaboration from all identified partners,
• Data Management Plan,
• Mentoring Plan only if postdocs or graduate students are funded,
• No additional letters of support beyond what is explicitly requested.

This is where many applicants fail: they treat collaboration letters as broad evidence pieces, but here the requirement is specific and traceable.

Submission method details

For collaborative proposals that involve multiple organizations in separate submissions, NSF directs use of Research.gov for those collaborative setups. If your project requires multiple organizations, plan platform choice early to avoid portal conflict.

Proposal strategy: how to make this competitive

This solicitation is judged by NSF merit review plus program-specific criteria.

Align with NSF review logic

At minimum, the proposal should show:

• a clear statewide vision and coordination mechanism,
• evidence of convening capacity,
• mapping between regional need and proposed intervention,
• measurable milestones and reporting pathways,
• resource mobilization beyond NSF seed support.

Without these, teams look like another planning document rather than a launch plan for regional AI readiness.

Build a partnership architecture first

The requirement for letters of collaboration is not decorative. It is a quality control instrument.

Before writing the proposal narrative:

1. Map your formal partners (education, workforce, industry, local agencies).
2. Define what each partner contributes operationally.
3. Draft partner letters with concrete commitments, not generic endorsements.
4. Integrate these commitments into your milestones section.

That sequence reduces late-stage proposal edits and strengthens review credibility.

Use realistic performance metrics

The solicitation explicitly recommends reporting outcomes such as:

• people trained,
• small business and government entities assisted,
• statewide convenings held,
• AI Deployment Corps participation,
• organizations receiving technical assistance.

If your metrics are missing or purely aspirational, the proposal is difficult to review.

Common mistakes and corrections

Mistake: Ignoring round structure

Some teams build for round 1 and lose the strategic opportunity to re-align for round 2/3 if rejected. Build a reusable framework that only changes priorities and partner sequence by round.

Fix: keep your core architecture but adapt timeline, sector focus, and partner sequencing by round.

Mistake: Missing LOI formatting and timeline

Because LOI is required and includes content constraints, teams sometimes treat LOI as an informal note.

Fix: create an LOI checklist and lock deadlines (LOI + proposal) into internal calendars with at least two internal reviews.

Mistake: Treating this as a standard individual research grant

This solicitation is not about one university lab or a single prototype.

Fix: frame outcomes as statewide coordination with measurable deployment and workforce pathways.

Mistake: Underestimating evidence burden

Even though this is not a science-output-only call, NSF reviews still expect evidence of capacity and execution.

Fix: include case-based indicators from existing activities: existing convenings, prior workforce programs, and partner implementation records.

Mistake: Overreliance on generic recommendation letters

The solicitation requires specific collaboration documentation and does not reward ambiguous letters.

Fix: include concrete partner roles and contribution commitments in letters.

Practical planning timeline (recommended)

If you want to avoid missing the window, plan backward from a real deadline.

12-week execution model

• Weeks 1–2: confirm proposer eligibility and internal authorization; map who can sign and submit.
• Weeks 3–4: lock scope (hub responsibilities), gather baseline state/territory AI planning context.
• Weeks 5–6: assemble partners and draft letters of collaboration.
• Weeks 7–8: prepare LOI and pre-brief internal review.
• Weeks 9–10: draft sections 1–5 with measurable outcomes and clear milestones.
• Weeks 11–12: finalize budget and submission compliance checks.

If using round 2 or 3, shift this calendar backward from your target due date and include a review window before submission deadlines.

FAQ

Is this only for universities?

No. The opportunity is centered on state and territory coordination systems, not one institution alone.

Do international institutions or individuals apply?

Unaffiliated individuals are not eligible. Institutional eligibility follows NSF PAPPG Chapter I.E.

Is the deadline a single date?

No. The solicitation includes multiple rounds with LOI and full proposal dates in 2026 and 2027.

Are cost-sharing commitments required?

No. Voluntary committed cost sharing is prohibited.

What is the maximum award duration?

Base support is up to three years with a possible one-year extension.

Is there an explicit amount per award?

Each Coordination Hub award is described as up to $1M/year for the three-year duration.

Official links and what to track next

For exact submission details and the latest instructions, use the official solicitation page and NSF systems links.

• Official opportunity page: https://www.nsf.gov/funding/opportunities/techaccess-ai-ready-america/nsf26-508/solicitation
• NSF PAPPG (for cross-checking submission rules): https://www.nsf.gov/policies/pappg
• NSF proposal submission portals: Research.gov and Grants.gov
• Program contact email (from official page): [email protected]

Before submitting, verify all of the following against the current solicitation page:

1. LOI and proposal due dates for your intended round.
2. Page limits and section structure.
3. Required supplemental materials.
4. PI and institutional authorization details.
5. Whether the Coordination Hub competition remains active for your geography.

Final take for applicants

If your goal is a one-off research award, this solicitation will feel too broad. If your goal is to coordinate AI readiness across a state or territory and run measurable workforce and adoption support, this is one of the first major federal channels in 2026/2027. The competition’s staged rounds and explicit support per Coordination Hub create a practical path for organizations that need one well-prepared, multi-sector proposal rather than multiple fragmented applications.

A competitive applicant should treat this as a governance-plus-implementation project:

• define one strong statewide mission,
• formalize partners,
• submit a compliant LOI,
• and then build a full proposal where every section is performance-oriented.

That sequencing is what turns a large federal concept into an awardable plan.