When considering a proposal hierarchy, it’s important to remember a proposal can be routed to multiple participating, non-lead units without using Proposal Hierarchy. (See http://kc.mit.edu/category/faq/routing). Also, anticipation of an Award Hierarchy structure does not necessitate a Proposal Hierarchy. For additional guidance, use the following chart to determine if a proposal hierarchy is needed:
Step 1. Are you preparing a Summary Budget for submission?
If |
Then |
||||
Yes |
A Proposal Hierarchy Cannot be Used |
||||
No |
Is more than one unit involved in the proposal? |
||||
|
If |
Then |
|||
|
No |
Proceed to Step # 2 |
|||
|
Yes |
Does at least one unit have Lab Allocations? |
|||
|
|
If |
Then |
||
|
|
Yes |
A Proposal Hierarchy Is Most Likely Necessary |
||
|
|
No |
Proceed to Step # 2 |
||
Step 2. Does the proposal involve more than one Activity Type (e.g Organized Research and Instruction)?
If |
Then |
||||
Yes |
A Proposal Hierarchy Is Most Likely Necessary |
||||
No |
Does the sponsor allow different rates for certain costs (outside of MIT's usual MTDC, FUNSN or other standard configurations)? |
||||
|
If |
Then |
|||
|
Yes |
A Proposal Hierarchy Is Most Likely Necessary or Helpful |
|||
|
No |
Does the sponsor require additional submission of a separate budget breakdown by task? |
|||
|
If |
Then |
|||
|
Yes |
A Proposal Hierarchy Is Most Likely Necessary or Helpful |
|||
|
No |
Proposal Hierarchy Should NOT be Necessary |
|||
Please contact the RAS Administrator for your DLC or ra-help@mit.edu for guidance on specific proposal scenarios.
* A proposal can be routed to multiple participating, non-lead units without using Proposal Hierarchy. See http://kc.mit.edu/category/faq/routing
** Anticipation of an Award Hierarchy structure does not necessitate a Proposal Hierarchy.