Evidence Page Template
Snapshot
The Evidence Page Template is the required structure for documenting individual records on EpsteinWiki. Use it for EFTA documents, court filings, FBI records, financial records, emails, photographs, flight records, address books, telephone records, property files, corporate records, FOIA releases, audio, video, screenshots, and other source material relevant to the Epstein investigation.
Every Evidence page must identify the record, explain its provenance, link readers to the original material, summarize what it contains, and state what it does and does not prove. The goal is not to make a document sound dramatic. The goal is to make the evidence understandable, traceable, and difficult to misrepresent.
When an EFTA number exists, link directly to the record using this format:
https://epstein-data.com/EFTA######## is an illustrative URL pattern only. Open the actual record, verify its identifier and contents, and copy its exact URL. Never publish the placeholder or construct a link from a guessed number.
For each citation, use the identifier and description verified against the actual record. The template supplies no example record as evidence.
How to Use This Template
Set the WordPress title separately using the title guidance below. Copy only the literal HTML inside the single code block into an HTML-capable article editor or Custom HTML block. Do not copy the outer code block, and do not add an H1 to the article body. Replace and remove every bracketed writing prompt before publication. Delete any field or section that truly does not apply, but do not remove a required evidentiary limitation merely because the document appears persuasive. Keep the required Snapshot, introduction, Key Takeaways, Conclusion, Questions and Answers, and Sources structure.
Read the complete record before writing. Do not summarize a search snippet, extracted entity list, isolated screenshot, automated answer, or single page from a longer document as though it represents the complete source.
Use a direct Epstein Data record link whenever an EFTA identifier is available. Use Epstein Data search to locate the document, the full text corpus to compare extracted text, the concordance database to examine available metadata, and the coverage map to investigate numbering gaps.
If no EFTA number exists, link the closest available primary source. Appropriate sources may include the United States Department of Justice Epstein Library, FBI Vault, CourtListener, PACER, a government FOIA reading room, a legislative committee repository, or an authenticated archival copy.
Required Title Format
Use a title that tells readers exactly what the record is.
For an EFTA document:
EFTA########: [Specific Descriptive Title]
Example:
[Verified EFTA identifier]: [Specific description verified against the record]
For a court record:
[Case Name]: [Document Type], [Filing Date]
For other evidence:
[Date or Identifier]: [Specific Descriptive Title]
Do not use sensational titles such as “Bombshell,” “Smoking Gun,” “Exposed,” or “Proof of a Cover Up” unless an authoritative source establishes the claim and the wording remains accurate in context.
Copy and Paste Evidence Page Template
<h2>Snapshot</h2>
<div style="max-width:100%; overflow-x:auto;">
<table style="width:100%; table-layout:fixed; border-collapse:collapse; color:#19273f; overflow-wrap:anywhere; white-space:normal;">
<caption style="caption-side:top; text-align:left; padding:0 0 12px; color:#19273f;">Evidence snapshot: [Record identifier]</caption>
<thead>
<tr style="background-color:#1c3159; color:#ffffff;">
<th scope="col" style="width:34%; padding:12px; text-align:left; color:#ffffff; background-color:#1c3159; vertical-align:top; overflow-wrap:anywhere;">Field</th>
<th scope="col" style="width:66%; padding:12px; text-align:left; color:#ffffff; background-color:#1c3159; vertical-align:top; overflow-wrap:anywhere;">Details</th>
</tr>
</thead>
<tbody>
<tr style="background-color:#f2f5fb; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">Document</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">[EFTA number, Bates range, exhibit number, docket entry, FBI serial, filename, or other stable identifier]</td>
</tr>
<tr style="background-color:#e7edf7; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">Direct evidence link</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">[Link the exact Epstein Data record or primary source]</td>
</tr>
<tr style="background-color:#f2f5fb; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">Date created</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">[Month Day, Year, approximate date, or unknown]</td>
</tr>
<tr style="background-color:#e7edf7; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">Date sent or filed</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">[Month Day, Year, if different]</td>
</tr>
<tr style="background-color:#f2f5fb; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">Date released</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">[Month Day, Year, if known]</td>
</tr>
<tr style="background-color:#e7edf7; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">Author or creator</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">[Person, agency, company, court, or unknown]</td>
</tr>
<tr style="background-color:#f2f5fb; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">Sender</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">[Name and role, if applicable]</td>
</tr>
<tr style="background-color:#e7edf7; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">Recipient</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">[Name and role, if applicable]</td>
</tr>
<tr style="background-color:#f2f5fb; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">Custodian or producing source</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">[Agency, court, litigant, company, archive, or collection]</td>
</tr>
<tr style="background-color:#e7edf7; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">Evidence type</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">[Email, FBI report, court filing, financial record, flight record, photograph, audio, video, property record, corporate record, FOIA release, or other]</td>
</tr>
<tr style="background-color:#f2f5fb; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">Length and format</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">[Number of pages, file type, attachments, transcript, or native file information]</td>
</tr>
<tr style="background-color:#e7edf7; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">Case or investigation</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">[Case name, docket number, agency file number, or unknown]</td>
</tr>
<tr style="background-color:#f2f5fb; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">People named</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">[List only relevant, verified identities]</td>
</tr>
<tr style="background-color:#e7edf7; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">Organizations named</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">[Relevant companies, agencies, nonprofits, banks, schools, or other entities]</td>
</tr>
<tr style="background-color:#f2f5fb; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">Locations named</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#f2f5fb; overflow-wrap:anywhere;">[Relevant properties, cities, airports, institutions, or countries]</td>
</tr>
<tr style="background-color:#e7edf7; color:#19273f;">
<th scope="row" style="padding:12px; text-align:left; vertical-align:top; font-weight:600; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">Content warning</th>
<td style="padding:12px; vertical-align:top; color:#19273f; background-color:#e7edf7; overflow-wrap:anywhere;">[Include when the record references sexual abuse, trafficking, exploitation, medical information, suicide, violence, or explicit material]</td>
</tr>
</tbody>
</table>
</div>
<hr />
<h2>What Is This Record?</h2>
<p>[Identify the document in plain language. Explain who created it, when it was created, why it appears to have been created, and where it was found or released. State whether the record is complete, partial, redacted, duplicated, extracted, translated, transcribed, or missing attachments.]</p>
<p>[If the date is inferred from metadata, surrounding records, a postmark, a filing stamp, or another clue, say so. Do not present an inferred date as certain.]</p>
<hr />
<h2>Key Takeaways</h2>
<ul>
<li>[One or two careful sentences stating why the record matters without overstating what it proves]</li>
<li>[Summarize a second central documented point and cite the exact supporting source.]</li>
<li>[State the most important evidentiary limit, current outcome, or unresolved issue.]</li>
</ul>
<hr />
<h2>Source and Provenance</h2>
<p>[Describe the record’s custody and release history. Identify the agency, court, litigant, company, archive, or publisher that produced it. Include the EFTA dataset, Bates range, FBI serial, docket entry, exhibit number, FOIA number, original filename, or hash when available.]</p>
<p>[Explain any gap in the chain of custody. State whether the page is a scan, screenshot, transcription, duplicate, cropped image, derivative file, or archived copy.]</p>
<p><strong>Primary source:</strong> [Direct link]</p>
<p><strong>Epstein Data record:</strong> [Direct EFTA link]</p>
<p><strong>Official or court source:</strong> [Direct link when available]</p>
<p><strong>Archived copy:</strong> [Direct link when necessary]</p>
<hr />
<h2>What the Record Contains</h2>
<p>[Summarize the document in chronological or logical order. Identify the most important statements, transactions, dates, people, organizations, locations, attachments, and referenced records.]</p>
<p>[Separate the document creator’s statements from claims made by witnesses, tipsters, attorneys, investigators, analysts, journalists, or third parties. Preserve qualifying terms such as alleged, reported, possible, suspected, unverified, or estimated.]</p>
<hr />
<h2>Key Evidence Points</h2>
<ul>
<li>[Evidence point with page number, Bates number, timestamp, entry number, or other locator]</li>
<li>[Evidence point with locator]</li>
<li>[Evidence point with locator]</li>
<li>[Evidence point with locator]</li>
</ul>
<p>[Each point should state what the record shows without adding an unsupported conclusion.]</p>
<hr />
<h2>What the Record Does and Does Not Prove</h2>
<p><strong>What it establishes:</strong> [List the facts directly supported by the record.]</p>
<p><strong>What it does not establish:</strong> [Identify reasonable limits. A name, payment, flight entry, contact listing, photograph, scheduled meeting, or third party allegation does not automatically establish criminal conduct, knowledge, intent, attendance, or the nature of a relationship.]</p>
<p><strong>Unresolved questions:</strong> [List material questions the record raises but does not answer.]</p>
<hr />
<h2>People and Entities Appearing in the Record</h2>
<h3>[Verified Person or Entity Name]</h3>
<p>[Explain exactly how the name appears and why it is relevant. State whether the person is a sender, recipient, subject, witness, accuser, accused person, employee, attorney, passenger, payor, payee, attendee, copied recipient, or person merely mentioned by someone else.]</p>
<p>[Include a material denial, response, acquittal, dismissal, correction, or contrary record when relevant.]</p>
<p>[Repeat only for people and entities necessary to understand the evidence.]</p>
<hr />
<h2>Timeline Significance</h2>
<p>[Explain where the record fits in the broader chronology. Link related events, investigations, lawsuits, financial activity, travel, communications, arrests, prosecutions, institutional decisions, or survivor accounts.]</p>
<p>[Distinguish the date of the underlying event from the date the record was created, filed, received, or released.]</p>
<hr />
<h2>Related Evidence</h2>
<ul>
<li>[Related EFTA record with direct Epstein Data link and one sentence explaining the relationship]</li>
<li>[Related court filing, FBI serial, exhibit, email attachment, financial record, flight record, or photograph]</li>
<li>[Record that corroborates, contradicts, updates, or places this evidence in context]</li>
<li>[Parent document or attachment, when applicable]</li>
</ul>
<hr />
<h2>Reliability and Limitations</h2>
<p>[Assess the source, not whether the document supports a preferred theory. Note authenticity, provenance, legibility, redactions, missing pages, missing attachments, OCR errors, handwriting uncertainty, translation issues, duplicate records, date conflicts, or unresolved identity questions.]</p>
<p>[For an FBI interview or intake report, explain that the document records what a person told the FBI unless the report independently verifies the statement.]</p>
<p>[For a complaint, affidavit, or deposition, distinguish allegations and testimony from judicial findings.]</p>
<p>[For an email, distinguish the sender, recipients, copied recipients, quoted text, forwarded material, attachments, and people merely mentioned.]</p>
<p>[For a financial record, distinguish a documented transfer from any claim about purpose, knowledge, or criminality.]</p>
<p>[For a photograph or video, distinguish visible presence from assumptions about relationship, knowledge, or conduct.]</p>
<p>[For a calendar entry, distinguish a scheduled event from confirmed attendance.]</p>
<hr />
<h2>Survivor Safety and Privacy Review</h2>
<p>[State whether the public record contains survivor names, pseudonyms, identifying details, medical information, addresses, telephone numbers, email addresses, explicit descriptions, images, or information about minors.]</p>
<p>[Explain what was omitted, summarized, or redacted on EpsteinWiki. Never reproduce unnecessary survivor identifying information, explicit imagery, child sexual abuse material, private medical details, login credentials, financial account numbers, or personal contact information.]</p>
<hr />
<h2>Why This Record Matters</h2>
<p>[Explain the record’s evidentiary or historical value in clear language. Connect it to documented patterns, institutions, decisions, timelines, financial structures, travel, communications, prosecutions, or survivor accounts without turning inference into fact.]</p>
<hr />
<h2>Verification and Source Review</h2>
<p>[State which details were independently verified and how. Identify any disputed, uncertain, or unverified claims. Record relevant denials and later developments.]</p>
<p>[State whether the original file, complete docket, surrounding email thread, attachments, native spreadsheet, audio, video, or comparison copy was reviewed.]</p>
<p><strong>Source review status and scope:</strong> [Verified, partially verified, disputed, unverified, incomplete, or authenticity unresolved]</p>
<p><strong>Last checked:</strong> [Month Day, Year]</p>
<p>[Describe only verification actually completed, the review scope, and material unresolved gaps. Do not publish a writer checklist or a blanket assurance that every claim is verified.]</p>
<hr />
<h2>Related EpsteinWiki Pages</h2>
<ul>
<li>[Relevant person page]</li>
<li>[Relevant organization page]</li>
<li>[Relevant property, case, timeline, evidence category, or investigation page]</li>
</ul>
<hr />
<h2>Conclusion</h2>
<p>[Summarize why this evidence matters, what the reviewed record establishes, and the most important remaining limitation. Introduce no new claims or speculation.]</p>
<hr />
<h2>Questions and Answers</h2>
<h3>What does this record actually establish?</h3>
<p>[Summarize the narrow facts supported by the record and cite exact pages or timestamps.]</p>
<h3>Where did the record come from?</h3>
<p>[Summarize the verified provenance, release context, and direct source link.]</p>
<h3>What remains uncertain?</h3>
<p>[Explain material limits, disputed identities or claims, and missing context without adding speculation.]</p>
<hr />
<h2>Sources</h2>
<ul>
<li>[Direct Epstein Data record]</li>
<li>[Official government, court, or producing source]</li>
<li>[Related primary record]</li>
<li>[Credible secondary source used only for necessary context]</li>
</ul>
Author Checklist
These instructions are for contributors. They are outside the article example and must not be pasted into the published article.
- Research before drafting. Open the relevant primary records and use the official Epstein Library and Epstein Data to find and compare sources. Consult the owner’s current approved original sleuth reporting, including Soror FV (RSS feed), and relevant international coverage. Follow reporting to its original evidence, credit the original researcher, and do not count recycled reports as independent corroboration. Describe only the records actually reviewed. Do not claim to have searched an entire corpus without a documented basis.
- Complete a human, claim-by-claim verification pass. Check identities, roles, dates, legal outcomes, amounts and currencies, record and docket identifiers, quotations, page numbers, and surrounding context against opened sources. Check document images or native files against OCR and AI output. Correct hallucinations, unsupported connections, omitted qualifiers, and misleading omissions. Preserve contrary evidence and place material responses beside the claims they answer.
- Protect survivors and preserve legal distinctions. Use chosen public names only when appropriate, protect minors and anonymous or pseudonymous survivors, and omit unnecessary identifying or graphic details. Separate a documentary mention from participation, an allegation from a finding, and a settlement from an admission. Obtain the required second human review for serious allegations, disputed identities, or sensitive survivor material.
- Attribute and write clearly. Cite primary records beside the claims they support and credit original reporting and images. Respect copyright and use only necessary, limited quotations. Write in plain American English at a high school reading level. Avoid dash punctuation in your own prose. Preserve exact punctuation in quotations, source titles, names, identifiers, and URLs. Remove tracking parameters only when they are not needed to locate the source. Remove bracketed writing prompts, AI instructions, writer notes, review logs, and SEO fields from the article body before publication.
- Check structure and sources. Keep the WordPress title separate. Begin the body with the Snapshot table, then an introduction and bullet Key Takeaways. Use actual H2 and H3 elements with one horizontal rule between major H2 sections. Retain the subject-specific evidence, chronology, safeguards, and limits. End with Conclusion, Questions and Answers, and Sources. Replace source placeholders with verified, clean direct links and exact locators; never guess an EFTA identifier or URL.
Images and Media
Use a verified, lawfully usable photograph of the actual person when a portrait is appropriate. If no suitable verified portrait is available, use a clearly documentary design without a portrait. Do not invent a likeness, event, scene, or evidence image. Prepare a 16:9 image at 1600 × 900 pixels, optimized to less than 2 MB. Use purple treatment for survivor pages without compromising dignity or implying unverified facts. Verify provenance, rights, identity, date, and context. Add an accurate caption and descriptive alt text that describe what is visible. Preserve existing approved media unless the assignment includes changing it.
SEO, Taxonomy, and Save Verification
Prepare the following separately from the article body, then enter the approved values in the native WordPress and Yoast fields. Do not append an SEO section to the public article.
- Meta description: [Write a clear description of approximately 140 to 155 characters using the EFTA number or record identifier and the central subject.]
- Focus keyphrase: [Use the EFTA number or a specific evidence phrase]
- Keywords and tags: [EFTA number, people, entities, location, evidence type, case, agency, and central subject]
- Use a concise, accurate SEO title and meta description, a specific focus keyphrase, a useful excerpt, and robust relevant existing categories and tags. Check the actual taxonomy and select terms for verified people, organizations, cases, locations, record types, dates, and identifiers where relevant. Avoid duplicates, keyword stuffing, and tags or descriptions that imply unsupported wrongdoing. Preserve accurate owner-edited metadata unless the assignment specifically calls for a change.
- Immediately before saving, read the current complete article again and reconcile any new owner edits. Preserve its title, slug and URL, publication status, media, taxonomy, and metadata except for changes within the authorized assignment. Do not publish a draft or change access merely because this template describes a publication workflow.
- After an authorized save, read the complete saved raw content and inspect the full public article, or the authorized preview for an unpublished page. Check for truncation, escaped or broken markup, remaining prompts, incorrect links, duplicate H1 or SEO text, and unintended changes to status, URL, media, or metadata. Verify the Snapshot at desktop and narrow mobile widths, including wrapping, color contrast, caption, and column and row headers.
Direct Epstein Data Linking Rules
Every EFTA Evidence page should place the direct receipt near the top of the article and repeat it in the Sources section.
Use:
https://epstein-data.com/EFTA######## is an illustrative URL pattern only. Open the actual record, verify its identifier and contents, and copy its exact URL. Never publish the placeholder or construct a link from a guessed number.
Do not link only to the Epstein Data homepage when a direct record exists. Do not link only to a search result, extracted text row, entity page, or automated report when the original EFTA record is available.
If an article discusses several EFTA records, link each identifier separately. The visible anchor should normally include the EFTA number and a short description.
Example:
Use descriptive link text containing the verified EFTA identifier and record description, and link it to the exact URL copied from the opened record.
When a record has a Bates range, identify the beginning and ending numbers in the Snapshot. If Epstein Data organizes the file under the beginning identifier, link that record and state the full range in text.
The Epstein Data interface contains extracted text and analytical tools. Those tools help researchers locate evidence, but the document image or original downloadable file remains the source to cite. Extracted text can contain OCR errors. Automated summaries and entity matches can contain interpretation errors. Verify quotations, names, dates, amounts, and page references against the record itself.
Provenance Requirements
Provenance explains where the evidence came from and how it reached the public archive. Every Evidence page should answer these questions when the information is available.
- Who created the record?
- Who received or maintained it?
- What agency, court, litigant, company, or archive produced it?
- When was it created, filed, acquired, or released?
- Does it carry an EFTA number, Bates stamp, exhibit number, docket number, FBI serial, FOIA number, or original filename?
- Is it a complete file, selected page, duplicate, attachment, transcription, screenshot, or derivative copy?
- Does metadata identify a parent document, custodian, source device, author, or hash?
- Are pages, attachments, native files, or surrounding records missing?
Do not invent missing provenance. Write “unknown,” “not stated in the released record,” or “not independently confirmed” when appropriate.
Follow the Chain of Custody Protocol for files received outside an established public repository.
Required Evidentiary Limits
An Evidence page must contain a clear “What the Record Does and Does Not Prove” section. This is required even when the evidence seems self explanatory.
A contact entry establishes that information appears in a contact collection. It does not automatically establish communication, friendship, knowledge, or misconduct.
A flight entry may establish that a person was listed for a particular flight leg. It does not automatically establish the purpose of travel, presence at every destination, or criminal conduct.
A photograph may establish visible presence at a moment and place. It does not automatically establish the nature or duration of a relationship.
An email establishes the content sent from one account to other listed accounts. It does not automatically establish that every recipient read, accepted, or acted on the message.
A calendar entry may establish that a meeting was scheduled. It does not automatically establish that the meeting occurred.
A financial record may establish that money moved between identified accounts. It does not automatically establish why the payment was made or what each person knew.
An FBI intake report establishes that information was reported to the FBI. It does not automatically establish that agents verified the allegation, interviewed the source, opened an investigation, or reached a factual finding.
A complaint records allegations. A charging document records charges. A deposition records sworn testimony. An order records a court ruling. A verdict or judgment records an adjudicated result. Use the precise procedural status.
Read Ethical Rules for Naming Public Figures before publishing any unadjudicated allegation involving an identifiable person.
Special Requirements by Evidence Type
Emails
Record the sender, recipients, copied recipients, date, time zone, subject, attachments, quoted material, and forwarded content. Do not describe a person mentioned in the text as a sender or participant. Link parent messages and attachments when available.
Financial records
Record the date, amount, currency, originating account or entity, recipient account or entity, bank, transaction reference, stated purpose, and source page. Mask account numbers and personal financial identifiers. Explain whether the record is a bank statement, wire instruction, internal review, suspicious activity report, invoice, ledger, or secondary summary.
Flight and travel records
Record the date, aircraft, tail number, origin, destination, flight leg, listed passengers, crew, and source page. Preserve uncertain handwriting and spelling. Do not merge separate legs or assume that everyone listed boarded.
Court records
Record the complete case name, court, docket number, filing date, document number, parties, document type, and current procedural status. Check for later orders, amendments, dismissals, settlements, appeals, or corrections.
FBI and law enforcement records
Record the agency, case number, serial, interview or intake date, report date, author when available, redactions, and whether the account was firsthand, hearsay, or investigator analysis. Do not treat the existence of a report as government verification of its contents.
Photographs and video
Record the source, date, location, visible people, original caption, edits, crop, duration, timestamps, and identification method. Separate what is visible from what a caption or witness claims. Do not use face matching alone to identify an uncertain person.
Audio and transcripts
Link the original audio when lawful and safe. State who produced the transcript, whether it was human reviewed, and where speech is unclear. Use timestamps for significant passages. Do not silently correct or complete uncertain speech.
Screenshots and archived web pages
Link the original page and an archived capture when available. Record the capture date. Explain what the screenshot omits. A screenshot without provenance should be treated as a lead until authenticated.
Survivor Safety Rules
Do not upload or reproduce child sexual abuse material. Do not reproduce explicit survivor imagery, private medical details, home addresses, personal telephone numbers, private email addresses, financial account numbers, passwords, or other information that creates unnecessary risk.
Do not identify a minor survivor. Do not reveal the identity of an anonymous or pseudonymous survivor through indirect details. Use a public name only when the survivor has clearly chosen public identification in a reliable source and including the name remains necessary and appropriate.
Use a content warning before descriptions involving sexual violence, trafficking, exploitation of minors, suicide, self harm, or graphic abuse. Describe only what readers need to understand the evidence.
Review Handling Sensitive Material, the Trauma Informed Writing Toolkit, and Editorial Standards before publishing survivor related evidence.
Evidence Page Review Checklist
Before publication, confirm every item below.
- The title identifies the exact record.
- The Snapshot includes a stable identifier and direct evidence link.
- The original file was reviewed in full.
- Dates distinguish the event, creation, filing, receipt, and release.
- The source and chain of custody are explained.
- Quotations, names, dates, amounts, and page references were checked against the record image or native file.
- The summary separates fact, allegation, testimony, analysis, inference, and judicial finding.
- The page states what the record does and does not prove.
- Relevant denials, corrections, dismissals, acquittals, and contrary evidence are included.
- Related EFTA records link directly to Epstein Data.
- Survivor identities and private information received a safety review.
- The page contains no unsupported implication of guilt by association.
- Headings, tags, captions, excerpts, and SEO text do not overstate the evidence.
- The Sources section contains primary records before secondary reporting.
- A second editor reviewed serious allegations, disputed identity, or sensitive evidence.
Use Fact Checking and Verification Resources for the final verification pass and Moderation and Flagging Protocols when a page requires correction or review.
Related EpsteinWiki Guides
- Getting Started With EpsteinWiki
- How to Read an Epstein Document
- Contributor Instructions
- Editorial Standards
- Chain of Custody Protocol
- Ethical Rules for Naming Public Figures
- External Investigation Databases Directory