Community Documentation Infrastructure

The success of both international diplomatic pressure and domestic FTCA litigation relies entirely on the quality, security, and structured preservation of the underlying documentation. Community organizations and human rights defenders have developed sophisticated architectures to transform isolated reports of abuse into actionable legal archives.

---

Centralized Documentation Systems

Moving Beyond Narrative

To establish the "widespread and systematic" patterns necessary for complex litigation or UN inquiries, organizations must move beyond narrative storytelling toward structured data methodologies.

HURIDOCS Events Standard Formats

The HURIDOCS (Human Rights Information and Documentation Systems) methodology dissects complex human rights events into relational data points:

Data Point	Description
Victim	Identification of affected individual
Perpetrator	Badge number, unit, matching across incidents
Violation Type	Specific abuse categorization
Location	Precise geographic coordinates
Date/Time	Temporal specificity
Source	How information was obtained
Corroboration	Supporting evidence links

Uwazi Platform

Uwazi is an open-source database designed specifically for human rights defenders.

Key Features:

Feature	Function
Custom Data Models	Design fields specific to immigration documentation
Multi-Format Indexing	PDFs, videos, sworn affidavits, photographs
Relationship Mapping	Visual connections between enforcement actions
Access Controls	Strict encryption and role-based permissions
Public/Private Layers	Separate sensitive data from advocacy reports
Timeline Visualization	Chronological pattern display
Geographic Mapping	Incident location visualization

Database Design Principles

Essential Fields for Immigration Documentation:

INCIDENT RECORD
├── Case ID (unique identifier)
├── Date/Time of incident
├── Location (facility, address, coordinates)
├── Incident Type (raid, detention, deportation, abuse)
├── Victim Information
│   ├── Anonymous ID
│   ├── Demographic data
│   └── Status (detained, deported, released)
├── Perpetrator Information
│   ├── Badge number(s)
│   ├── Agency (ICE, CBP, other)
│   ├── Physical description
│   └── Unit/facility assignment
├── Witnesses
│   ├── Contact information (encrypted)
│   └── Statement status
├── Evidence
│   ├── Document links
│   ├── Hash values
│   └── Chain of custody reference
├── Legal Status
│   ├── Complaints filed
│   ├── Litigation status
│   └── International submissions
└── Pattern Links
    └── Related incidents

---

Secure Evidence Storage

Mobile Capture: Tella

Tella is a secure mobile application for human rights documentation in hostile environments.

Security Architecture:

Feature	Protection
Encrypted Vault	Evidence stored in password-protected container
Bypass Camera Roll	Photos/video never touch standard device storage
Camouflage Mode	App disguised as calculator or other utility
Quick Exit	Rapid vault lock if device seized
Offline Sync	Secure capture without internet
Remote Wipe	Emergency destruction capability

Evidence Capture Workflow

FIELD CAPTURE (Tella)
        ↓
ENCRYPTED STORAGE (Local vault)
        ↓
HASH GENERATION (SHA-256)
        ↓
SECURE SYNC (When safe connection available)
        ↓
BACKEND DATABASE (Uwazi/ODK)
        ↓
LOCAL PURGE (Evidence removed from device)

Berkeley Protocol Compliance

Digital evidence must meet Berkeley Protocol on Digital Open Source Investigations standards:

1. Identification - Systematic location of potential evidence
2. Collection - Acquisition preserving integrity
3. Preservation - Protection against alteration
4. Analysis - Forensic examination
5. Presentation - Court-admissible format

Cryptographic Authentication

Hash Generation:

• Generate SHA-256 hash at moment of capture
• Record hash in separate secure log
• Store hash on immutable ledger (blockchain/DLT) if available
• Any file alteration changes hash value

Verification:

• Regenerate hash when evidence accessed
• Compare against original hash
• Mismatch indicates tampering

---

Network Coordination

Regional Documentation Networks

Documentation efforts are exponentially more effective when coordinated across organizations.

Benefits of Coordination:

• Identify geographic patterns across jurisdictions
• Pool resources for complex investigations
• Share methodological expertise
• Strengthen advocacy with aggregate data
• Prevent duplication of effort

Data Sharing Agreements

Sharing data introduces risks. Organizations must utilize strict agreements specifying:

Element	Specification
Data Categories	What types of data are shared
Anonymization Standards	How identifying information is protected
Use Limitations	Permitted purposes for shared data
Security Requirements	Minimum protection standards
Access Controls	Who can access shared data
Retention Periods	How long data is kept
Destruction Protocols	How data is deleted when no longer needed

Coalition Structures

Effective Models:

Model	Function
Lead Organization	Central coordinator with technical capacity
Regional Nodes	Local documentation partners
Legal Partners	Privilege protection and litigation capacity
Technical Support	Database management and security
Advisory Board	Strategic guidance and oversight

---

Legal Partnership Models

Why Legal Partnerships Matter

