This page supplements DARPA Broad Agency Announcements (BAA) and Research Announcements (RA) published on FBO.gov, as well as Grants.gov, and identifies issues proposers should be aware of when drafting proposals in response to BAAs or RAs. The information on this page is part of any BAAs and RAs that specifically reference this page. Should discrepancies exist between published BAAs or RAs that reference this page and its contents, the BAA or RA text takes precedence.
National Policy Requirements, Solicitation Provisions, and Award Clauses and Terms and Conditions
Solicitation Provisions Applicable to FAR-Based Procurement Contracts:
FAR 52.252-1 -- Solicitation Provisions Incorporated by Reference (FEB 1998)
This solicitation incorporates one or more provisions by reference, with the same force and effect as if they were given in full text. Upon request, the contracting officer will make their full text available. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at either of the following:
(End of Provision)
DFARS 252.204-7000 Disclosure of Information (OCT 2016)
(a) The Contractor shall not release to anyone outside the Contractor's organization any unclassified information, regardless of medium (e.g., film, tape, document), pertaining to any part of this contract or any program related to this contract, unless—
(1) The Contracting Officer has given prior written approval;
(2) The information is otherwise in the public domain before the date of release; or
(3) The information results from or arises during the performance of a project that involves no covered defense information (as defined in the clause at DFARS 252.204-7012) and has been scoped and negotiated by the contracting activity with the contractor and research performer and determined in writing by the contracting officer to be fundamental research (which by definition cannot involve any covered defense information), in accordance with National Security Decision Directive 189, National Policy on the Transfer of Scientific, Technical and Engineering Information, in effect on the date of contract award and the Under Secretary of Defense (Acquisition, Technology, and Logistics) memoranda on Fundamental Research, dated May 24, 2010, and on Contracted Fundamental Research, dated June 26, 2008 (available at DFARS PGI 204.4 (DFARS/PGI view)).
(b) Requests for approval under paragraph (a)(1) shall identify the specific information to be released, the medium to be used, and the purpose for the release. The Contractor shall submit its request to the Contracting Officer at least 10 business days before the proposed date for release.
(c) The Contractor agrees to include a similar requirement, including this paragraph (c), in each subcontract under this contract. Subcontractors shall submit requests for authorization to release through the prime contractor to the Contracting Officer.
(End of clause)
DFARS 252.204-7008 Compliance with Safeguarding Covered Defense Information Controls (OCT 2016)
(a) Definitions. As used in this provision—
“Controlled technical information,” “covered contractor information system,” “covered defense information,” “cyber incident,” “information system,” and “technical information” are defined in clause 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting.
(b) The security requirements required by contract clause 252.204-7012, shall be implemented for all covered defense information on all covered contractor information systems that support the performance of this contract.
(c) For covered contractor information systems that are not part of an information technology service or system operated on behalf of the Government (see 252.204-7012(b)(2)—
(1) By submission of this offer, the Offeror represents that it will implement the security requirements specified by National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171 “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations” (see http://dx.doi.org/10.6028/NIST.SP.800-171) that are in effect at the time the solicitation is issued or as authorized by the contracting officer not later than December 31, 2017.
(2)(i) If the Offeror proposes to vary from any of the security requirements specified by NIST SP 800-171 that are in effect at the time the solicitation is issued or as authorized by the Contracting Officer, the Offeror shall submit to the Contracting Officer, for consideration by the DoD Chief Information Officer (CIO), a written explanation of—
(A) Why a particular security requirement is not applicable; or
(B) How an alternative but equally effective, security measure is used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection.
(ii) An authorized representative of the DoD CIO will adjudicate offeror requests to vary from NIST SP 800-171 requirements in writing prior to contract award. Any accepted variance from NIST SP 800-171 shall be incorporated into the resulting contract.
(End of provision)
DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting (OCT 2016) (To be included in any resultant procurement contracts)
(a) Definitions. As used in this clause—
“Adequate security” means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.
“Compromise” means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.
“Contractor attributional/proprietary information” means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.
“Controlled technical information” means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.
“Covered contractor information system” means an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.
“Covered defense information” means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.archives.gov/cui/registry/category-list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is—
(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or
(2) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract.
“Cyber incident” means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.
“Forensic analysis” means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.
“Information system” means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.
“Malicious software” means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.
“Media” means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system.
‘‘Operationally critical support’’ means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.
“Rapidly report” means within 72 hours of discovery of any cyber incident.
“Technical information” means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data—Noncommercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.
(b) Adequate security. The Contractor shall provide adequate security on all covered contractor information systems. To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:
(1) For covered contractor information systems that are part of an Information Technology (IT) service or system operated on behalf of the Government, the following security requirements apply:
(i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract.
(ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract.
(2) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply:
(i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations” (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171) in effect at the time the solicitation is issued or as authorized by the Contracting Officer.
(ii)(A) The Contractor shall implement NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at email@example.com, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.
(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place.
(C) If the DoD CIO has previously adjudicated the contractor’s requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.
(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.
(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.
(c) Cyber incident reporting requirement.
(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor’s ability to perform the requirements of the contract that are designated as operationally critical support and identified in the contract, the Contractor shall—
(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor’s network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor’s ability to provide operationally critical support; and
(ii) Rapidly report cyber incidents to DoD at https://dibnet.dod.mil.
(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at https://dibnet.dod.mil.
(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see http://iase.disa.mil/pki/eca/Pages/index.aspx.
(d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the Contracting Officer.
(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.
(f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis.
(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.
(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.
(i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD—
(1) To entities with missions that may be affected by such information;
(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;
(3) To Government entities that conduct counterintelligence or law enforcement investigations;
(4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or
(5) To a support services contractor (“recipient”) that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information.
(j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government’s use and release of such information.
(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.
(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor’s responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.
(m) Subcontracts. The Contractor shall—
(1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial items, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and
(2) Require subcontractors to—
(i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and
(ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause.
Protests to the Agency (For FAR-based procurement contracts only)
Interested parties may file an agency procurement protest directly with the DARPA Contracting Officer in accordance with FAR 33.103. An independent review at a level above the Contracting Officer is available only as an appeal of a Contracting Officer adverse decision on a protest. The responsible DARPA Official for conducting such independent review, if necessary, is the DARPA Head of the Contracting Activity (HCA).
(End of clause)
Information Applicable to ALL AWARDS:
Controlled Unclassified Information (CUI) on Non-DoD Information Systems
In addition to classified information, certain types of unclassified information also require application of access and distribution controls and protective measures for a variety of reasons. This information is referred to collectively as Controlled Unclassified Information (CUI). DoD CUI includes, but is not limited to: For Official Use Only (FOUO), Law Enforcement Sensitive (LES), DoD Unclassified Controlled Nuclear Information (DoD UCNI), and Limited Distribution, as well as some categories developed by other executive branch agencies. For further information, consult DoDM 5200.01, Volume 4, “DoD Information Security Program: Controlled Unclassified Information (CUI).”
All non-DoD entities doing business with DARPA are expected to adhere to the following procedural safeguards, in addition to any other relevant federal or DoD specific procedures, for submission of any proposals to DARPA and any potential business with DARPA:
Proposers with questions regarding CUI should contact the DARPA Security and Intelligence Directorate at (703) 526-1581.
Publication Restrictions on Non-Fundamental Research
National Security Decision Directive (NSDD) 189 defines fundamental research as follows:
“Fundamental research” means basic and applied research in science and engineering, the results of which ordinarily are published and shared broadly within the scientific community, as distinguished from proprietary research and from industrial development, design, production, and product utilization, the results of which ordinarily are restricted for proprietary or national security reasons.
The following clause or similar language will be included in all awards where the resultant research will not be considered fundamental research and there will be restrictions on publication:
"There shall be no dissemination or publication, except within and between the contractor and any subcontractors, of information developed under this contract or contained in the reports to be furnished pursuant to this contract without prior written approval of DARPA’s Public Release Center (DARPA/PRC). All technical reports will be given proper review by appropriate authority to determine which distribution statement is to be applied prior to the initial distribution of these reports by the contractor. With regard to subcontractor proposals for fundamental research, papers resulting from unclassified fundamental research are exempt from prepublication controls and this review requirement, pursuant to DoD Instruction 5230.27 dated October 6, 1987.
When submitting material for written approval for open publication, the contractor/awardee must submit a request for public release to the DARPA/PRC and include the following information: (1) Document Information: document title, document author, short plain-language description of technology discussed in the material (approx. 30 words), number of pages (or minutes of video), and document type (e.g., briefing, report, abstract, article, or paper); (2) Event Information: event type (conference, principal investigator meeting, article, or paper), event date, desired date for DARPA's approval; (3) DARPA Sponsor: DARPA program manager, DARPA office, and contract number; and (4) Contractor/Awardee's Information: POC name, e-mail, and phone. Allow three weeks for processing. Due dates under three weeks require a justification. Unusual electronic file formats may require additional processing time. Requests may be sent either via email to firstname.lastname@example.org or by mail to 675 North Randolph Street, Arlington VA 22203-2114, telephone (571) 218-4235. Refer to the following for link for information about DARPA’s public release process: http://www.darpa.mil/work-with-us/contract-management/public-release.
FAR-Based Procurement Contract Clauses of Note
Below are a list of clauses that may be included in resultant FAR-based procurement contracts, depending on their applicability. If similar language may be included in OTs, grants, or cooperative agreements, the language’s use is indicated in the chart below. This list is not exhaustive, and the clauses included in a resultant contract will depend on the nature of the award, the award type, the award recipient, and any security or publication restrictions. This list serves to put potential proposers and awardees on notice of requirements and award clauses they may have to adhere to, should they be selected for negotiation for potential award.
Full text for these clauses can be found at
Class Deviations to the FAR and DFARS can be found at: http://www.acq.osd.mil/dpap/dars/class_deviations.html
Sample Terms and Conditions for Grants and Cooperative Agreements
Sample DARPA-specific grant and cooperative agreement terms and conditions can be found at: http://www.darpa.mil/work-with-us/contract-management#GrantsCooperativeAgreements.
Human Subjects Research and Animal Use
Human Subjects Research
All research selected for funding involving human subjects, to include use of human biological specimens and human data, must comply with the federal regulations for human subjects protection. Further, research involving human subjects that is conducted or supported by the DoD must comply with 32 CFR 219, Protection of Human Subjects (and DoD Instruction 3216.02, Protection of Human Subjects and Adherence to Ethical Standards in DoD-Supported Research (http://www.dtic.mil/whs/directives/corres/pdf/321602p.pdf).
Institutions awarded funding for research involving human subjects must provide documentation of a current Assurance of Compliance with federal regulations for human subjects protection, such as a Department of Health and Human Services, Office of Human Research Protection Federal Wide Assurance (http://www.hhs.gov/ohrp). All institutions engaged in human subjects research, to include subcontractors, must also hold a valid assurance. In addition, all personnel involved in human subjects research must provide documentation of completion of human subjects research training.
For all proposed research that will involve human subjects in the first year or phase of the project, the institution must provide evidence of or a plan for review by an Institutional Review Board (IRB) upon final proposal submission to DARPA as part of their proposal, prior to being selected for funding. The IRB conducting the review must be the IRB identified on the institution’s Assurance of Compliance with human subjects protection regulations. The protocol, separate from the proposal, must include a detailed description of the research plan, study population, risks and benefits of study participation, recruitment and consent process, data collection, and data analysis. It is recommended that you consult the designated IRB for guidance on writing the protocol. The informed consent document must comply with federal regulations (32 CFR 219.116). A valid Assurance of Compliance with human subjects protection regulations along with evidence of completion of appropriate human subjects research training by all investigators and personnel involved with human subjects research should accompany the protocol for review by the IRB.
In addition to a local IRB approval, a headquarters-level human subjects administrative review and approval is required for all research conducted or supported by the DoD. The Army, Navy, or Air Force office responsible for managing the award can provide guidance and information about their component’s headquarters-level review process. Note that confirmation of a current Assurance of Compliance with human subjects protection regulations and appropriate human subjects research training is required before headquarters-level approval can be issued.
The time required to complete the IRB review/approval process varies depending on the complexity of the research and the level of risk involved with the study. The IRB approval process can last between one and three months, followed by a DoD review that could last between three and six months. Ample time should be allotted to complete the approval process. DoD/DARPA funding cannot be used toward human subjects research until ALL approvals are granted.
Award recipients performing research, experimentation, or testing involving the use of animals shall comply with the rules on animal acquisition, transport, care, handling, and use as outlined in: (i) 9 CFR parts 1-4, Department of Agriculture rules that implement the Animal Welfare Act of 1966, as amended, (7 U.S.C. § 2131-2159); (ii) National Institutes of Health Publication No. 86-23, "Guide for the Care and Use of Laboratory Animals" (8th Edition); and (iii) DoD Instruction 3216.01, “Use of Animals in DoD Programs.”
For projects anticipating animal use, proposals should briefly describe plans for Institutional Animal Care and Use Committee (IACUC) review and approval. Animal studies in the program will be expected to comply with the Public Health Service (PHS) Policy on Humane Care and Use of Laboratory Animals, available at http://grants.nih.gov/grants/olaw/olaw.htm.
All award recipients must receive approval by a DoD-certified veterinarian, in addition to an IACUC approval. No animal studies may be conducted using DoD/DARPA funding until the United States Army Medical Research and Materiel Command (USAMRMC) Animal Care and Use Review Office (ACURO) or other appropriate DoD veterinary office(s) grant approval. As a part of this secondary review process, the award recipient will be required to complete and submit an ACURO Animal Use Appendix, which may be found at http://mrmc.amedd.army.mil/index.cfm?pageid=research_protections.acuro_animalappendix.
System for Award Management (SAM) Registration, Universal Identifier Requirements, and Representations and Certifications
All proposers (except those exempt per FAR 4.1102 or 2 CFR 25.110, as applicable) must be registered in the System for Award Management (SAM) and have a valid Data Universal Numbering System (DUNS) number to receive an award. All proposers must maintain an active and current SAM registration at all times throughout the award process, should they be selected. All proposers are encouraged to provide their DUNS number, if available, in each proposal they submit.
Click HERE to register in SAM.
Click HERE to acquire a DUNS number.
Representations and Certifications
In accordance with FAR 4.1201, prospective proposers shall complete electronic annual representations and certifications at www.sam.gov. SAM will be supplemented with DARPA contract specific representations and certifications. Below is a copy of the standard DARPA representations and certifications; these may be modified on an award-by-award basis, as necessary, in consultation with your contracting officer.
Current DARPA-Specific Representations and Certifications for Proposers
GRANTS.GOV Submission Information
DARPA encourages grant and cooperative agreement proposers to submit their proposals via electronic upload. Proposers that plan to submit through Grants.gov must be aware of the following procedures and the potential time it may take to complete them.
Proposers electing to use Grants.gov must complete a one-time registration process on Grants.gov before a proposal can be electronically submitted. However, before you can register as an applicant with Grants.gov, you will need to obtain a DUNS number and complete registration in SAM. These processes can take up to four weeks. Once your DUNS number has been verified, you can submit your registration to Grants.gov. For more information, see http://www.grants.gov/web/grants/register.html.
2. Submit an Application
Submit your proposal via electronic upload at:
For more information on submitting proposals to Grants.gov, see: http://www.grants.gov/web/grants/applicants/applicant-faqs.html. Technical support for Grants.gov submissions may be reached at 1-800-518-4726 or email@example.com.
3. Track and Application
Once Grants.gov has received a proposal submission, Grants.gov will send two email messages to advise proposers as to whether or not their proposals have been validated or rejected by the system. It may take up to two days to receive these emails. The first email will confirm receipt of the proposal by the Grants.gov system, but this email only confirms receipt, not acceptance, of the proposal. The second email will indicate that the application has been successfully validated by the system prior to transmission to the grantor agency or that it has been rejected due to errors. If the proposal is validated, then the proposer has successfully submitted their proposal. If the proposal is rejected, the proposed must be corrected and resubmitted before DARPA can retrieve it. If the solicitation is no longer open, the rejected proposal cannot be resubmitted. Once the proposal is retrieved by DARPA, the proposer will receive a third email from Grants.gov. For more information on tracking your proposal submission, see: http://www.grants.gov/web/grants/applicants/track-my-application.html
Grants.gov recommends that proposers submit their proposals to Grants.gov 24-28 hours in advance of the proposal due date specified in the BAA to provide sufficient time to complete the registration and submission process, receive email notifications and correct errors, as applicable.
You are now leaving the DARPA.mil website that is under the control and
management of DARPA. The appearance of hyperlinks does not constitute
endorsement by DARPA of non-U.S. Government sites or the information,
products, or services contained therein. Although DARPA may or may not
use these sites as additional distribution channels for Department of
Defense information, it does not exercise editorial control over all of
the information that you may find at these locations. Such links are
provided consistent with the stated purpose of this website.
After reading this message, click to continue