May 31, 2026

HSCVS SOP-OPS-DOC-001 Disaster Documentation & Records Management

HSCVS SOP-OPS-DOC-001 | Disaster Documentation & Records Management
HEAVEN SENT COMMUNITY SERVICES & VETERANS ASSISTANCE SOP-OPS-DOC-001 • Disaster Documentation & Records Management • EIN 41-2961092
Standard Operating Procedure

Disaster Documentation & Records Management

This SOP explains how HSCVS creates, organizes, protects, and retains disaster-related records so work in the field can be turned into clean reports, match, and reimbursement for federal, state, and private funders.

2 CFR 200 record retention FEMA PA & federal grants ready In-kind & match documentation Client & case records for LTR
DocumentSOP-OPS-DOC-001
Version1.0
EffectiveMarch 28, 2026
ReviewMarch 28, 2027
OwnerDirector of Operations
Approved byJoseph Ryan, CEO
Service areaPennsylvania to Florida and across the Gulf Coast to Texas
EIN41-2961092

1. Purpose, scope & principles

Why documentation matters

This SOP defines how HSCVS manages disaster-related documentation and records so that work in the field can be supported by evidence that meets federal, state, and private funder requirements.

It applies to all HSCVS disaster operations, including preparedness, response, and long-term recovery, and covers both paper and electronic records created by staff, volunteers, contractors, and partners under HSCVS leadership.

Principle. If it is not documented, funders and auditors may treat it as if it never happened, even when the work was real; this SOP makes documentation part of daily operations, not an afterthought.

2. Roles & responsibilities

Who owns which records

Organizational roles

  • CEO. Approves this SOP, signs major grant and cost-share agreements, and ensures organizational commitment to accurate records and audits.
  • Director of Operations (DO). SOP owner; ensures that operational leaders integrate documentation into daily workflow and that forms align across SOPs.
  • Finance & Grants Lead. Oversees financial, procurement, and match documentation for grants, including FEMA Public Assistance and other federal awards.
  • Program & Site Leads. Responsible for local logs, sign‑ins, incident reports, and program service documentation under their sites.

Disaster & LTR roles

  • Disaster Case Management / Casework Supervisors. Lead client and case record documentation in line with VOAD guidance and local LTRG expectations.
  • Records Coordinator (may be combined role). Maintains centralized filing structure, monitors retention timelines, and supports audits or monitoring visits.
  • All staff & volunteers. Create timely, truthful, and complete records using approved forms; report any loss or damage to records immediately.

3. What must be documented

Core categories
CategoryExamplesWhy it matters
Financial & procurementBudgets, invoices, payroll, purchase orders, bids/quotes, contracts, payment approvals.Supports grant billing, FEMA PA reimbursement, audits, and compliance with 2 CFR 200.
Volunteers & laborVolunteer applications, sign‑in logs, timesheets, staff time allocations for projects.Documents in‑kind support and labor used as match or cost share under grants.
In‑kind goods & servicesDonation offers, in‑kind receipts, valuation worksheets, distribution logs.Supports fair valuation and eligibility of donated goods/services as match when allowed.
Client & case recordsIntake forms, assessments, case plans, assistance records, release of information, closure notes.Show that aid was tied to documented disaster impacts, vulnerability, and coordinated LTR efforts.
Operational logsPOD shift reports, shelter occupancy, meal counts, incident logs, situation reports (SITREPs).Provide evidence of services delivered and resource use; inform after‑action reviews and planning.
Governance & agreementsMOUs, Data Sharing Agreements, LTRG bylaws, meeting minutes, authorizations, and policies.Show that HSCVS had authority, partnerships, and controls needed to do the work and share data.

4. Financial & procurement records

For grants, PA & audits

Financial records

  • Maintain ledgers that clearly separate disaster projects and grants from general operations so that costs can be traced to specific funding sources.
  • Keep supporting documentation (invoices, receipts, time sheets, mileage logs, bank statements, approvals) for all costs charged to a federal or state award.
  • Ensure that costs are necessary, reasonable, and consistent with organizational policies to be eligible for FEMA PA and other federal reimbursement.

Procurement & contracts

  • Document procurement steps, including quotes/bids, justification for vendor choice, and any emergency procurement decisions, in line with 2 CFR 200 Uniform Guidance.
  • Keep executed contracts, including required federal clauses where applicable, and track deliverables and payments against those contracts.
  • For FEMA PA or other programs, ensure that contracts and procurement files can show that work was eligible, properly competed when required, and tied to the declared incident.

5. Volunteer, in‑kind & match records

Turning efforts into match

Volunteer time, donated goods, and donated professional services can often be counted as cost share (“match”) if they meet grant rules, are used for eligible work, and are properly documented.

Volunteer documentation

  • Use standardized volunteer sign‑in logs and timesheets that show name, date, role, hours, and supervisor confirmation.
  • When volunteer labor is used as match, record the type of work performed and the location to show it is tied to eligible disaster activities.
  • Assign a reasonable hourly value for volunteer time following grant guidance or accepted local rates, and keep the calculation method on file.

In‑kind goods & services

  • Record donated commodities and equipment on in‑kind receipt forms that include donor, date, description, quantity, and estimated fair‑market value.
  • Document donated professional services (e.g., legal, clinical, construction) with time logs, scope descriptions, and agreed valuation.
  • Ensure that donated resources counted as match are not also paid for by other federal funds and are used for eligible activities within the grant period.

6. Client, case & LTRG records

People‑focused documentation

Client & case files

  • Case files for disaster casework and Disaster Case Management include intake, consent, assessment, case plan, assistance notes, and closure, following VOAD guidance.
  • Documentation shows that assistance is based on disaster-caused needs, not pre‑existing conditions alone, and that other resources (insurance, FEMA, SBA, etc.) were considered.
  • Files are organized consistently and stored securely, with clear naming conventions and case IDs.

