Digital Forensics Intake Kit

An agency-adaptable request form, requester guide, and implementation guide with print, fillable, and editable paths for handing examiners the authority, scope, evidence details, and investigative question needed to begin well.

Version 1.2 · Updated August 5, 2026

Preview of Digital Forensics Intake Kit
For

Digital forensic units receiving requests from officers or investigators

When

When an officer or investigator knows what they need answered, but the request still has to survive the handoff into a forensic unit.

Why it exists

Reduce avoidable clarification and create a more reliable handoff from investigative need to forensic examination

Form

Print PDF + fillable PDF + editable sources + guides

Choose the working style

One intake structure. Three ways to use it.

The release does not assume every department, requestor, or examiner wants the same interaction. Start with the version that fits the actual handoff.

Fill on screen

Local fillable PDF

Type into 105 fields, save the file locally, and print or route it through an approved agency process. The PDF contains no JavaScript, telemetry, or automatic submission.

Write by hand

Print-ready PDF

Use the same two-page structure in a paper-first intake, signature, or in-person handoff process without forcing the requester into another screen.

Make it local

Editable agency source

Change branding, routing, approval fields, terminology, services, and local instructions before the form becomes an official part of an agency workflow.

Local by design. The fillable PDF saves entered values inside the file. It contains no form submission action, telemetry, or connection back to Forge & Verse.

Inside the release

Use the whole kit, or take only what fits.

The same intake structure now supports three real working preferences: type locally in a fillable PDF, print and write by hand, or adapt the editable source for an agency workflow. The guides support the handoff around the form.

Fillable PDF132 KB

Intake Request Form

Local-only two-page form with 105 text and checkbox fields. Saves entered data in the PDF and does not transmit it.

Download Fillable PDF
Print PDF90 KB

Intake Request Form

Print-ready two-page form for authority, scope, objectives, submitted evidence, targets, handling, and unit acceptance.

Download Print PDF
Editable DOCX41 KB

Intake Request Form

Agency-adaptable source file for branding, routing, approvals, evidence-system fields, and local terminology.

Download Editable DOCX
JSON17 KB

Form Field Map

Machine-readable list of all 105 field names, labels, types, and page locations for form review or workflow mapping.

Download JSON
PDF54 KB

Before You Submit a Digital Forensics Request

One-page handout that teaches officers and investigators to provide an objective, authority, scope, targets, context, and device condition.

Download PDF
Editable DOCX40 KB

Requester Guide

Editable handout for local terminology and approved handling instructions.

Download Editable DOCX
PDF95 KB

Intake Kit Implementation Guide

Four-page guide for adaptation decisions, pilot rollout, field rationale, version control, and records discipline.

Download PDF
Editable DOCX43 KB

Implementation Guide

Editable source for agency-specific training notes and implementation planning.

Download Editable DOCX

The request form

See the structure before you deploy it.

The preview shows the actual two-page form, not a decorative mockup.

First page of the Digital Forensics Intake Request showing requester, case, authority, objectives, and evidence fieldsOpen preview
Page 1 · Request, authority, objectives, and submitted evidence
Second page of the Digital Forensics Intake Request showing targets, credentials, preservation history, and forensic unit acceptance fieldsOpen preview
Page 2 · Targets, access, preservation history, and unit acceptance

Built around the handoff

The form is not the whole workflow.

The requester guide helps officers prepare a useful submission. The implementation guide helps a forensic unit adapt and maintain the release.

Preview of the one-page Before You Submit a Digital Forensics Request guideOpen preview
Requester GuideA one-page handout for officers and investigators before the device reaches the forensic unit.
Preview of the Digital Forensics Intake Kit implementation guideOpen preview
Implementation GuideA four-page guide for adapting, piloting, publishing, and maintaining the workflow.

Use it when

  • An officer or investigator is submitting a device or digital-evidence request
  • The examiner needs the investigative question, not merely a requested tool action
  • Authority, scope, date range, or access information could otherwise arrive through separate messages

What it captures

  • Requestor, case, and contact information
  • Legal authority, scope, and express limitations
  • Devices, evidence identifiers, and handling history
  • Investigative objectives, targeted data, and relevant date ranges
  • Known credentials, accounts, applications, and time-sensitive concerns

