Shelter Project

Directions: In five double-spaced pages, describe your program's security/disaster plan (including a description of the building’s security features, if any). Please avoid using bullet-points. Rather, submit the information in narrative form. Although this is not a formal paper, be sure to cite all supporting information (using APA format), where appropriate.
IMPORTANT: Consult the TAC for specific requirements.Copy and paste the following links to access Tex. Admin. Code §379.626, 379.503, and 379.504, respectively:

https://texreg.sos.state.tx.us/public/readtac$ext.TacPage?sl=R&app=9&p_dir=&p_rloc=&p_tloc=&p_ploc=&pg=1&p_tac=&ti=1&pt=15&ch=379&rl=626
https://texreg.sos.state.tx.us/public/readtac$ext.TacPage?sl=R&app=9&p_dir=&p_rloc=&p_tloc=&p_ploc=&pg=1&p_tac=&ti=1&pt=15&ch=379&rl=503
https://texreg.sos.state.tx.us/public/readtac$ext.TacPage?sl=R&app=9&p_dir=&p_rloc=&p_tloc=&p_ploc=&pg=1&p_tac=&ti=1&pt=15&ch=379&rl=504

Address the various HHSC-identified security threats/disaster situations staff may encounter (these included BUT ARE NOT LIMITED TO: batterer/intruder on the property, assaults, threatening phone calls, data security, power outages, floods, fires, etc.). Use sub-headings to separate the sections.**

Also: Be mindful of client and building location confidentiality when responding to emergency situations. [Hint: For liability reasons, and as a matter of protocol, you might consider having staff notify the Shelter Manager or other Supervisor-on-Call once the emergency/security threat has been resolved.]

*A Supervisor-on-Call may be an Assistant Shelter Manager or a manager from another program within the agency (ex. the Counseling Manager, etc.) who shares an on-call, after-hours rotation with the Shelter Manager. As appropriate, the Shelter Manager or SOC should, then, inform the Executive Director.

**For disasters/evacuations:

Consider networking with another shelter to temporarily accommodate your clients. (This is the best case scenario since other shelter programs are cognizant of clients' safety and confidentiality needs. Again, for the most extreme disaster scenarios, think about client transportation/relocation, agency records, maintaining the hotline, and food and supplies, etc.).

The hotine can be transferred to the National Domestic Violence Hotline.

Note also that buses are difficult to secure in times of emergency. See Powerpoint #4 and TAC §379.626 for HHSC rules concerning any disruption of shelter services. Be sure to include this information in your disaster plan.) Use sub-headings to separate each section (ex. Fires, Flooding, etc.).

The following resources may also be of use. HOWEVER, ALL INFORMATION SHOULD BE PRESENTED ENTIRELY IN YOUR OWN WORDS. Neglecting to follow these instructions/plagiarizing other sources will result in a failing grade.

1.) National Network to End Domestic Violence Template Policy and Tipsheets:

a.) Template Policy: Victim Confidentiality Considerations for Domestic Violence and Sexual Assault Programs

When Responding to Rare or Emergency Situations:

http://tools.nnedv.org/template/policies/134-template-policy-victim-confidentiality-considerations-for-domestic-violence-and-sexual-assault-programs-when-responding-to-rare-or-emergency-situations

2.) (For disasters) http://www.nsvrc.org/sites/default/files/Publications_NSVRC_Guides_Sexual-Violence-in-Disasters_A-planning-guide-for-prevention-and-response.pdf.

3.) (For disasters) http://vawnet.org/special-collections/DisasterPrep.php

4.) (For security considerations) Arizona Coalition Against Domestic Violence. (2000). Best practices manual for domestic violence programs, pp. 56-57. Retrieved from: http://vawnet.org/domestic-violence/summary.phpdoc_id=897&find_type=web_desc_GC

5.) Computers and Networks (for data security):

http://tools.nnedv.org/tipsheets-charts/tipsheets/77-computersnetworks

6.) Cloud Computing (for data security):

http://tools.nnedv.org/tipsheets-charts/tipsheets/107-cloudcomputing