Once the prime award is active in KC, the DLCIs must request subawards using B2P and RAM to begin the process of subaward issuance.
PI/DLCI Role
- If not verified by RAS at proposal, confirm the relationship meets the criteria of a subrecipient
- Ensure project deliverables involving subrecipients are within reasonable timeframes, as negotiating terms of the subaward agreement between the parties will take time
- Collect all necessary documentation for submission to RAS Subaward team
- Scope of work specific to the subrecipient (not full proposal SOW)
- Detailed subrecipient budget and justification
- Applicable subawardee protocol approvals, e.g., IRB, IACUC
- Subrecipient Commitment Form [PDF]
- Subrecipient Profile Questionnaire [PDF] (for entities new to MIT)
- Special instructions, documents and/or communications, e.g., ancillary agreements such as NDAs and MTAs
- Submit requisition through B2P for PO creation and financial management of your subaward
- Request a new supplier in B2P for new subrecipient organizations
- Contact B2P@mit.edu for questions regarding errors or issues within B2P
- Submit a new service request in RAM
- Type: New Subaward
- Subject: Enter the requisition # and subrecipient name
- Project Links: Link the service request to the same cost object used in B2P
- Complete the questionnaire and upload associated documents
RAS Subaward Team Role
- Confirm the relationship meets the criteria of a subrecipient
- Ensure all necessary information and documents have been received (contact DLCI if not provided)
- Complete subrecipient assessment
- Consult with internal MIT offices as needed (OGC, OSATT, TLO, COI, Export Control)
- Engage PI/DLCI as needed (for example, to approve Sub Monitoring Plan for high risk entities)
- Draft subaward agreement and conduct negotiations with subrecipient
- Copy PI and DLCI administrator when sending fully-executed subaward to subrecipient