FAQs: Hierarchy

What are some Key Points to know about hierarchy proposal creation?

An “Initiating Child” proposal is created first and the Parent will be generated from it. Other child proposals are created and linked to the parent.

The lead unit of the Initiating Child proposal determines the Lead Unit of the hierarchy parent.

PI of the Hierarchy Parent is determined by PI on Initiating Child at the time the hierarchy is created.

**Determine the PI of entire project before creating hierarchy; this individual must be the PI on the initiating child.**

NOTE:

  • Do not delete personnel from the Hierarchy Parent – maintain personnel from within the children and sync to Parent.
  • Certifications (and Notify to Certify) must be done at the Parent.
  • Questionnaires must be done at the Parent.

Linking and Unlinking

Changes to the Budget are made in the child proposals. Those changes are then synced up to the parent proposal. Changes to the budget cannot be made directly in the parent proposal with the ONLY exceptions of Modular Budgets and Budget Settings Include Cost Share and selection for Modular budget. Please contact ra-help@mit.edu with any questions.

  • Once linked child proposals remain editable. Additional personnel, attachments and budget edits need to be synced to parent.
  • Do not unlink lead/initiating child from the hierarchy without contacting ra-help@mit.edu first. This should not normally be done as it may alter the parent so its remaining data is no longer correct.
  • Do not unlink all children from the parent unless you plan to create a new parent. A parent cannot be relinked once all children are severed; it is put into Canceled status which is a final and irreversible status.

How do I determine if I need to use Proposal Hierarchy?

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.

Subscribe to Hierarchy