VA-SPORTS-26A: Amendment Round for Grants for Adaptive Sports Programs for Disabled Veterans and Disabled Members of the Armed Forces

VA-SPORTS-26A: Amendment Round for Grants for Adaptive Sports Programs for Disabled Veterans and Disabled Members of the Armed Forces

The U.S. Department of Veterans Affairs (VA) Adaptive Sports Grant ecosystem has a narrow but important window in 2026 for organizations that already submitted to VA-SPORTS-26. The amendment opportunity at Simpler Grants (VA-SPORTS-26A) is specifically for revising an existing submission, not for new general intake. The official record says applications are open to organizations that successfully submitted under the original opportunity and can apply amendments under the SF424 revision flow.

This is one of those opportunities where the “headline money” and the “current action” are two different things. The underlying VA-SPORTS-26 NOFO states up to $16,000,000 available with a maximum of $750,000 per organization. The amendment window, however, carries its own operational constraints: it is for revisions to those already-in system packages, and late or incomplete revisions are treated differently from a fresh proposal package. If your team missed the original filing and did not submit successfully, this is not the right path.

This page is written as a practical guide for organizations that are already in the process or already past the initial step and now need to decide whether to amend.

At-a-glance details

What this opportunity actually is

If you are new to grant notices, this can be confusing: VA-SPORTS-26A is not a separate program with a fresh pool and fresh topic narrative. It is the post-deadline mechanism tied to VA-SPORTS-26. The underlying record explicitly describes it as an amendment opportunity for organizations that successfully submitted to VA-SPORTS-26, and it specifies that amendment processing follows the SF424 revision path.

In practical terms:

• this is for eligible prior submitters only,
• submission changes need to be done through the standard application portal flow,
• eligibility and program substance remain tied to the same NOFO framework,
• it is bounded by the timeline and review milestones in the original opportunity.

You should therefore treat VA-SPORTS-26A as a narrow operations-focused window, not a “new call for new proposals.”

From a strategy perspective, that changes what you optimize for:

• instead of writing a full grant from scratch, you are correcting, tightening, and sometimes restructuring existing materials,
• application management quality is more about version control and compliance than concept invention,
• the chance to improve competitiveness depends on what was missing and what is still eligible to revise under grant rules.

The description also states that amendments are assessed under the normal review pipeline logic and that revisions after the initial submission deadline cannot change scope or increase requested award amounts by more than 10%. That line is critical. It means this window is for legitimate correction and refinement, not a strategic redirection into a different project model.

Why this matters and who it is for

The Adaptive Sports Grant Program supports adaptive sports and related activities for disabled Veterans and members of the Armed Forces. That includes instruction, participation, competition, training, technical support, and related program operations. The broader VA page reinforces that these programs are designed to improve independence and quality of life through sport and therapeutic activity.

A good fit for VA-SPORTS-26A usually looks like this:

• you already submitted to VA-SPORTS-26,
• your organization is non-federal and capable of delivering adaptive sports programming,
• your team discovered omissions, form errors, document gaps, or compliance problems,
• and you now need a controlled revision that does not materially expand project scope.

A poor fit is often a team that misses the central constraints:

• agencies or organizations outside eligibility expectations,
• no valid successful submission in VA-SPORTS-26,
• revision attempts that attempt major scope expansion,
• or missing operational readiness (UEI/SAM/Grants.gov/VA10091 workflow).

The base NOFO for VA-SPORTS-26 defines major intent and operational eligibility clearly enough to build a simple filter for your team:

• Non-federal eligibility and service experience are central,
• adaptive sports activity history and target population alignment are essential,
• funding awards are one-year in nature and subject to availability,
• and programmatic outputs matter to the VA review process.

This amendment does not create a second chance to define eligibility. It gives a second chance to submit correctly within a strict framework.

Confirmed eligibility and constraints (use this as your pre-submission gate)

Here is the practical eligibility and constraints checklist based on official language and records.

Confirmed eligibility

