Department of Defense (Department of War)

DOD Grant Opportunity Listings on Grants.gov

DOD Current Contract Listings

DOD Agencies

• Air Force Office of Scientific Research
• Army Medical Research and Development Command
• Army Research Lab
• Army Research Office
• Congressionally Directed Medical Research Programs
• Defense of Medical Research and Development Program
• DARPA
  • Universities
• Office of Naval Research

Access the Federal Acquisition Regulation

It is important to read the BAA thoroughly because the information below can change at any time and may in the BAA.

Identify the Funding Opportunity

• Visit  Grants.gov or AFOSR BAA page to find active Broad Agency Announcements (BAAs).
• Read the full BAA carefully to understand scope, eligibility, and submission instructions.

Prepare the Pre-proposal (only if required by the BAA)

• This is done directly by the PI (OPAS does not need to be involved in the pre-proposal but contact them if you have any questions).
• Should you wish to submit via OPAS, develop a Kuali record with the required elements according to the BAA.
  • Depending on the BAA, the pre-proposal should describe the research concept, objective and approach, scientific significance, and the expected outcome. The pre-proposal is limited to two pages (text and legible graphics). A short budget statement on the approximate cost for a three (3) to five (5) year effort must be provided. A third page containing key references may be included.
  • Route to OPAS for review and submission.

Prepare the Proposal in Kuali

• Develop the record in Kuali using the S2S packages. Follow UMass Kuali standard guidelines on how to upload the correct and current package into Kuali. Follow the Kuali Proposal S2S Guidelines for attachments and S2S submissions.
• Note that AFOSR packages sometimes show an error because they want a specific form (e.g., Project Abstract) attached in the User Attached Forms section. Adding the form will allow the package to load,  and the rest of the files can be attached, as directed/needed.
• Follow AFOSR formatting guidelines (usually 12-point font, labeled sections).

Include all required components, remembering to attach the files in Kuali by matching the Type with the file name. Note that the Grants.gov forms in bold below are embedded in the S2S package, and the PI only has to attach the required documents as flattened pdfs in the Attachment Proposal tab so that the files will map to the appropriate submission forms.

• Cover page (Form SF 424 (R&R)). If a pre-proposal was submitted and an identifier number was assigned, the number should be filled in “Sponsor Proposal ID” field of the Sponsor & Program Information tab in the Basics section in Kuali. This will link the ID number to the Federal ID 4a field of the SF424.
• R&R Other Project Information Form
  • Technical narrative
  • Publicly Releasable Project Abstract/Summary attached to the R&R Other Project Information form. Attach it as a flattened pdf file in the Attachment Proposal section with the description “Summary/Abstract” Budget and justification (a separate Equipment justification too, as needed)
  • Facilities and equipment
  • Data management plan (outline data sharing and preservation strategy)
• R&R Project Abstract Summary Form
  • You will also need to upload the Project Abstract/Summary Form attached as User Attached Form so that S2S package validates correctly. Be sure to use a unique filename for each of the Summary/Abstract uploads.
• R&R Senior / Key Person Profile Form (Expanded)
  • Biosketches
  • Current and pending support (Include all active and pending collaborations)
