Nevada Education Department tells subrecipients: subawards are legally binding contracts; payments require full execution

The Nevada Department of Education's Grants Management Unit (GMU) used a regular office‑hour session to explain that subawards issued by the department are legally binding contracts and to review what subrecipients must provide before NDE can disburse funds.

Amber (Grants Management Unit staff) opened the session by saying the presentation would move from federal and state regulations to NDE's internal procedures and then to the components of the subaward packet. She told attendees that "subawards as legal contracts" means NDE must ensure both the department and each subrecipient meet statutory, regulatory and policy obligations before making payments.

The nut graf: The GMU walked through the legal sources that govern subawards — including 2 CFR 200 (Uniform Guidance/EDGAR), Nevada statutes and administrative code, the Nevada Grant Manual and the Nevada Grant Policy Manual — and tied those authorities to practical requirements: a complete notice of award, a scope of work, an approved budget, signed assurances, a vendor number, compliance monitoring and fully executed amendments for any material change.

At the top of the responsibilities list, NDE emphasized that it cannot issue payments until a subaward is "fully executed" — meaning all required signatures or attestations are in place. Amber quoted the grant manual language: "Fully executed grant agreements and grant agreement amendments are legally binding documents," and said state policy requires that changes to a subaward be handled by fully executed amendments. The GMU reiterated that Nevada operates primarily on a reimbursement basis: subrecipients must submit requests for reimbursement (RFRs) that match the approved grant budget and include backup documentation.

Presenters reviewed the standard contents of an NDE notice of award: subrecipient identity (including UEI), vendor number, project number, GAN/FAIN/CFDA identifiers when federal funds apply, the period of performance, dollar amount committed, the scope of work and the approved budget, plus the federal or state assurances the subrecipient must sign. The notice also sets payment and closeout rules, including monthly RFR timing and final financial reporting deadlines.

NDE provided specific timing and procedural clarifications that subrecipients raised during Q&A. The GMU said routine RFRs should be submitted by the 15th of each month for expenditures from the previous month. For final financial reports and closeout, Amber corrected a slide to state that for FY23 federal awards NDE expects final reports within 60 days after period end, while state grants generally have a 30‑day final reporting window; the office stressed it needs sufficient time after receiving subrecipient reports to compile state reporting obligations. The GMU also noted NDE cannot pay a subrecipient that lacks a vendor number assigned by the State Controller's Office.

On amendments and flexibility, the GMU explained the department must document changes to the original obligation, compensation, terms, expiration date or contract attachments through numbered, fully executed amendments. In response to questions, staff said the department is building ePage functionality to allow up to 5% shifting within a given object code without a formal amendment for awards managed in ePage (the flexibility will not apply to paper subawards). That feature must be coded by the ePage vendor and will come into effect only after NDE deploys and announces it.

NDE also discussed retroactive memos for start dates in limited circumstances: if a program's period of performance should begin before the subaward's final signature date, a retroactive memo can be used but the GMU said its preference is to have subawards executed before the funding period starts (many state subawards aim for July 1 start dates). The department explained multiyear intent does not guarantee year‑to‑year funding; carryforward and future fiscal availability remain subject to federal and state processes.

During the session participants raised operational concerns. A GMU slide showed the unit managing dozens of subawards near fiscal deadlines — for example, NDE reported trying to process 224 subawards to meet a July 1 objective and that, late in June, only about half had completed budgets in the GMU. Staff said moving more awards from paper into ePage is part of the plan to reduce late workloads and avoid retroactive memos.

On communications and support, NDE urged subrecipients to contact programmatic leads (for Title II matters the GMU named Dr. Silvana Gorton) or the universal grants info mailbox for questions, and said the GMU has committed to improved acknowledgement and to working toward a three‑day response window for inquiries. The office also announced upcoming dates for GMU events and asked attendees to complete a brief feedback survey.

Ending: The GMU closed the session by reiterating the core points: subaward packets must include specified documentation and signatures; reimbursements must match approved budgets and include backup; amendments are required for material changes; and the department is implementing ePage improvements to provide limited budget flexibility and to reduce administrative lag. Staff encouraged subrecipients to use the universal grants email and programmatic contacts for clarifications.