July 3, 2026

QSP vs QSD Difference: California Roles Explained

In California, a QSD (Qualified SWPPP Developer) writes and amends the Stormwater Pollution Prevention Plan for a construction site, while a QSP (Qualified SWPPP Practitioner) implements that plan in the field — running inspections, sampling, and corrective actions. Both certifications are issued under the State Water Board's Construction General Permit; the QSD is the design/authorship role and the QSP is the field/implementation role, and one person can hold both.

A QSD (Qualified SWPPP Developer) authors and revises the Stormwater Pollution Prevention Plan for a construction site. A QSP (Qualified SWPPP Practitioner) implements it — inspections, sampling, corrective actions, and the field record. Both roles exist under California's current Construction General Permit — confirm the current order number and effective date at the SMARTS portal — and the same person can carry both certifications, which is why the distinction gets blurred on small jobs.

What does a QSD actually do?

The QSD role is authorship. A QSD develops the SWPPP before ground disturbance, selects the applicable risk level (the CGP uses a risk-level framework based on sediment risk and receiving water risk — confirm the current criteria in the permit), and specifies the BMPs the site will run. When conditions change — a phase transition, a new grading area, a failed BMP that needs redesign — the QSD amends the plan and signs the amendment.

The certification path runs through a State Water Board-approved training provider (CASQA administers a widely used program). A QSD credential requires an underlying professional license or certification — for example, a California PE, PG, CPESC, CPSWQ, or landscape architect registration — plus the required QSD training and exam; confirm the current qualifying credentials in the permit. That gatekeeping matters because the QSD is signing a technical design document, not just filling a form.

What does a QSP do differently?

The QSP owns the site while the plan is being executed. That means the routine inspections the permit requires — before, during, and after qualifying rain events, with the specific triggering thresholds and frequencies set in the current CGP; confirm those at the SMARTS portal — plus visual monitoring, sample collection when triggered, and logging corrective actions. The QSP is the person whose name is on the inspection report the Regional Water Board sees during an audit.

QSP certification has a lower floor than QSD: the training and exam, plus qualifying experience or an entry credential, but generally not the PE/PG requirement — confirm the current qualifications in the permit. A QSD is generally qualified to act as a QSP; the reverse is not true. At a small consulting firm, the practical pattern is often one or two people carrying QSD credentials and a wider bench doing QSP field work.

Why does the QSP/QSD split matter for liability?

Because it determines who owns the delivery obligation, and delivery is where firms get exposed.

The permit doesn't just require that inspections happen — it requires that records exist and get submitted through SMARTS (the State Water Board's Stormwater Multiple Application and Report Tracking System). Annual reports are due on the deadline set in the permit — confirm the current date and reporting period at the SMARTS portal. NALs and NELs (Numeric Action Levels and Numeric Effluent Limitations) trigger reporting timelines set by the permit — confirm the current deadlines in the CGP. When something is late or missing, the question during enforcement isn't "did the consultant do the work" — it's "can you prove the record left your hands and reached the right party on the right date."

That is a delivery problem, and it lands differently depending on role. A QSD who signs a SWPPP amendment and emails it to the general contractor has, until it's confirmed received, a signed document and no proof it was acted on. A QSP who runs a post-storm inspection and drops the report into a shared folder has a file, not a record of transmittal. When a discharger gets a Notice of Violation, the consulting firm's defense is the paper trail — and email threads are not a paper trail an auditor treats as authoritative.

This is the specific gap Mainstay closes: it produces a tamper-proof record of every send — which report, to which party, on which date — so that when a QSP's inspection or a QSD's amendment goes out, the transmittal itself is provable, not reconstructed from an inbox six months later.

Can one person be both QSP and QSD?

Yes. A single certified individual can develop the SWPPP as QSD and implement it as QSP on the same project, and on small sites that's common. But combining the roles doesn't merge the obligations — the authorship record and the field-implementation record are still distinct, and both have to be delivered and documented separately. The firm carries both liabilities regardless of whether one badge or two is doing the work.

How does this affect billing on a small firm?

Directly. QSD work is usually scoped and billed as a deliverable — the plan, the amendment. QSP work is recurring: per-inspection, per-storm-event, monthly monitoring. Recurring field work is where invoicing drifts, because the trigger for billing is the delivered report, and if the report's delivery isn't recorded cleanly, the invoice sits. Tying the billing event to a confirmed delivery — the QSP report actually landing with the client — is what keeps stormwater monitoring from becoming the line item that ages on a small firm's receivables.

Mainstay coordinates the delivery and documentation of environmental compliance work — it is not a compliance advisor and makes no regulatory determination. Always confirm requirements with the relevant agency.

Sources

This post is for general informational purposes only. Mainstay coordinates the delivery and documentation of environmental compliance work — it is not a compliance advisor and makes no regulatory determination. Regulatory requirements vary by permit type, jurisdiction, and project conditions. Always confirm applicable requirements with the relevant agency or a qualified professional.