Versioned EDF control
The output records the EDF profile and valid-value profile used for every cycle.
California EDF preflight and correction
Preflight GeoTracker EDF data with authority-bound relational package generation
Saxum reproduces the technical issue, checks cross-table integrity and returns a controlled findings packet. No value is silently changed merely to make a checker pass.
No portal credentials. No guaranteed external result. Scope confirmed before sensitive material is transferred.
Flagship product depth
GeoTracker submission depth
Deeper deterministic controls reduce setup and recurring review work while preserving customer-controlled submission and qualification boundaries.
LIMS adaptation
Laboratory exports can be mapped into EDFSAMP, EDFTEST and EDFRES roles without hiding unsupported fields.
Rejection-to-resubmission loop
External rejection rows are matched into a blocking worklist and corrected packages remain fail closed until relational controls pass.
Review how Saxum separates internal execution from external proof →
Qualification: external proof pending. This executable engine is internally verified. Live source credentials, provider acceptance, recovery evidence, measured intervention, false-positive results and renewal proof are still required before production qualification.
Fail-closed reviewUnsupported facts remain unresolved.
Transparent changesCorrections receive a visible audit trail.
Least-data intakeOnly necessary information is requested.
Independent serviceNo agency or platform affiliation implied.
Reviewed 12 August 2026
Current system boundary
GeoTracker electronic deliverables are governed by current California Water Board requirements and case context. Saxum validates the supplied EDF population and records the rule set used; the responsible party or authorized consultant controls the official submission.
The operational problem
Why the standard portal or checklist is not enough
EDF preparation combines relational identifiers, analytical results, qualifiers and project context. A desktop checker or portal error can reveal a problem late, but the team still has to trace the source and avoid corrupting valid laboratory data.
Truth boundary: Saxum controls preparation, evidence and technical review. It does not replace the customer’s legal, tax, accounting, scientific or regulatory professionals, and it does not control external acceptance.
Best-fit customer
Environmental consulting firms, laboratories and responsible parties submitting analytical data
Problems this product helps control
California GeoTracker Electronic Deliverable Format packages with structural, relational, controlled-value or source-population problems that should fail before portal submission.
What Saxum needs
A bounded intake, not an open-ended data dump
The case starts with enough context to reproduce the problem and define responsibility. Credentials, unrelated personal data and unsupported assumptions are excluded.
- EDF deliverable and available checker output
- Project and laboratory identifiers
- Applicable format version
- Source export or laboratory evidence for disputed fields
The deliverable
What arrives at the end of the engagement
The output is designed to be reviewed, handed off and defended—not merely marked “passed.”
- Structural and relational validation report
- Cross-file identifier checks
- Rejected-record worklist
- Deterministic correction candidate
- Before/after audit log
- Submission handoff checklist
Controlled workflow
From messy source material to a reviewable release packet
Each stage has a clear stop condition. When evidence is insufficient, the case pauses rather than manufacturing certainty.
Inventory
Identify the file set, version and project context.
Validate
Check structure, relationships, controlled values and record counts.
Investigate
Trace failures to the source rather than patching symptoms.
Package
Return a rechecked deliverable and evidence report.
Consulting-firm portfolio mode
Control EDF packages across laboratories and responsible-party clients
Keep facilities and clients segregated while reusing approved LIMS mappings, EDF controls and rejection-to-resubmission evidence.
Segregated accounts
Each customer, entity or operating unit keeps separate source evidence, mappings, exceptions and outputs.
Reusable controls
Approved mappings and review policy reduce repeat setup without allowing one client's assumptions to leak into another.
Portfolio oversight
Firm teams can see recurring due work, unresolved exceptions and evidence-backed outcomes without flattening client boundaries.
First-cycle outcome proof
Show the buyer exactly what Saxum proved
The first controlled cycle produces customer-visible proof before the workflow is expanded. Saxum keeps internal completion separate from external/provider acceptance and never turns estimates into verified outcomes.
Source coverage
See which files, mappings and authority sources were used, what was missing and which assumptions remained unresolved.
Exception register
Every blocker has a reason, owner and current state. Unsupported facts remain open instead of disappearing into a generic pass.
Evidence-graded scorecard
Separate Saxum-completed work from provider-final evidence, verified value, source-backed exposure, observed time savings and estimates.
Commercial fit
Use this when the cost of an unresolved exception exceeds the cost of review
Saxum is strongest when the workflow repeats, the evidence is fragmented and one preventable mistake can delay revenue, create rework or weaken the customer’s audit trail.
Indicative pricing
$199/month per laboratory · firm portfolio plans by quote
Every engagement starts with scope confirmation. Pilot and research offers are intentionally limited until the workflow is proven on paid cases.
Request an EDF preflight →Questions buyers ask
GeoTracker EDF Control FAQ
Direct answers on access, responsibility, deliverables and limits.
No. Official guidance and submission systems remain authoritative.
Not without documented source evidence and customer authorization.
Yes. Early checks are useful for exposing identifier and mapping problems.
No. Saxum reduces preventable technical failures and documents remaining exceptions.
Yes. Reusable mappings and controls can be established after a successful pilot.
Primary references
Verify the underlying requirement
Saxum product pages link to primary agency or platform material so buyers can confirm the official requirement themselves.
Primary-source review date: 12 August 2026. Re-check before each engagement.
Related Saxum desks
Continue the control layer
Bring the real case, not a hypothetical
Describe the workflow, deadline and evidence you already have. Do not send passwords, API keys or regulated data through the public form.
Evaluate before onboarding
See the workflow before you bring customer data
Every executable Saxum product now has a synthetic first-cycle walkthrough. Where a free checker or guide exists, it is linked here too.