LTRG & unmet needs records

  • Long‑Term Recovery Groups (LTRGs) maintain minutes, policies, and case review records that reflect coordinated decision‑making on assistance.
  • HSCVS keeps copies of any decisions, commitments, or distributions in which it is the implementing partner, linked to the underlying case file.
  • Data sharing is governed by written agreements and client consent, with clear rules on what can be shared in meetings and what remains confidential.

7. Record retention & access

How long to keep what

For federal awards, 2 CFR 200 requires that financial and program records be retained for at least three years from the date of submission of the final financial or performance report, with some important exceptions.

Retention standards

  • For federal grants and subawards, retain financial, supporting, and programmatic records for at least three years after the final report is submitted, or longer if the award terms require it.
  • For property and equipment purchased with federal funds, retain records for three years after final disposition of the property.
  • If there is an audit, claim, or litigation related to an award, retain relevant records until all issues are fully resolved, even if this extends beyond three years.

Access

  • Authorized representatives of federal agencies, pass‑through entities, auditors, and monitors must be given reasonable access to relevant records when required by award terms and law.
  • HSCVS maintains an access log for non‑routine access to sensitive records, particularly client files and detailed financial records.

8. Quality control, audits & monitoring

Staying ready, not scrambling

Internal quality checks

  • Supervisors periodically review samples of financial, volunteer, in‑kind, and case records for completeness and consistency.
  • Findings from reviews or after‑action reports are used to update forms, training, and SOPs.
  • Staff and volunteers receive training on documentation expectations before and during major incidents.

External audits & monitoring

  • HSCVS cooperates with required audits and site visits by federal, state, and private funders, providing the requested records promptly and securely.
  • Responses to audit findings or monitoring recommendations are documented, and corrective actions are tracked to completion.
  • Major findings that affect multiple programs may trigger organization‑wide improvements in documentation and controls.

9. Data security & privacy

Protecting sensitive information

Many disaster records contain personally identifiable information (PII) and sensitive financial or medical details; HSCVS protects this information in line with privacy laws, funder requirements, and VOAD guidance.

  • Paper records are stored in locked cabinets or rooms with controlled access; electronic records are stored in systems with appropriate user permissions and backups.
  • Client identifiers are limited in shared LTRG or VOAD discussions unless explicit consent and data‑sharing agreements allow more detail.
  • Records are disposed of securely (e.g., shredding or secure electronic deletion) at the end of the retention period, with documentation of destruction for sensitive files.

10. Demobilization & archive

Closing the paper trail well
  • Near the end of a disaster operation or grant period, HSCVS conducts a records reconciliation to ensure that financial, operational, and case records are complete and filed correctly.
  • Key records are indexed and archived in a central structure with clear labels so they can be located quickly for future audits or program design.
  • Lessons learned about documentation are integrated into after‑action reports and used to improve forms and SOP language for the next event.

Leader checklists

Quick reference for documentation

Incident start‑up documentation checklist

  • Confirm which grants, MOUs, and agreements apply to this incident and what documentation they require.
  • Ensure all sites have the correct sign‑in logs, timesheets, in‑kind forms, and incident logs.
  • Brief supervisors on how to complete and submit records daily or weekly.
  • Set up a simple digital or paper filing structure by incident and project so records are organized from day one.

Pre‑audit / pre‑closeout checklist

  • Verify that all costs charged to grants have underlying documentation (invoices, timesheets, approvals).
  • Confirm that in‑kind and volunteer match records are complete and valued correctly for any grants that plan to use them.
  • Check that case files and LTRG records are closed or transitioned and that consent and data‑sharing requirements were followed.
  • Ensure that retention timelines and storage locations are documented for each major funding source.

Appendix A – Documentation forms

Simple tools to standardize records

DOC-LOG-01 — Disaster Records Index

Use this to keep a one‑page snapshot of where key records for an incident are stored (both paper and electronic).

DOC-MATCH-01 — Match & In‑Kind Summary Sheet

Use this to summarize volunteer and in‑kind match for a specific grant or project.

Match typeDescriptionDocumentation locationEstimated value
Volunteer time
In‑kind goods
In‑kind services

DOC-AUD-01 — Audit & Monitoring Prep Checklist

Use this to track readiness for an announced audit or monitoring visit.

`); printWindow.document.close(); if(status) status.textContent='Print window opened.'; } function downloadForm(formBox){ const status=formBox.querySelector('.form-status'); const styles=document.querySelector('style') ? document.querySelector('style').innerHTML : ''; const html=`${document.title}${formBox.outerHTML}`; const blob=new Blob([html], {type:'text/html'}); const url=URL.createObjectURL(blob); const link=document.createElement('a'); const fileName=(formBox.getAttribute('data-form-id') || formBox.id || 'form') + '.html'; link.href=url; link.download=fileName; document.body.appendChild(link); link.click(); document.body.removeChild(link); URL.revokeObjectURL(url); if(status) status.textContent='Download started.'; } document.querySelectorAll('.form-box[data-form-id]').forEach(formBox=>{ loadForm(formBox); const saveBtn=formBox.querySelector('.btn-save'); const printBtn=formBox.querySelector('.btn-print'); const downloadBtn=formBox.querySelector('.btn-download'); if(saveBtn) saveBtn.addEventListener('click', ()=>saveForm(formBox)); if(printBtn) printBtn.addEventListener('click', (e)=>{e.preventDefault(); printForm(formBox);}); if(downloadBtn) downloadBtn.addEventListener('click', (e)=>{e.preventDefault(); downloadForm(formBox);}); });