Monthly discharge-reporting quality control

Close each required DMR reporting period before preventable errors reach NetDMR

Saxum organizes each reporting period’s sample and laboratory records into a permit-mapped control packet, surfaces potential exceedances and inconsistencies, and prepares a reviewed draft for the authorized signatory.

No portal credentials. No guaranteed external result. Scope confirmed before sensitive material is transferred.

FAMILYRegulated Operations
SOURCE REVIEW19 AUG 2026
AUTHORITYCUSTOMER-HELD
RULE CHANGESView change log →
Flagship product depth

DMR permit-cycle depth

Deeper deterministic controls reduce setup and recurring review work while preserving customer-controlled submission and qualification boundaries.

Expected-sample control

Permit expectations are compared with the received laboratory population before a reporting draft is prepared.

Deterministic unit conversion

Only explicitly supported unit conversions are performed; unknown conversions remain exceptions.

Monitoring calendar and anomaly evidence

The cycle carries expected monitoring rows, prior-period anomalies and unresolved evidence into one review packet.

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 19 August 2026

Permit-specific reporting rule

DMR reporting frequency, monitoring parameters and due dates are permit-specific. Saxum maps every cycle to the controlling permit and permitting-authority instructions rather than assuming that every facility reports monthly. The authorized signatory retains certification and submission responsibility.

The operational problem

Why the standard portal or checklist is not enough

NetDMR is the submission surface. The upstream work still includes permit-limit mapping, result qualification, averaging rules, unit consistency, no-discharge logic, exception review and evidence retention. A wrong value can become part of the official record.

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 consultants and laboratories managing recurring DMR work, plus small permittees

Problems this product helps control

NPDES discharge monitoring report cycles where permit parameters, limits, periods, NODI codes or source measurements need review before NetDMR 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.

  • Current permit and monitoring requirements
  • Laboratory results and field logs
  • Prior accepted DMR or reporting map
  • Declared no-discharge and operational events
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.”

  • Permit-to-parameter reporting map
  • Unit, date and qualifier checks
  • Calculation and averaging workpaper
  • Potential exceedance and missing-data queue
  • NetDMR entry draft or controlled handoff
  • Signed monthly evidence packet
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.

Map

Translate the permit’s monitoring requirements into a controlled reporting matrix.

Reconcile

Bind each reportable value to laboratory or field evidence.

Calculate

Apply customer-approved calculation rules and surface uncertainty.

Release

Deliver the reviewed draft for the permittee’s authorized signatory.

Environmental-consultant portfolio mode

Close recurring DMR cycles across permittee clients

Keep permits and facilities segregated while reusing approved laboratory mappings, permit rules, expected-sample controls and exception policy.

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.

See how outcome proof is graded →

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
$499 onboarding · from $399/location/month · consultant portfolio plans by quote

After the permit map is approved, each reporting cycle can run from scheduled laboratory exports; the permittee’s authorized signatory retains certification and submission.

Start a DMR first-cycle assessment →
Questions buyers ask

DMR Control FAQ

Direct answers on access, responsibility, deliverables and limits.

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: 19 August 2026. Re-check before each engagement.

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.

Start a DMR first-cycle assessment →
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.