Skip to main content

Incoming Subawards

1. New Incoming Subaward Proposal in COEUS

All Incoming Subawards are required to be submitted through COEUS in order to capture needed information to approve the proposal.  Incoming Subaward proposals must then be submitted through PEER to be negotiated by the CO.

Required Documentation needed for COEUS Submission

  1. Letter of Intent to Establish a Federal Sub-Award Contract
  2. Non-Federal Letter of Intent to Establish a Sub-Award Contract (to be signed by SPA to be returned to Prime Recipient)
  3. Budget Justification
  4. Statement of Work

Please contact your SPA specialist if you require technical assistance in creating your Incoming Subaward proposal. 

2. Log an Incoming Subaward Proposal in PEER

After you have fully completed the COEUS proposal, but before submitting it for approval, the Research Unit (RU) creates a PEER Subaward - Incoming log (“G” log) to track proposal and capture PI Assurance Certification and Key Person(s) Conflict of Interest (COI). 

PI and Faculty involved as Key Persons in proposal will receive e-mail requesting Assurance and COI be completed. Proposal will not be approved by SPA until all certifications are completed.

After submitting “G” log for Incoming Subaward proposal, return to COEUS proposal, certify the investigator, and submit proposal. 

3. Route COEUS Proposal for Approval

When RU submits proposal to SPA for approval, the proposal is also routed to other RUs with Faculty listed as Key Persons on the project for approval prior to being received by SPA. 

4. SPA Incoming Subaward Proposal Approval Process

Once all RUs have approved the proposal the COEUS Proposal is received in SPA for review. 

  • SPA Grant Coordinator updates PEER “G” Log to “Received in Central Office”.
  • Proposal appears on designated SPA Specialist PEER work log indicating that proposal is waiting for review.
  • SPA Administrative Review includes?  (What are you reviewing?)
      1. Abstract/Scope of Work (SOW)
      2. Budget (F&A/Fringe Rates, Percent Effort)
      3. Budget Justification (comparing it to the budget for accuracy)
      4. Letter of Intent (LOI)

Please note:  During review, the proposal may be returned to PI/department for corrections based on budget, effort, missing narratives...  Please see "Routing and Possible Problems" (coming soon) for more information.

  • SPA Specialist updates PEER “G” log to "Completed" and approves COEUS proposal.
  • SPA specialist will notify RU by email that they can initiate a Contract Request from the “G” log once the Other Party has provided the DRAFT Subaward agreement document. 

5. Creating a New Contract Request in PEER

  • Research Unit (RU) initiates Contract Request (CR) via PEER using the “G” log associated with the COEUS proposal
  • PEER Manual: Page 14 "New Contract Requests"

* Please note: the Contract Request will not be approved without a link to a COEUS proposal via a “G” PEER log.

  PEER Navigation pages to complete:

  1. General Information
  2. Funding & Dates
  3. Sponsor/Other Party
  4. Questionnaire
  5. Subcontracts
  6. Attachments -- Draft Agreement (including SOW and Budget Justification)
  7. Review & Submit -- 

  8. System will run validations to ensure complete request.


REMINDER: A Contract Request will not be approved without a link to a COEUS proposal via a “G” PEER log.

 A Contract Request is completed and submitted by Research Unit via PEER to SPA. 

6. PEER Contract Request Approval by SPA

  • SPA receives notice via PEER that a Contract Request has been submitted and is ready for set-up.
  • SPA assigns the CR to a Contract Officer (CO).
  • Contract Coordinator (CC) is notified via PEER to initiate contract set-up and assign UNIV # in PEER.
  • Research Unit and CO receive an automated introductory email titled “PEER-New Contract – UNIV ####” indicating CO will begin review.
  • CO will work with PI and RU to negotiate contract with VUMC.