[lstac] Assurances question

Wed Nov 5 06:04:36 PST 2025

In Georgia, we operate just like Ohio with keeping them separate. It was
also a process I inherited. We used to federal assurances annually and now
do it at award along with the other required documents.

[image: logo with link to Georgia Public Library Service website]
<https://georgialibraries.org/>

Shannan R. Furlow, MLIS

Director of LSTA and Sponsored Programs

------------------------------

Georgia Public Library Service

2872 Woodcock Blvd, Suite 250 | Atlanta, GA 30341

(404) 235-7137 | sfurlow at georgialibraries.org

[image: logo with link to Georgia Public Library Service Facebook page]
<https://www.facebook.com/georgialibraries>[image: logo with link to
Georgia Public Library Service Instagram page]
<https://www.instagram.com/georgialibraries/>[image: logo with link to
Georgia Public Library Service LinkedIn page]
<https://www.linkedin.com/company/georgia-public-library-service/>[image:
logo with link to Georgia Public Library Service Threads page]
<https://www.threads.net/@georgialibraries>

Join our email list <http://georgialibraries.org/subscription> for stories
of Georgia libraries making an impact in our communities.

On Wed, Nov 5, 2025 at 8:59 AM JRegensburger--- via lstac <
lstac at omls.oregon.gov> wrote:

> In Ohio, we maintain the assurances/certifications document separate from
> the contract/grant management requirements document.
>
>
>
> Neither document are required to apply for a grant, but both are required
> from the subrecipients if a grant is awarded.
>
>
>
> I expect there are arguments for doing it one way over the other, but
> honestly, I do it like that mostly because that’s the method I inherited,
> and it seems to work OK.
>
>
>
> Jeff
>
>
>
> [image: A picture containing text Description automatically generated]
>
>
>
> *Jeff Regensburger (he/him/his)*
>
> *Library Consultant/LSTA Coordinator, Library Programs & Development*
>
> State Library of Ohio
>
> 274 E. 1st Avenue
>
> Columbus, OH 43201
>
> T: 614.644.6863
>
> jregensburger at library.ohio.gov
>
> library.ohio.gov
>
>
>
> *From:* lstac <lstac-bounces at omls.oregon.gov> *On Behalf Of *Melanie Boyd
> via lstac
> *Sent:* Tuesday, November 4, 2025 7:19 PM
> *To:* Reish, Karren (MDE) <ReishK at michigan.gov>
> *Cc:* lstac at omls.oregon.gov
> *Subject:* Re: [lstac] Assurances question
>
>
>
> Hi Karren,
>
>
>
> Thanks for starting this convo. I've been at Utah State Library for about
> 8 months, and need to update all our LSTA docs and website... I'll be
> watching replies.
>
>
>
> We currently have the Assurances in our Pre-Application documents. You can
> see how the the doc list is currently organized here
> <https://library.utah.gov/lsta/current-grant/>on our website (which is
> another project). The assurances are also linked in each LSTA subgrant
> application, and the applicant digitally confirms them by typing their name
> into and answer box as part of that process. They are also referenced in
> our LSTA subgrantee contracts. Additionally, in our Certified Library
> process also covers these items, and certification is a requirement for
> funding eligibility.
>
>
>
> I'm about to do my first LSTA Adminstration training, and hadn't thought
> about including the Assurances there. In our case, I don't see a need to
> review these as part of the grant administration training beyond perhaps a
> bullet point mentioning them as required. If I were in your shoes, I
> wouldn't rewrite the manual either. What I would do is make sure they're
> referenced within attached in an addendum to your contracts. It happens
> that the person applying for the grant sometimes isn't a director, and just
> signs the box to get the application submitted without realizing the full
> obligation. Including a reference or addendum in the contract assures that
> the responsible and accountable parties are duly  informed.
>
>
>
> Melanie
>
>
>
> On Tue, Nov 4, 2025 at 1:57 PM Reish, Karren (MDE) via lstac <
> lstac at omls.oregon.gov> wrote:
>
> I was dutifully checking the other sample assurances against mine and have
> a question for the hive mind. Some folks are putting grant management
> requirements together with federal assurances into one document. I’m doing
> federal assurances as one document that is signed as part of the
> application. I also have grant management requirements in a grant
> administration manual. We are under the Department of Education that has a
> standard 2-page form for grant awards. On that form, I can note specific
> program requirements, and I say must follow the grant admin manual and the
> signed assurances.
>
>
>
> Any thoughts on why to do it one way or another? I do like the one
> document for clarity, but I really don’t want to rewrite my admin manual.
>
>
>
> Karren Reish
>
> Library Grants Coordinator
>
> Library of Michigan
>
> 517-241-0021 / www.mi.gov/lsta
>
> [image: Michigan's Top 10 Strategic Education Plan]
> <https://www.michigan.gov/mde/resources/michigans-top-10-strategic-education-plan>
>
> [image: Michigan.gov/Vote logo Description automatically generated]
> <https://mvic.sos.state.mi.us/>
>
> Get personalized voter information on early voting and other topics at
> Michigan.gov/Vote <https://mvic.sos.state.mi.us/>.
>
>
>
>
>
>
>
> *CAUTION:* This is an external email and may not be safe. If the email
> looks suspicious, please do not click links or open attachments and forward
> the email to csc at ohio.gov or click the Phish Alert Button if available.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omls.oregon.gov/pipermail/lstac/attachments/20251105/f6a7cad9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 22781 bytes
Desc: not available
URL: <https://omls.oregon.gov/pipermail/lstac/attachments/20251105/f6a7cad9/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 18127 bytes
Desc: not available
URL: <https://omls.oregon.gov/pipermail/lstac/attachments/20251105/f6a7cad9/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 12580 bytes
Desc: not available
URL: <https://omls.oregon.gov/pipermail/lstac/attachments/20251105/f6a7cad9/attachment-0002.png>