13 CSR 110-2.080 - Runaway and Absconding Youth

PURPOSE: This rule establishes formal procedures to be followed when a youth runs away from a residential facility or has absconded from community care or aftercare, and is apprehended. It is recognized that local procedures followed in these circumstances vary from facility-to-facility. Each facility shall write procedures which can be logically and consistently followed.

(1) These procedures are to be followed in the case of runaways.
(A) Immediately upon the discovery and verification that a youth has run away, the premises shall be secured and an immediate search will be conducted. The local police shall be notified and given the information necessary to help locate the youth.
(B) Upon apprehension or return to placement the case will be reassessed and necessary treatment intervention made and documented.
(C) If the youth is not apprehended during the initial search period, then the need for a pickup and detention warrant will be ascertained.
(D) A critical incident report shall be prepared by the site supervisor or service coordinator. Upon apprehension, the pickup order/warrant will be canceled and notification given to appropriate local law enforcement, local juvenile officer, parent(s)/guardian(s), and service coordinator.
(E) If the youth is not apprehended or does not return within fourteen (14) days, the youth will be placed on the inactive roll by the Division of Data Processing until apprehension or appropriate discharge.
(F) In the event the youth is not apprehended, has reached age seventeen (17), has passed the discharge date of any determinate sentence, if applicable, and has been on runaway status for six (6) consecutive months, the Division Director, Deputy Director, Regional Administrator, or Deputy Compact Administrator shall discharge the youth.
(2) These procedures are to be followed when a youth absconds from aftercare.
(A) Upon notification that a youth has absconded, the service coordinator shall assess the immediate situation, consulting with parent(s) or guardian(s) and the service coordinator's supervisor to determine the necessary intervention. Upon completion of the assessment, if appropriate, the service coordinator shall request the apprehension and detention of the youth by law enforcement.
(B) Upon apprehension or return to placement, the case will be reassessed and necessary treatment intervention documented.
(C) If the youth is apprehended before central office has been notified of the runaway, this fact should be indicated on the report. If the youth was not apprehended and central office was notified, then a follow-up report should be sent to the appropriate supervisor indicating the youth is back in DYS custody.
(D) In the event a pickup order/warrant was issued, a letter will be sent to officially cancel the pickup order/warrant.
(E) If a letter was sent to various officials and the parent(s)/guardian(s) notifying them of the youth's abscondence, a letter will also be sent to notify them that the youth has been apprehended.
(F) In the event a youth is not apprehended, has reached age seventeen (17), has passed the discharge date of any determinate sentence, if applicable, and has been on abscondence status for three (3) consecutive months, the Division Director, Deputy Director, Regional Administrator, or Deputy Compact Administrator shall discharge the youth.

Notes

13 CSR 110-2.080
AUTHORITY: sections 219.036 and 660.017, RSMo 2016.* Original rule filed Dec. 30, 1975, effective Jan. 9, 1976. Amended: Filed Feb. 10, 2000, effective Aug. 30, 2000. Amended: Filed April 18, 2018, effective Nov. 30, 2018.
AUTHORITY: section 219.036, RSMo 1994.* Original rule filed Dec. 30, 1975, effective Jan. 9, 1976. Amended: Filed Feb. 10, 2000, effective Aug. 30, 2000. Amended by Missouri Register October 15, 2018/Volume 43, Number 20, effective 11/30/2018

State regulations are updated quarterly; we currently have two versions available. Below is a comparison between our most recent version and the prior quarterly release. More comparison features will be added as we have more versions to compare.


No prior version found.