• Representations and certifications (ensure all required certifications are completed. OPAS to review and sign.
• R&R Subaward Budget Attachments Form/Subaward Budget (if applicable)
• R&R Project / Performance Site Locations Form
• Attachments Form: DHHS NICRA Rate Agreement and other misc. docs, if required
• Address AFOSR-Specific Requirements (can vary depending on BAA)
  • Security Program Questionnaire (See Appendix 1). Address security and export control disclosures or restrictions.
  • “Privacy Act Statement” consent form for each Covered Individual that is also signed by the Applicants/Recipients as the Individual’s Sponsors (See “Covered Individual” section below and Appendix 2) Include Statement of Work (SOW) with clear milestones.
  • Include public release approval required for dissemination of research results, if applicable.
  • Provide a copy of all peer-reviewed publications developed or produced from research conducted with Air Force and Space Force funds (if required by BAA).

Submit the Proposal

• OPAS will submit and email the final submission package with the Grants.gov tracking ID to the PI.

Post-Submission

• Monitor Grants.gov and email for confirmation and status updates.
• Be prepared to respond to AFOSR technical and administrative inquiries. Any proposal updates, revisions, or budget changes must be submitted by OPAS.

It is important to read the BAA thoroughly because the information below can change at any time and may in the BAA.

In the context of research proposal submissions, ARO (Army Research Office) and ARL (Army Research Laboratory) are both part of the U.S. Army's research ecosystem, but they serve distinct roles and have different submission processes and focus areas. 

Key Differences Between ARO and ARL 

Typical submissions to ARO vs. ARL

• Submit to ARO if your research is basic science, exploration, and aligns with long-term Army technology needs.
• Submit to ARL if your work is more applied, mission-oriented, or if you're responding to a specific ARL research topic under their BAA.
• BAA Forms for both: https://arl.devcom.army.mil/resources/baa-forms/ 

Both entities fall under DEVCOM ARL, but ARO is more externally focused on academia, while ARL includes internal labs and broader collaborations. This is a general guide to their standard areas of interest, but the areas are not limited to each division, and the specific BAA is what decides the area of focus.

To submit a proposal to the Army Research Laboratory (ARL), you generally follow the Department of War (DOW) and Army Research Office (ARO) procedures, as ARL often collaborates with ARO for funding mechanisms. At UMass 99% of the submissions are through the Kuali S2S system (not grants.gov). Please contact them if you have questions about how to submit.

Identify the Funding Opportunity

• Visit Grants.gov or SAM.gov to find active ARL or ARO Broad Agency Announcements (BAAs).
• Review the BAA for eligibility, scope, and submission instructions.

Submit a White Paper (depends on BAA and can be “optional but encouraged”)

• This is done directly by the PI (OPAS does not need to be involved in the pre-proposal but contact them if you have any questions).
• Contact the ARL Program Manager/DEVCOM Analysis Center to discuss if you have questions.
• Submit a white paper to the ARL/DAC TPOC for feedback.
• Await recommendation to proceed with a full proposal.

Prepare the Full Proposal

• Develop a record in Kuali and pull the BAA Package into the S2S system. Follow the Kuali Proposal S2S Guidelines for attachments and S2S submissions.
• Follow the BAA and General formatting guidelines (e.g.,12-point font, labeled sections).
• Include:
  • Cover page
  • Technical narrative
  • Budget and justification
  • Biosketches
  • Facilities and equipment
  • Data management plan
  • Current and pending support
  • Representations and certifications

Address Specific Requirements and Regulations

• Include Statement of Work (SOW) with clear milestones. (ARL-specific)
• Address security and export control considerations. (ARL-specific)
• Include public release approval if applicable. (ARL-specific)
• General guidance on Research Terms and Conditions
• Federal Acquisition Regulations (FAR)
• DFARS Federal Acquisition Regulations 

Submit the Proposal

• Ensure all documents are uploaded into Kuali by the deadline and email OPAS to confirm.
• OPAS will do a final check; send a final printout for approval to the PI.
• OPAS will submit via Kuali and confirm the grants.gov tracking ID and attach the final submission package with the PI.

Post-Submission

• Monitor Grants.gov for confirmation and status updates.
• Respond promptly to ARL inquiries or requests for clarification.                                                 

It is important to read the BAA thoroughly because the information below can change at any time and may in the BAA.

Below is a comprehensive DARPA grant (BAA/RA) submission checklist, combining official guidance and general best practices for proposals. It follows the Darpa General Terms and Conditions but each BAA requirements may differ, so examine each solicitation closely.

Pre-proposal Submission

• Identify solicitation and pre‑proposal requirements.
• Active registration for PI TFIMS account, if not already done.
• Develop a Kuali record with the required elements according to the BAA with required content (follow BAA but below is a general list):
  • Prepare content per page/formatting constraints.
  • Add labeling and required legends.
  • Encrypt if required/proprietary.
  • Disclosures
• Route to OPAS for review and approval before submitting.
• Once approved by OPAS, the PI may upload the required content via TFIMS before the deadline.
• The PI should save the submission confirmation (e.g., screen shot) and send it to OPAS.

Proposal Submission

• Create a Kuali record for the submission, following the standard Kuali guidelines for developing the record. Follow the Kuali Proposal S2S Guidelines for attachments and S2S submissions.
• Section I: Cover Page
  • DARPA/RFP number, program title, organization name, business type
  • Proposal title, submission date
  • Technical and administrative points of contact
  • Total proposed cost.
• Section II: Summary of Proposal
  • Overview of technical rationale and objectives.
  • Description of Deliverables, Milestones and Team
  • Biosketches
  • Current and Pending
  • Statement of Work
• Section III: Detailed Proposal
  • Technical Rationale – justify approach
  • Objectives, Deliverables, & Milestones – define SOW
  • Team Description & Management Plan – roles, responsibilities
  • Risk Assessment & Mitigation – technical and project risks
  • Transition & Commercialization Strategy (if relevant)
• Section IV: Supporting Info
  • Bibliographies and citations
  • Publications
  • Current and pending support documentation for key personnel
  • Biosketches and CVs for all personnel
  • Letters of support

Volume I – Technical & Management Proposal

Volume II – Cost Proposal

• Cover Page
  • DARPA BAA number, technical area, organization, award instrument.
  • Title, POC names, place(s) and period(s) of performance.
  • Total proposed cost.
  • DUNS, TIN, CAGE code.
  • Cognizant DCMA and DCAA contact information.
  • Proposal preparation date and validity period.
  • Subcontractor summary, as applicable.
• Cost Detail
  • Detailed Budget and Justification - The Government recommends proposers use the provided MS Excel DARPA Standard Cost Proposal Spreadsheet in the development of their cost proposals.
  • Detailed phase/task/month breakout.
  • Direct labor (roles, effort), Fringe.
  • Subcontracts (itemized).
  • Materials and equipment.
  • Other direct costs (travel, fees).
  • F&A rates (In Kuali, choose Standard Federal MTDC for Grants and cooperative agreements, DOD Standard Federal MTDC for Contracts).

Administrative & Formatting Requirements

• Letter-size (8.5″×11″), single-spaced
• Font: ≥ 12-point (e.g. Times New Roman), margins ≥ 1″
• Clearly mark documents containing proprietary data with applicable legends 

Compliance & Certifications

• Include DARPA-specific and DOW COOPs (“Reps & Certs”) per award vehicle [darpa.mil]
• For classified proposals, follow DARPA’s procedures, marking, encryption, and submission protocols [ https://share.google/2nzlNz96DU4Q4kdfH]

Additional Instructions

• Align proposals with solicitation-specific instructions and BAA details [darpa.mil]
• For grants/co-op agreements, follow DoD research T&Cs (2 CFR 200) and DARPA-specific clauses [darpa.mil], [darpa.mil]

Final submission steps

• All sections of Volumes I & II complete and consistent
• Administrative forms (DUNS, CAGE, DCMA/DCAA contacts) included
• Formatting adheres to DARPA requirements
• Proprietary/classified legends and markings applied correctly
• Required certifications and representations included
• Proposal assembled into a single PDF (or required format)
• Submission via Grants.gov or BAA portal before deadline
• Confirmation of upload and validation received

It is important to read the BAA thoroughly because the information below can change at any time and may in the BAA. For Funding Opportunities, see Congressionally Directed Medical Research Programs (CDMRP).

Electronic Biomedical Research Application Portal (eBRAP) Registration

The first step is to register in the eBRAP system. PI’s register themselves in eBRAP.org.

Search Organizations will come up. UMass is registered as Massachusetts, University of, Amherst - type this as the organization and hit search.

Massachusetts, University of, Amherst, will come up. Select Choose this Organization.

Select Principal Investigator on the drop down list in answer to the question I am a new: (role). Select start Registration. Fill in the information here and continue to click next until finished. You will see a screen in eBRAP that says: Thank you for registering! An email has been sent to (email address) containing a confirmation link…. This refers to an auto email sent to OPAS for review and approval.

Note: Be sure to select the correct organization. There are two listed options to choose from and the correct one is: Massachusetts, University, of Amherst). Choosing the correct institution will ensure that the pre-proposal is linked to UMass and the full proposal will be connected to the pre-proposal too. 

You must be affiliated with Massachusetts, University of, Amherst as a PI in eBRAP before submitting a pre-application. 

Once OPAS confirms the PI’s registration request to be affiliated with Massachusetts, University of, Amherst, eBRAP will then send an email to the PI confirming that registration was successful. The eBRAP screen will say Email confirmation and registration was successful, you may now log in!

You will then be able to begin a letter of intent, pre-application or application in eBRAP.

• The eBRAP user guide
• The user guide is supplemented by the DOD General Application Instructions
• eBRAP FAQs

Pre-Application Submission in the eBRAP portal

1. This is done directly by the PI and no Kuali record is required. (OPAS does not need to be involved in the pre-proposal but contact them if you have any questions).
2. Pre-application content and forms must be accessed and submitted by the PI at eBRAP. In the PI profile, check that the correct organization is selected. Note that there are two options to choose from and the correct one is: Massachusetts, University, of Amherst). Choosing the correct institution will ensure that the pre-proposal is linked to UMass and the full proposal will be connected to the pre-proposal too.
3. Select the correct funding opportunity and award mechanism (e.g., grant, coop agreement, contract).
4. Complete and upload required pre-application documents (e.g., LOI or pre-proposal).
   1. Assign the Collaborators (if applicable); Business Official (BO); Authorized Organizational Representative (AOR). Select Kristy Reese as the Business Official.
   2. Make sure all PI contact info is the same as what will be on the SF424.
      For all pre-proposals, please use this address:
   3. 100 Venture Way
      Suite 201 Hadley, MA 01003-9450
      Phone: 413-545-0699
      Fax: 413-545-1202
   4. For all pre-proposals, please use the OPAM email address: @email. We must use this address, because at the full proposal stage, grants.gov full proposals can only be submitted under this address, and the pre-proposal and full proposal must use the same information. Please see the warning below:
   5. Please note: The application title, eBRAP log number, and all information for the PI, Business Official(s), performing organization, and contracting organization must be consistent throughout the entire pre-application and full application submission process. Inconsistencies may delay application processing and limit or negate the ability to view, modify, and verify the application in eBRAP. If any changes need to be made, the applicant should contact the CDMRP Help Desk at @email or 301-682-5507 prior to the application submission deadline.
