Trainings & Deployments From: LCMS Disaster Response & Training

This is setup for the sole purpose of providing an avenue for LERT volunteers to procure (or renew) your LERT background check in preparation for future deployments.

Please complete this process only if you intend to volunteer for an upcoming LERT deployment.

If you would like to procure your LERT background check (or need to renew an expired LERT background check) so that you are prepared to respond to future LERT Deployments, please use this event to do so.

As you try to sign up for this event, you will be redirected to the Sterling Volunteers site to enter your information. LCMS Disaster Training covers the cost of LERT background checks. It is made available to you at no cost.

NOTE: there is no physical event connected with this signup. The sole purpose is provide an avenue for you to obtain (or renew) your background check before a future LERT Deployment. You do not need to sign up for this event after your background check is complete.

Please note that the background check is good for one (1) year and must be renewed annually if you wish to keep current.

LERT Background Checks are required for all LERT Deployments in which the following activities/conditions are taking place:

Those who work with youth (also following all LERT Youth Guidelines) Those working in disaster victims' homes Those engaged in the recovery of disaster victims' personal property Those who are staying overnight in an LCMS LERT volunteer housing camp

You can read our blog post about background checks here: Why Background Checks? | LCMS Disaster Response (lcms-lert.org)

+++

If you have questions regarding your background check, LERT volunteers should contact Sterling Volunteers at:

855-326-1860, option 3 (8 a.m. - 8 p.m. EST) or TheAdvocates@sterlingvolunteers.com

+++

 

This is setup for the sole purpose of providing an avenue for LERT volunteers to procure (or renew) your LERT background check in preparation for future deployments. You should not sign up for this event because there is no active deployment associated with it.