ByteCase by Forensics ByteExplore Tools

Digital Forensics Request Builder

v0.9.0 · Pre-release Ready First signed release cycle

ByteCase Intake

Build complete, consistent digital forensics requests before evidence reaches the lab.

Explore the module View on GitHub View roadmap →

Start with a request the lab can act on

ByteCase Intake creates a better starting record for examiner review without attempting to replace that review.

Current release status

ByteCase Intake v0.9.0 is prepared for its first pre-release cycle.

Signed Windows publication is pending Azure Artifact Signing certificate verification.

Explore the interface

See how the module structures the work.

Select a workspace to view the interface and understand how it supports the surrounding forensic workflow.

1 of 5

Start the Request

Capture the case number, incident type, submitting agency, investigator, contact information, and supervisor details.

Capabilities

Built around the work.

Guided request building

Collect case identifiers, requester details, authority, devices, requested examinations, urgency, and delivery requirements.

Submitted-item documentation

Record devices, peripherals, attachments, physical item photographs, and handoff details.

Review before export

Check required information and resolve validation warnings before generating the request package.

Portable case records

Generate TXT, DOCX, and JSON material inside the shared ByteCase case-folder structure.

Who this is for

Designed for practical forensic environments.

Solo examiners receiving informal requestsSmall laboratories without a dedicated request platformInvestigators preparing evidence for submissionTechnical reviewers checking scope and handoff information

When to use it

Good fits for the module.

  • Capture case, requester, authority, scope, and urgency
  • Inventory devices, submitted items, peripherals, attachments, and photographs
  • Review request completeness before examiner handoff
  • Preserve the original request with the case

What it does not replace

Keep the boundary clear.

  • Legal review of authority or scope
  • Agency approval and prioritization procedures
  • Evidence intake or custody systems
  • Examiner judgment about technical feasibility

Example workflow

From case input to saved record.

  1. 01

    Identify the request

    Record the case number, requester, contact, and deadlines.

  2. 02

    Define authority and scope

    Document the authority presented and requested examination areas.

  3. 03

    Describe submitted items

    Capture devices, peripherals, condition, access information, attachments, and photographs.

  4. 04

    Review and generate

    Resolve missing information and create the saved request package.

Detailed boundaries

What this module does not claim.

  • ByteCase Intake does not determine whether legal authority is sufficient.
  • Agency approval, evidence-intake, and prioritization procedures remain outside the application.
  • The v0.9.0 build is not yet presented as a signed public Windows release.

Development direction

Where the module can go next.

  • Publish the first signed Windows pre-release
  • Collect requester and examiner feedback
  • Refine configurable agency fields
  • Prepare future Hub interoperability

Product status

v0.9.0 · Pre-release Ready

v0.9.0 prepared for the first signed pre-release cycle.

Current focusSigned publication, structured external testing, and refinement from examiner feedback.View development history →

ByteCase by Forensics Byte

Documentation that remains useful when the case returns.

Use focused standalone modules for specific workflow problems, then connect them only where shared data adds clear value.

Explore all toolsShare feedback →