Establishing formal partnerships with legal organizations provides critical protections for documentation efforts.

Attorney-Client Privilege

When community documentation operates under attorney direction:

• Communications are privileged
• Work product is protected
• Government cannot subpoena materials
• Advocates cannot be compelled to testify

Attorney Work Product Doctrine

Materials prepared in anticipation of litigation are protected from discovery.

Requirements:

• Attorney involvement in documentation design
• Clear litigation purpose documented
• Maintained in attorney's files or under attorney control

Partnership Structure

LEGAL ORGANIZATION
├── Provides privilege umbrella
├── Designs documentation protocols
├── Reviews evidence for litigation
└── Files cases using community evidence
        ↓
COMMUNITY ORGANIZATION
├── Conducts field documentation
├── Follows attorney-approved protocols
├── Maintains chain of custody
└── Transfers evidence to legal partner

Pro Bono Networks

Connect with:

• ACLU affiliates
• National Immigration Law Center
• American Immigration Lawyers Association (AILA)
• Law school clinics
• Pro bono programs at major law firms

---

Template Development

Incident Report Template

INCIDENT REPORT FORM

Report ID: _______________
Date/Time of Incident: _______________
Date/Time of Report: _______________
Documenter: _______________

LOCATION
Address: _______________
Facility Name (if applicable): _______________
GPS Coordinates: _______________

INCIDENT TYPE
[ ] Raid/Arrest
[ ] Detention Condition
[ ] Deportation
[ ] Family Separation
[ ] Physical Abuse
[ ] Medical Neglect
[ ] Other: _______________

AFFECTED INDIVIDUAL(S)
Anonymous ID: _______________
Age Range: _______________
Gender: _______________
Nationality: _______________
Current Status: _______________

PERPETRATOR IDENTIFICATION
Agency: [ ] ICE [ ] CBP [ ] Other: _______
Badge Number(s): _______________
Physical Description: _______________
Vehicle/Unit: _______________

INCIDENT DESCRIPTION
(Factual, chronological narrative)
_______________________________________________

WITNESSES
Name/Contact: _______________ (encrypted storage)
Willing to Provide Statement: [ ] Yes [ ] No

EVIDENCE COLLECTED
[ ] Photographs (Hash: _______________)
[ ] Video (Hash: _______________)
[ ] Audio (Hash: _______________)
[ ] Documents (Hash: _______________)

CHAIN OF CUSTODY INITIATED: [ ] Yes

Consent Waiver Template

INFORMED CONSENT FOR DOCUMENTATION

I, _______________, understand that:

1. This organization is documenting immigration
   enforcement incidents for [advocacy/legal purposes].

2. My information may be used for:
   [ ] Legal proceedings
   [ ] International human rights submissions
   [ ] Advocacy reports (anonymized)
   [ ] Research (anonymized)

3. I have the right to:
   - Withdraw consent at any time
   - Review information about me
   - Request anonymization
   - Decline to answer questions

4. Risks include:
   - Potential subpoena of records
   - Possible identification despite protections
   - Emotional difficulty in recounting events

5. Protections include:
   - Secure storage of information
   - Legal privilege where applicable
   - Anonymization in public reports

CONSENT:
[ ] I consent to documentation and use as described above.
[ ] I request the following limitations: _______________

Signature: _______________
Date: _______________
Witness: _______________

Chain of Custody Receipt

CHAIN OF CUSTODY RECEIPT

Evidence ID: _______________
Case Reference: _______________

ITEM DESCRIPTION
Type: _______________
Quantity: _______________
Condition: _______________
Hash Value (if digital): _______________

TRANSFER RECORD

Released By: _______________
Organization: _______________
Date/Time: _______________
Signature: _______________

Received By: _______________
Organization: _______________
Date/Time: _______________
Signature: _______________

Purpose of Transfer: _______________
Storage Location: _______________

CONDITION UPON RECEIPT
[ ] Unchanged from description
[ ] Changes noted: _______________

---

Federal Rules of Evidence Compliance

Admissibility Requirements

Documentation must meet FRE standards for potential litigation use:

Rule	Requirement
FRE 401	Evidence must be relevant
FRE 402	Only relevant evidence admissible
FRE 403	Probative value must outweigh prejudice
FRE 802	Hearsay generally inadmissible (with exceptions)
FRE 901	Authentication required
FRE 902	Self-authentication categories
FRE 1002	Best evidence rule for writings/recordings

Best Practices for Admissibility

1. Contemporaneous recording - Document at or near time of event
2. Witness availability - Maintain contact for testimony
3. Original preservation - Keep originals, work from copies
4. Metadata protection - Don't alter file metadata
5. Clear chain of custody - Document all handling

---

Related Pages

• International Accountability Hub
• Crimes Against Humanity Documentation
• Individual Agent Accountability

---

This guide is for informational purposes only and does not constitute legal advice. Organizations should consult with qualified counsel regarding documentation protocols and legal partnerships.