Package discovery and pairing
Discover package components and deterministically pair DAT and OPT files.
Production Package Doctor
Production Package Doctor is a local, read-only Windows preflight tool that checks eDiscovery production packages before upload or workspace import.
No case data shown / Diagnostic material only
Main dashboard showing offline access, Pilot time, and package usage before any real package is audited.
- 01
Windows local processing
Selected package contents are processed on the operator’s Windows computer.
- 02
Read-only source package
The selected source package is read, not repaired or rewritten.
- 03
HTML and JSON reports
Completed audits can produce human-readable HTML and machine-readable JSON reports.
- 04
Limited authorization traffic
Only limited authorization, device-lifecycle, and opaque Pilot-accounting traffic may use the network.
Before workspace import
The package should be understood before the platform becomes the test.
- 01
Manual preflight checks are repetitive and can vary between reviewers.
- 02
DAT, OPT, and referenced files need to be checked together, not as isolated artifacts.
- 03
Structural problems are often discovered only when a downstream import is attempted.
- 04
One-off scripts rarely provide a consistent review trail or a shared report format.
Implemented V1 scope
What V1 checks
The capability and its boundary belong in the same view. The report remains the authority for the rules applied to a particular audit.
DAT and OPT structure
Review DAT header mapping, OPT structure, and selected relationships between them.
Audit-window source integrity
Record source-integrity evidence during the audit window and apply the rules listed in the report.
V1 does not validate every production format, family relationship, privilege log, or downstream-platform rule.
A reviewable workflow
From selected package to evidence.
Core text and reports remain accessible without relying on animation or client-side application state.
- 01
Select a production package
Choose the source package that should be reviewed.
- 02
Choose an audit mode
Use Strict or Best-Effort mode according to the uncertainty the operator needs to preserve and review.
- 03
Run a local, read-only audit
Process selected package contents locally without repairing or rewriting the source package.
- 04
Review the result and reports
Review the operational result together with the generated HTML and JSON evidence.
A focused first step
One workflow question is enough to start.
No files or case materials needed. Use 15 minutes to check whether PPD fits the review problem in front of you.
Authentic product evidence
The interface, result, and report stay connected.
These images come from the current bundled Demo and protected Pilot interface. Credentials, identifiers, and real case content are not shown.
Demo PASS Result
Bundled Demo result showing a clean pass with no findings within the implemented V1 rules.
Generated HTML Report
An authentic bundled Demo HTML report showing the clean-pass outcome, observed production components, source-integrity evidence, and implemented V1 limitations.
Demo NEEDS_REVIEW Result
Bundled Demo result for expected-natives-missing, flagging a structural question that requires operator confirmation.
Operational outcomes
Three results. Each still needs context.
These statuses describe authenticated synthetic samples under the implemented V1 rules. They are not legal judgments, compliance certifications, or customer case studies.
01
PASS
No finding was raised within the implemented V1 rules for the authenticated synthetic sample.
02
NEEDS_REVIEW
The sample contains a structural question that requires operator confirmation.
03
FAILED
The sample contains a blocking structural problem that should be resolved before relying on the package.
Local case-content boundary
Local processing is specific, not absolute.
Case-package content and reports stay local. Limited authorization and device-lifecycle traffic is described separately rather than hidden behind an “offline” label.
Read Privacy & SecurityCase contents stay local
DAT, OPT, image, text, native, report, and derived case content are not uploaded by the desktop application.
Network use is narrowly separated
Authorization, lease refresh, device lifecycle, and opaque Pilot accounting may exchange limited data.
Reports go where the operator chooses
Reports are written to a separate operator-selected location.
Limits are part of the product
Automation supports review. It does not replace it.
Professional review remains required
Automated findings support professional review and do not replace professional judgment.
No legal or platform guarantee
The tool does not provide legal advice, certify compliance, or guarantee downstream import.
V1 has an explicit scope
V1 does not validate every production format, relationship, or downstream-platform rule.
Invited Pilot
Start with the workflow, not an installer.
Invited access
Pilot access is offered individually after a workflow-fit discussion; it is not public or self-service.
30 days or five recognized packages
The Pilot allows up to five recognized real production packages during 30 calendar days beginning after the first successful real-package audit.
Separate offline refresh window
Seven-day offline access is a cached authorization refresh window, not the Pilot duration.
- 01
Request a focused Demo
Tell us your role, whether you work with DAT and OPT packages, and the workflow you want to discuss.
- 02
Review the public evidence
Use the screenshots, authenticated synthetic samples, and public reports before sharing any sensitive context.
- 03
Confirm workflow fit
Use a 15-minute conversation to determine whether the current V1 scope matches a real review need.
- 04
Receive an invitation separately
Suitable users may receive individual Pilot access. A Demo request does not automatically grant software access.
Production Package Doctor
Review the evidence, then discuss workflow fit.
No case materials, license keys, or confidential package content are needed to request a Demo.
Invited Pilot access is offered separately; a Demo request does not automatically grant software access.