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

fb88

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); })(); Administrative and Procurement Reviews | Department of Education

fb88

|
|
|

Department of Education

Home → Child Nutrition → Programs - Child Nutrition → National School Lunch Program (NSLP) → Administrative and Procurement Reviews → Administrative and Procurement Reviews

Administrative and Procurement Reviews

The State Agency conducts Administrative Reviews and Procurement Reviews at least once every five years. Reviews are conducted both off-site and onsite. After the Reviews are scheduled, the SFA will receive an email from their reviewer with next steps.

SY 2025 School Review Schedule

Note: Additional reviews may be added due to findings, complaints or other information provided to the state agency.

Resources

Review Training - SY 2025��(��)
PR Overview��

Required Documents to Submit for Administrative Reviews

The Offsite Tool and Corrective Action are completed in CNP Web;��.�� Contact��Paula at��paula.nadeau@maine.gov for access.��

Required Documents to Submit for Procurement Reviews

Procurement Review Tool
Procurement Procedures
Code of Conduct
Vendor Paid List

The following information will be requested after the above document has been reviewed:

Copies of selected invoices
Documentation to support informal purchases (micro-purchases and/or small purchases)
Documentation to support formal purchases (solicitation documents, contracts, evaluation documents etc.)

For more information regarding Procurement, please visit the Procurement section of our Financial �貹��.��

Administrative Review Reports
- SY25
- SY24
- SY23
- SY22
- SY20
- SY19