5. An email notification of the submission will be sent to the contacts listed in the pre-application.
6. Pre-application screening results showing invitation status are posted in eBRAP. The PI will receive a notification that it has been posted.
7. Partnering PI Option: After the Initiating PI submits the pre-application the Partnering PI will receive a link via email to assign the Organization and Business Official to their portion of the pre-application. This link is valid up until the pre-application deadline. After the deadline please send this information to the eBRAP Helpdesk and they will input the information.
8. Once the pre-proposal or letter of intent is submitted by the PI, eBRAP will assign an eBRAP log number to the proposal. This number is required to be on the full proposal application, so you will need it at the full proposal stage.
9. For specific instructions regarding content of the pre-application submission components, refer to the Program Announcement.
10. For specific instructions on how to submit each pre-application component, please the DOD general application instructions.
11. Click Submit and Confirm Submission to complete the pre-application submission before the deadline.
12. Submitted pre-applications may be set to draft status prior to the pre-application deadline. eBRAP will automatically submit documents that are still in draft status at the end of the pre-application deadline. 

Full Application Submission via Kuali S2S

Full applications are submitted through Grants.gov using the UMass Kuali system. Full proposals should adhere to the Sponsored Project Proposal Submission Requirements and Procedures (Five Day Submission Procedure).

Follow the guidelines for required documents in the Program Announcement. Use the generic forms for application submission in eBRAP as required by the Program Announcement. Funding Opportunities and forms are available here.

