capturing changes to paf after proposal is submitted to the sponsor but prior to award option 1 –...

6
Capturing Changes to PAF after Proposal is Submitted to the Sponsor but PRIOR to Award Option 1 – Budget change =>20% ( or other triger) 1.PAF sent back by ORSP so the PI team can fix the PAF. Changes are captured on the PAF per ORSP SOP 300.01 Option 2 – All other changes prior to award are to be handled per 2 nd FAQ of ORSP SOP 300.01 (item 1 below) and LSA Process (item 2 below) 2.Revised Proposal Documents which are required by a Sponsor, but do not reflect the changes listed in this policy, should be uploaded to the applicable eRPM PAF record via a Posted Comment, and you should include your ORSP Project Representative and Dean’s Office as a Posted Comment recipient. THIS INCLUDES ALL CHANGES NOT JUST BUDGET CHANGES. 3.Commitment changes (ie.budget amount, subcontract amount, subproject grant amount(s), and effort will be added to MUD fields.

Upload: claire-glenn

Post on 18-Jan-2016

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Capturing Changes to PAF after Proposal is Submitted to the Sponsor but PRIOR to Award Option 1 – Budget change =>20% ( or other triger) 1.PAF sent back

Capturing Changes to PAF after Proposal is Submitted to the Sponsor

but PRIOR to Award

Option 1 – Budget change =>20% ( or other triger)1. PAF sent back by ORSP so the PI team can fix the PAF. Changes are captured on the PAF per ORSP SOP 300.01

Option 2 – All other changes prior to award are to be handled per 2nd FAQ of ORSP SOP 300.01 (item 1 below) and LSA Process (item 2 below)

2. Revised Proposal Documents which are required by a Sponsor, but do not reflect the changes listed in this policy, should be uploaded to the applicable eRPM PAF record via a Posted Comment, and you should include your ORSP Project Representative and Dean’s Office as a Posted Comment recipient. THIS INCLUDES ALL CHANGES NOT JUST BUDGET CHANGES.

3. Commitment changes (ie.budget amount, subcontract amount, subproject grant amount(s), and effort will be added to MUD fields.

Page 2: Capturing Changes to PAF after Proposal is Submitted to the Sponsor but PRIOR to Award Option 1 – Budget change =>20% ( or other triger) 1.PAF sent back

Capturing Changes to PAF at Award

Option 1 – Change of =>20% between PAF and award1. Follow process in ORSP SOP 400.012. LSA Research Office will require the following prior to their approval:

• Explanation of how budget cut affects aims of project, revised budget and budget justification (posted to PAF via post a comment)

• Update MUD screen for budget amount, subcontract amount, subproject grant amounts(s), and effort

Option 2 – Change of <20% between PAF and award3. LSA Research Office will contact RA requesting the following:

• Copy of completed 7471 (which is required via the PAN). Should be upload via post a comment in eRPM with us selected as comment recipient

• Update MUD screen for budget amount, subcontract amount, subproject grant amounts(s), and effort

Option 3 – No Change between PAF and award4. No updates to MUD5. LSA does not need to see a copy of 7471

Page 3: Capturing Changes to PAF after Proposal is Submitted to the Sponsor but PRIOR to Award Option 1 – Budget change =>20% ( or other triger) 1.PAF sent back
Page 4: Capturing Changes to PAF after Proposal is Submitted to the Sponsor but PRIOR to Award Option 1 – Budget change =>20% ( or other triger) 1.PAF sent back
Page 5: Capturing Changes to PAF after Proposal is Submitted to the Sponsor but PRIOR to Award Option 1 – Budget change =>20% ( or other triger) 1.PAF sent back
Page 6: Capturing Changes to PAF after Proposal is Submitted to the Sponsor but PRIOR to Award Option 1 – Budget change =>20% ( or other triger) 1.PAF sent back