Print/Save to PDF

Using RAM and B2P for Subawards

As of November 9, 2026, DLCI administrators use both B2P and RAM (Research Administration Module) to request and manage third party subawards.

Actions in B2P are for procurement requirements and financial management of your subaward and will not require uploading documents or providing subaward details.
RAM service requests provide the necessary information to initiate the process of issuing subawards and subaward amendments to third party entities.

Please refer to Requesting New Subawards and Managing Subawards for additional details.

The table below details which systems are required for various subaward actions:

All new subawards require the creation of a B2P requisition followed by the creation of a RAM service request.
Not all B2P change orders on subaward POs require a RAM service request, and not all subaward amendment requests require a B2P change order.

Required B2P and RAM Requests for Subaward Actions
Subaward Action	B2P Action	RAM Service Request
New subaward	Requisition	New Subaward
Subaward amendment with funding amount change	Purchase Order Change	Subaward Modification/ Amendment
Subaward amendment without funding amount change	N/A	Subaward Modification/ Amendment
Purchase order technical change (no subaward amendment needed)	Change Order Please also email subawards@mit.edu	N/A
New purchase order for existing subaward	Requisition: Please email subawards@mit.edu	N/A

Questions? Please reach out to subawards@mit.edu.

^{Last edited November 9th, 2026}