The total guidelines consist of the 1) Program Announcement (BAA/Funding Opportunity) and the 2) DOD/CDMRP General Application Instructions. Each solicitation also has a helpful “Synopsis” of the funding opportunity. Read all three documents.

1. Wait for invitation to submit after submitting the pre-proposal (if applicable).
2. Find and upload the package in the S2S tab in Kuali.
3. Prepare full application package using the Kuali S2S system (automatically completes the SF424 (R&R) and forms in the package).
4. You must include the unique eBRAP Proposal ID assigned the pre-proposal in SF424 block 4a (Federal Identifier). In Kuali, this is entered in the Sponsor Program ID field in the Sponsor & Program Information tab, so it populates field 4a in the SF424. If you are partnering with another PI to submit a proposal, make sure that both PIs are submitting individual proposals and enter the unique number they are given during the pre-proposal process to connect them when submitted.
5. Files should be named according to guidelines. Write the exact file names in Description field in Kuali so they map to the package. Only the sponsor-required documents should be attached to the Proposal tab in the Attachments section of Kuali. Follow the Kuali Proposal S2S Guidelines for attachments and S2S submissions.
6. Kuali only recognizes Attachment for the Type dropdown. Other dropdowns will not allow the file to be mapped and will not show up in the combined pdf.
7. Files should be attached according to the order in the Guidelines. The Narrative should always come first. In Kuali, this means that the first file (Narrative) should be at the bottom of the screen, and the last file should be at the top. Use the blue arrows to move the files around and check the pdf to see if they are in order.
8. Go to the S2S Opportunity page in the Basics section of the proposal record. Click Forms, then select the forms that will be submitted to the sponsor. Select Create PDF.
9. Check that the PI contact information matches in the eBRAP portal and S2S record.
10. Once the technical narrative is finalized and loaded to Kuali, please let your OPAS reviewer know it is ready for submission, and OPAS will submit the proposal in Kuali. 

