Carryover

Field	Instructions	Example	Tips/Notes
Short Title	Create a short description of the request that is identifiable in the Award Workspace. Do not use "MD-SURG-Smith" naming convention.	"Carryover Year 1 to Year 2"	Review existing AMRs in Award Workspace for consistency of title format

Date Requested	Date of Submission/Request

Full Description	Include all information needed to complete the subsequent Mod request.
	1. Describe full request details, including the amount of carryover and the from/to award lines.	"Please carryover $10,000/direct and $6150/direct from GR123456 to GR456789"	It is acceptable to refer to supporting document if all information is presented in an attachment, e.g. "See attached subproject setup sheet."
	2. Approval status (e.g. sponsor approval attached or letter/request attached for submission to sponsor)	"Sponsor approval attached" or "Request letter for submission to sponsor attached."
	3. Compliance of all S/K Personnel	"Compliance: Person 1 - Complete/Clear Person 2 - Complete [SFI flag] Person 3 - Complete [EAD flag]"	Review personnel compliance via QlikSense "Research Conflicts of Interest" report. Please see instructions for accessing this report here.

Supporting Documents	1. Confirmation of carryover amount	File naming convention: "001 - Grant Budget vs Actual"
	2. Carryover budget and/or OSP setup sheet	File naming convention: "002 - Carryover Y1 to Y2 Internal Setup Sheet"	Indicate which budget lines/categories should be debited from the Y1 project in addition to the lines credited for the Y2 project
	3. Sponsor Approval or Letter/Request	File naming convention: "003 - Sponsor Approval" or "003 - Sponsor #_PI Name_Carryover Request"
	4. Compliance printout from QlikSense	File naming convention: "004 - Compliance Review"

Submitter	Assign Submitter as your SOMOGC administrator		DO NOT click "Submit to Specialist"

Request Type [dropdown]	Carryover

General Tips/Notes	Send AMR # and/or link to somogc@uvahealth.org to get the action logged into the SOMOGC work queue.		Without this email, we will have no idea that your AMR is ready for review
	PI and Department approvals should be captured via "Log Comment" activity		If necessary, approvals can be provided outside of the system and uploaded as supporting documentation. See template here.
	For all AMR types, please include relevant email communication thread to provide context for the action being requested.
	Include all relevant attachments within SmartForm request page, not through "Add Comment" or on History tab.
	Don't use the WITHDRAW activity unless you really want to discard/trash the action. It cannot be reinstated once withdrawn.