1. You must have successfully submitted to VA-SPORTS-26.
2. You should be able to complete a revision through the SF424 revision process.
3. Contact path and questions are routed via [email protected].
4. Submission flows are through grants.gov, and the official source points to VA’s grant portal process.

Confirmed constraints for changes

• Do not attempt major scope changes in the amendment package.
• Increases in requested amount are constrained and cannot exceed the published amendment-related cap linked to the original NOFO guidance.
• Late submission rules for the base opportunity still matter because many program systems process revisions against earlier checkpoints.
• Administrative and merit review implications differ if revision quality fails threshold logic.

The base NOFO language is explicit in principle: applications that are not complete or are submitted after deadlines can face ineligibility. For organizations already in the pipeline, that means revisions are about finality and correctness, not flexibility.

What should your organization do before filing the amendment

The base NOFO and VA program site list the required readiness profile for original application, and that still applies for successful revision quality. Use this as a “pre-amendment operations checklist.”

1) Verify your organizational profile and IDs

Before your first revision submission, confirm all of the following are active and consistent:

• EIN,
• UEI,
• active SAM registration,
• customer engagement portal form requirements (VA10091 pathway referenced in VA program materials),
• all legal entity names consistent across systems.

If this was handled during the base submission, verify it again. Mismatches after initial upload are a common source of administrative rejection and can make a revised submission fail before merit review.

2) Re-open your base NOFO and list “fixes only”

Use the VA-SPORTS-26 NOFO as your control document. The NOFO gives the definitions, eligibility framework, submission expectations, and reporting obligations. Build your amendment list by class:

• missing attachments,
• missing signatures,
• inconsistent budget logic,
• incorrect category or program language,
• compliance-related omissions in administrative sections,
• evidence gaps in organizational capacity.

Keep this list bounded. If it becomes a new narrative, it is likely outside amendment scope.

3) Map each fix to a field and evidence type

For each issue, identify:

• the specific SF424 field / package component,
• the file name convention,
• proof evidence needed,
• whether the fix changes only format or also budget logic.

4) Maintain a submission ledger

The strongest applicants keep a mini ledger with:

• file version IDs,
• submission date/time,
• changed document IDs,
• reviewer comments tied to specific fields,
• status of each correction.

For an amendment opportunity, this protects your team from submitting patchy changes and helps if support staff need clarification.

Application flow and likely reviewer expectations

The Simpler page for VA-SPORTS-26A gives the official “how”: application package updates are submitted through Grants.gov as a revision. This implies two review modes:

• administration: the package has to be complete and valid,
• merit/pathway review: content quality matters only where your correction improves technical and programmatic strength.

The key is this: an amendment should improve compliance first, then competitiveness.

From the base NOFO, likely review priorities are still tied to:

• program relevance and veteran outcome focus,
• operational readiness and delivery plan quality,
• budget credibility and spend discipline,
• evidence of capacity to run adaptive sports programming.

If your amendment introduces cleaner data, stronger program justification, and corrected documents (without changing scope), you are in the strongest position.

Common mistakes in amendment rounds

Mistake 1: Treating this as a fresh proposal window

Organizations sometimes rebuild the full proposal and try to pivot scope. That approach usually fails review logic for amendments and can be rejected on compliance grounds.

Mistake 2: Submitting revisions that exceed scope

The text limits scope changes and caps increase amounts in the amendment context. If your team submits a package that materially changes project design, it can be rejected as outside permissible revision boundaries.

Mistake 3: Ignoring system identity mismatches

Incompatible registration or registration drift (UEI, SAM, EIN, organization name) can invalidate a revision. These are not “small formatting” issues; they are threshold-level checks.

Mistake 4: Missing the real deadline while relying on “open” language

The listed closing date is June 19, 2026. Amendment windows are often where teams assume there is slack. In practice, if you submit at the last minute with missing required fields, you may miss the review window.

Mistake 5: Confusing program documents

Use the amendment record for process and the base NOFO for rules, eligibility text, and definitions. Do not rely on marketing summaries or social updates without corroborating the official NOFO language.

How to judge whether your revision is worth submitting

Before sending anything, score your proposed revision on three questions:

