, but this code // executes before the first paint, when

ÃÛÌÒapp

is not yet present. The // classes are added to so styling immediately reflects the current // toolbar state. The classes are removed after the toolbar completes // initialization. const classesToAdd = ['toolbar-loading', 'toolbar-anti-flicker']; if (toolbarState) { const { orientation, hasActiveTab, isFixed, activeTray, activeTabId, isOriented, userButtonMinWidth } = toolbarState; classesToAdd.push( orientation ? `toolbar-` + orientation + `` : 'toolbar-horizontal', ); if (hasActiveTab !== false) { classesToAdd.push('toolbar-tray-open'); } if (isFixed) { classesToAdd.push('toolbar-fixed'); } if (isOriented) { classesToAdd.push('toolbar-oriented'); } if (activeTray) { // These styles are added so the active tab/tray styles are present // immediately instead of "flickering" on as the toolbar initializes. In // instances where a tray is lazy loaded, these styles facilitate the // lazy loaded tray appearing gracefully and without reflow. const styleContent = ` .toolbar-loading #` + activeTabId + ` { background-image: linear-gradient(rgba(255, 255, 255, 0.25) 20%, transparent 200%); } .toolbar-loading #` + activeTabId + `-tray { display: block; box-shadow: -1px 0 5px 2px rgb(0 0 0 / 33%); border-right: 1px solid #aaa; background-color: #f5f5f5; z-index: 0; } .toolbar-loading.toolbar-vertical.toolbar-tray-open #` + activeTabId + `-tray { width: 15rem; height: 100vh; } .toolbar-loading.toolbar-horizontal :not(#` + activeTray + `) > .toolbar-lining {opacity: 0}`; const style = document.createElement('style'); style.textContent = styleContent; style.setAttribute('data-toolbar-anti-flicker-loading', true); document.querySelector('head').appendChild(style); if (userButtonMinWidth) { const userButtonStyle = document.createElement('style'); userButtonStyle.textContent = `#toolbar-item-user {min-width: ` + userButtonMinWidth +`px;}` document.querySelector('head').appendChild(userButtonStyle); } } } document.querySelector('html').classList.add(...classesToAdd); })(); Closing out the Grant | ÃÛÌÒapp

ÃÛÌÒapp

Skip to main content

Closing out the Grant

Close Out

Closing out the grant will be a cinch, provided you have maintained all documentation throughout the life of the grant and have spent all the money. Filing the last annual report, drawing down the remaining funds, completing the last annual audit, and receiving the final correspondence from your programs officer are several steps involved with closing out your grant.

Every grant has a beginning and ending date as stipulated by the funding agency. The Grants and Foundation Relations department will contact you 90 to 60 days prior to the close of your reward to assist you.

If you feel that it is not feasible to complete the project by the end of the designated period and you have funds remaining on your account, in most cases you may request a no-cost extension from the funding agency. If this is done in a timely fashion, many agencies will allow you to expend funds beyond the final date of your original grant. Please contact Grants and Foundation Relations Office prior to requesting a no-cost extension. If you spend funds after the closing date of the grant without receiving permission in advance, the funding agency is likely to refuse reimbursement to the university.  

It is helpful to use a 60-day target date to prepare for closeout. You need to anticipate final expenditures, particularly as they relate to payroll, benefits and purchasing. The Grant and Foundation Relations staff will assist you as needed.