Please Note: 

• The Project Narrative and Budget Form cannot be changed after the application submission deadline. For these reasons:
• PI’s are strongly encouraged to submit their proposals to OPAS early to allow for time to submit corrections to potential errors.
• The full application submission deadline and the end of the application verification period in eBRAP are stated in the specific Program Announcement. The PI should NOT modify the application within eBRAP without checking in with the OPAS Pre-award Administrator. As noted above, OPAS may make changes to the full application package (except to the project narrative and budget form) in eBRAP until the end of the application verification period. Again, PI’s are encouraged to submit their proposals to OPAS early to address possible errors and warnings.
• The PI may also validate their proposal in eBRAP to confirm that it is final, however, eBRAP will automatically verify the application after the application verification period, if the PI has not validated.
• OPAS will submit via S2S and confirm the GRANT ID tracking # and final submission package that was sent.

Following retrieval and processing of the Grants.gov application, eBRAP will notify the organizational representatives and PI by email to log into eBRAP to review, modify, and verify the Grants.gov application submission. eBRAP will validate retrieved files against the specific Program Announcement requirements and discrepancies will be noted in both the email and in the Full Application Files tab in eBRAP. eBRAP does not confirm the accuracy of file content. It is the applicant’s responsibility to review all application components and ensure proper ordering as specified in the Program Announcement. If either the Project Narrative or the budget fails eBRAP validation or if the Project Narrative or the budget need to be modified, an updated Grants.gov application package must be submitted via Grants.gov as a Changed/Corrected Application with the previous Grants.gov Tracking ID prior to the application submission deadline. 

Post-Submission Verification in eBRAP

1. Wait for email from eBRAP that confirms the proposal was received (usually within two hours). If no email is received w/in 2 hrs., OPAS may need to call eBRAP and check.
2. Once the email is received and OPAS/eBRAP confirms the pre-proposal is linked to the full proposal, OPAS will:
   • Review uploaded application components.
   • Modify allowable sections (e.g., contact info, institution details).
   • Verify and validate the proposal in eBRAP.

It is important to read the BAA thoroughly because the information below can change at any time and may in the BAA 

Identify the Funding Opportunity

• Visit ONR Funding Opportunities or Grants.gov to search for Broad Agency Announcement (BAA) or Funding Opportunity Announcement (FOA).
• Review the relevant eligibility.

Submit a White Paper (Optional but Recommended)