1. Is this required for eligibility and administration? If no, hold it unless needed for review quality.
2. Does this fall under a “revision” interpretation (same mission, clarified scope, corrected docs), or a re-scope attempt? If re-scope, consider withdrawing and reapplying in future cycles.
3. Is every corrected item linked to one of the required fields or a clear scoring/quality gap? If no, it may dilute the package.

If at least two of three answers are “yes,” proceed with a controlled package.

What to include in your amendment packet

A clean amendment packet usually includes:

• revised SF424 package with revision selected,
• updated or corrected narrative sections,
• updated budget with explicit amendment rationale,
• corrected supporting forms,
• proof updates for required registrations/administrative requirements,
• no new unrelated claims that conflict with original scope.

Even though the page does not publish every internal QA checklist, this conservative filing pattern reflects standard VA grant revision practice and aligns with the published constraints.

Official preparation timeline

Because this is a specific amendment window, think backward from the June 19 close:

• 5 days before close: finalize internal sign-off and field-level validation.
• 4 days before close: reconcile package version with all required evidence.
• 3 days before close: run final registration and submission readiness checks.
• 2 days before close: do a final compliance read and submit at least one internal backup copy.
• 1 day before close: avoid major changes unless they are critical compliance fixes.
• Close day: submit early enough to avoid system congestion.

This is a practical schedule, not a requirement from official text, but consistent with the strict amendment framing and administrative checks.

Risks, monitoring, and after-submission actions

After submission, track these:

• package confirmation in Grants.gov,
• support notifications,
• reviewer queries,
• whether an issue was flagged at admin checkpoint.

The NOFO for the base opportunity explains how programs are tracked and evaluated, including later report obligations. Even before award, you should preserve the version history and ensure internal teams know where each changed file sits.

A lot of teams lose momentum after “submission done.” In this case, post-submission governance matters:

• update your leadership on what changed versus the original baseline,
• keep a simple FAQ for internal staff,
• maintain all versions in one folder path,
• prepare quick evidence packets in case the grant office requests clarification.

Official links to keep bookmarked

• Amendment opportunity record: https://simpler.grants.gov/opportunity/d03d5c9c-287b-4599-8ed3-a7b543c6852d
• Base call record (VA-SPORTS-26): https://simpler.grants.gov/opportunity/bfeab996-2c6b-475e-ba3e-722125b80ec6
• VA grant program page: https://department.va.gov/veteran-sports/grant-program/
• VA-SPORTS-26 NOFO PDF: https://files.simpler.grants.gov/opportunities/bfeab996-2c6b-475e-ba3e-722125b80ec6/attachments/f23dede0-d358-4950-adf0-38186871c528/VA-SPORTS-26_NOFO.pdf

Frequently asked questions

Is VA-SPORTS-26A open to first-time applicants?

No. It is positioned as an amendment opportunity for organizations that already submitted successfully to VA-SPORTS-26.

Can an applicant increase requested funding by more than 10%?

No. The amendment framing and associated language indicate limits on changes that would increase the amount too much or alter scope.

Is there a separate NOFO for VA-SPORTS-26A?

The public listing references the base NOFO document (VA-SPORTS-26) and defines the amendment workflow. If your filing depends on a rule interpretation, use the base NOFO and, if needed, request a direct clarification through official contacts.

Is this suitable if your original submission was weak?

It is mainly suitable for eligible, structured corrections. If you need major concept changes, a full replacement request in a new cycle is usually the safer path.

What is the best reason to submit an amendment?

Administrative completeness and strict compliance are the most common legitimate reasons: corrected forms, missing proof elements, and targeted package corrections that improve threshold and review readiness.

Strategic takeaway

Treat VA-SPORTS-26A as a controlled correction mechanism tied to an existing VA submission, not a broad grant application round. The strongest applicants use this window to close compliance risk, strengthen proof quality, and reduce review friction. If your organization already met the baseline and has valid submission status, this can be an efficient way to stabilize your application before full review stages. If not, this is not the entry point for first-time access to this VA Adaptive Sports stream.