Before you deploy it

  • Add agency branding, routing instructions, and approval fields
  • Align legal-authority choices with local policy and law
  • Remove services your unit does not provide and add those it does
  • Review retention, signature, accessibility, and records requirements before operational use

From download to workflow

Adapt it before it becomes official.

The files are ready to review, not ready to bypass local judgment.

  1. 01

    Review

    Compare the files with local law, policy, services, records obligations, evidence procedures, and prosecutor expectations.

  2. 02

    Adapt

    Change the editable files to match the unit's authority choices, routing, identifiers, approvals, and approved credential method.

  3. 03

    Pilot

    Run realistic requests through the complete handoff and note missing information, unclear fields, and workarounds.

  4. 04

    Publish

    Place one approved version in a controlled location, remove superseded copies, and name the owner of future revisions.

A weak intake creates avoidable back-and-forth. An examiner receives a device, but not the question the examination is meant to answer. The legal authority may be somewhere else. The requested date range is unclear. A known passcode exists, but nobody knows who has it.

The intake form gives the requesting officer or investigator one place to describe the examination in terms an examiner can act on. It emphasizes investigative objectives because “extract the phone” is an action, not a question.

The rest of the kit supports the handoff around the form. The requester guide explains what a useful submission looks like before the device reaches the unit. The implementation guide helps an agency decide what to customize, how to pilot the workflow, where completed requests become records, and how to prevent old copies from lingering after the process changes.

The print PDF is ready for a paper-first handoff. The fillable PDF supports local typing and saving without sending data anywhere. The DOCX files are intentionally editable so a department can add its own routing instructions, approvals, evidence-system fields, legal language, services, and branding. Test the fillable edition in the agency-approved PDF viewer before operational use because save, print, and signature behavior can differ between viewers.

This is a starting framework, not a universal policy or legal form. Review it against local law, agency policy, prosecutor expectations, retention requirements, accessibility obligations, evidence procedures, and the actual services your forensic unit provides before operational use.

Use permission

You may use, modify, reproduce, and distribute an adapted version within your organization for operational, administrative, or training purposes. Attribution is appreciated but not required after adaptation. Do not resell the kit as a standalone item or present an altered version as an official Forge & Verse release.

Follow the thread

The idea continues elsewhere.

A useful object, a practice note, and a developing study can approach the same working moment from different directions.

Release history

What changed, and why.

Version 1.2August 5, 2026

Added a local-only fillable PDF with 105 fields, a machine-readable field map, and a public JSON release manifest. The print-ready PDF and editable DOCX remain separate choices rather than forcing one workflow.

Version 1.1August 4, 2026

Expanded the original form into a complete kit with a one-page requester guide, four-page implementation guide, editable source files, bundled release, and component checksums.

Version 1.0August 4, 2026

Initial two-page intake request released as print-ready PDF and editable DOCX.

Verify the download

The hashes are part of the release.

Compare the SHA-256 value after download when file integrity matters in your workflow.

Download checksum manifest Download release manifest JSON
Complete kit · SHA-256forge-and-verse-digital-forensics-intake-kit-v1.2.zip
91ef34615c97a432bdb2c93d40bcc498da006f4ba12aea1ea0d3f72e7bae089c
Fillable intake PDF · SHA-256intake-kit/digital-forensics-intake-request-fillable.pdf
10c361e4c03a19b6c83f9e33caa1a1299c50e27c484a37600f6a197bc359dbe3
Print intake PDF · SHA-256intake-kit/digital-forensics-intake-request.pdf
0da8ca48173e9279bc69d7e30ecfd62d32d1d52de0d31630bb6447a624245cc2
Editable intake DOCX · SHA-256intake-kit/digital-forensics-intake-request.docx
062f2a56ea3b4d5f2bbcfd9baacd580641e582160fe9fe24f184a155fa694ac9
Field map JSON · SHA-256intake-kit/digital-forensics-intake-request-field-map.json
937e529dd5b51c5a3e132f1c0d73f63e635656d3cbe51c3f3bc0e0edb3957ffe
Requester guide PDF · SHA-256intake-kit/digital-forensics-intake-requester-guide.pdf
3f435c5af70e1822b80de0a59aa3d9460c0157e1dc603d6691c690378835de11
Implementation guide PDF · SHA-256intake-kit/digital-forensics-intake-implementation-guide.pdf
579e1c1f0d2f48ad676e47671379b67b6ac85f88a4e3fc9aaf11b03a6d3cd200