• Submit a white paper to the ONR Program Officer. This is done directly by the PI (OPAS does not need to be involved in the pre-proposal but contact them if you have any questions).
• Should you wish to submit via OPAS, develop a Kuali record with the required elements according to the BAA.
  • Depending on the BAA, the pre-proposal should describe the research concept, objective and approach, scientific significance, and the expected outcome. The pre-proposal is limited to two pages (text and legible graphics). A short budget statement on the approximate cost for a three (3) to five (5) year effort must be provided. A third page containing key references may be included.
• Route to OPAS for review and submission.
• Wait for feedback from ONR on alignment with ONR priorities.
• Proceed to full proposal if encouraged (usually you may still submit even if discouraged).

Prepare the Proposal in Kuali

• Contracts: Submit directly to the ONR Program Officer using ONR templates.
• Grants: Submit via Kuali S2S. Develop the record in Kuali using the S2S packages. Follow UMass Kuali standard guidelines on how to upload the correct and current package into Kuali. Follow the Kuali Proposal S2S Guidelines for attachments and S2S submissions.
• Develop the record in Kuali using the S2S packages. Follow UMass Kuali standard guidelines on how to upload the correct and current package into Kuali. Follow the Kuali Proposal S2S Guidelines for attachments and S2S submissions.
• Note that ONR packages sometimes show an error because they want a specific form (e.g., Project Abstract) attached in the User Attached Forms section. Adding the form will allow the package to load. and the rest of the files can be attached, as directed/needed.
• Follow ONR formatting guidelines (usually 12-point font, labeled sections).
  • Include all required components, remembering to attach the files in Kuali by matching the Type with the file name. Note that the Grants.gov forms in bold below are embedded in the S2S package, and the PI only has to attach the required documents as flattened pdfs in the Attachment Proposal tab so that the files will map to the appropriate submission forms.
• Cover page (Form SF 424 (R&R)). If a pre-proposal was submitted and an identifier number was assigned, the number should be filled in “Sponsor Proposal ID” field of the Sponsor & Program Information tab in the Basics section in Kuali. This will link the ID number to the Federal ID 4a field of the SF424.
  • R&R Other Project Information Form
    • Technical narrative (ONR Template)
      • Statement of Work (SOW) (ONR Template)
      • Publicly Releasable Project Abstract/Summary attached to the R&R Other Project Information form. Attach it as a flattened pdf file in the Attachment Proposal section with the description “Summary/Abstract”
      • Cost Proposal Template and justification (a separate Equipment justification too, if needed)
      • Facilities and equipment
      • Data management plan (outline data sharing and preservation strategy)
    • R&R Project Abstract Summary Form
      • You will also need to upload the Project Abstract/Summary Form attached as User Attached Form so that S2S package validates correctly. Be sure to use a unique filename for each of the Summary/Abstract uploads.
    • R&R Senior / Key Person Profile Form (Expanded)
      • Biosketches
      • Current and pending support (Include all active and pending collaborations)
    • Representations and certifications (ensure all required certifications are completed. OPAS to review and sign.
    • R&R Subaward Budget Attachments Form/Subaward Budget (if applicable)
    • R&R Project / Performance Site Locations Form
    • Attachments Form: DHHS NICRA Rate Agreement; OCI disclosure (if applicable); Animal use documentation (if applicable), and other misc. docs, if required

Address AFOSR-Specific Requirements (can vary depending on BAA)

• Security Program Questionnaire (See Appendix 1).
• Address security and export control disclosures or restrictions.
• “Privacy Act Statement” consent form for each Covered Individual that is also signed by the Applicants/Recipients as the Individual’s Sponsors (See “Covered Individual” section below and Appendix 2)
• Include Statement of Work (SOW) with clear milestones.
• Include public release approval required for dissemination of research results, if applicable.
• Provide a copy of all peer-reviewed publications developed or produced from research conducted with Naval funds (if required by BAA).

Submit the Proposal

• Route to OPAS for review and submission.
• Ensure all documents are complete and match budget figures across forms.
• OPAS will submit and email the final submission package with the Grants.gov tracking ID to the PI.

Post-Submission

• Monitor Grants.gov and email for confirmation and status updates.
• Be prepared to respond to ONR technical and administrative inquiries. Any proposal updates, revisions, or budget changes must be submitted by OPAS.
• Await technical and programmatic review.