This guide covers how to verify a California SMARTS filing before committing, including checking the live record for the current step count and the applicable NOI deadline.
It focuses on verify-before-you-commit checks: confirm the live record, the exact option, and the stated basis for any fee or deadline before submitting.
How It Works
California's Stormwater Multiple Application and Report Tracking System, commonly called SMARTS, is the state's online record system for stormwater permit applications and reports. Its mechanism is administrative tracking: it stores the site record, links it to a permit program, and shows submission status, but the portal record should be read alongside the permit document rather than treated as the permit itself.
The working sequence is record-based. An account is associated with a facility or project, the facility is associated with a permit program, and each submission creates a tracked item with a status. Before committing, verify that the live record shows the exact facility name, address, receiving water, and permit category you intend to use, because a mismatch can cause a later report, modification, or termination to attach to the wrong site.
| Term | Plain-language meaning | What to verify |
|---|---|---|
| NOI | Notice of Intent to be covered by a general permit | That the site and permit category match the live record |
| NOT | Notice of Termination when coverage ends | That termination is submitted only after the site conditions in the permit are met |
| SWPPP | Stormwater Pollution Prevention Plan | That the plan version matches the site and submission date |
| Tracking number | Identifier assigned to the record | That it appears on every related submission and report |
| Annual report | Recurring compliance submission | That the reporting period and site data are current |
Key terms should be treated as status labels, not approvals. An NOI starts coverage, an NOT ends it, a SWPPP documents site controls, and an annual report updates the record; none of those labels by itself proves that the site conditions, sampling, or inspections are complete. The practical check is to match each term to the underlying permit requirement and site file before submission.
The 14-day NOI deadline, where it applies, is a planning checkpoint rather than a reason to rush an incomplete record. Count backward from the first day of regulated activity, reserve time for SWPPP review, site maps, and internal approvals, and confirm the current deadline in the live permit and portal instructions before relying on it. If the portal, permit, and site file disagree, resolve that discrepancy before submitting, because the tracked record becomes part of the compliance history.
CASQA, which advances sustainable stormwater management and represents over 26 million Californians, is one source of practitioner context; even so, portal rules, deadlines, and submission requirements should be verified against the live state system before commitment.
Key Factors to Consider
Before committing to any option in California's Stormwater Multiple Applications and Report Tracking System, the first decision criterion to lock in is scope of coverage. Do not assume one filing matches every site. Check the exact site boundary you are about to enter against the live record for that site, and confirm it is the boundary tied to the option you intend to select. A change in boundary is not a wording edit, it can change what must be tracked, so treat this as a line by line check with no assumptions.
The second criterion is cost exposure. According to Let's Talk Windsor, a stormwater fee can be based on each property’s water runoff contribution as a result of its total impervious area, and it states the estimated replacement cost value of the existing stormwater system is approximately $2 billion. In addition, San Bernardino County (.gov) reports an updated analysis showing proposed stormwater mandates will cost San Bernardino County and cities $11 billion. These are not stated as universal SMARTS filing fees, but they show impervious area can be tied to very large dollar figures in California stormwater contexts. For your exact option, pull the live fee line, confirm the stated basis for it, and compare like-for-like totals with every listed add-on before committing.
The third criterion is capture value. As noted by CalMatters, water officials and experts agree that capturing more stormwater before it flows into drains is a top priority to help boost California’s water supply. NRDC also points to efficiency, reuse, and stormwater as part of California’s water supply potential. With that in mind, if any option claims a supply benefit, do not accept it at face value. Ask for the stated basis for that claim on the live option, and weigh it against the verified total cost for that same option.
As for the numbers that matter, verify three things at the moment of review: the live total for the exact option, the live basis used to reach any fee (such as impervious area), and the live deadline window shown for that option. With multi-billion figures present in other stormwater contexts, a single unchecked line can carry weight. The top decision criteria remain scope, cost exposure, and capture value, each requiring its own live check.
Common Mistakes
The first pitfall is assuming continuity between filings. A concrete example is a site that had an existing record from a prior action, but after a change to the physical layout, the person preparing the next action copies the exact site description from an old draft instead of checking the live record. The safeguard is to treat the live record shown at the moment of action as the source of truth, not a saved draft. If the description in the live record does not match the layout you intend to act on, that is a mismatch to correct before committing.
That same pitfall can extend to the site boundary. Even if the description appears similar, the boundary shown in the live record is what is tied to that record. The check is to compare the boundary visible in the live record to the boundary you intend to act on for this specific action. This is not about assuming one filing fits all, but about verifying the exact boundary for the action you are about to commit.
The second pitfall is treating attachments as interchangeable. A concrete example is uploading a document that was prepared for a different site context, assuming it is acceptable for the live record you are about to commit. Since California's Stormwater Quality Association, CASQA, describes the system as an administrative tracking record, the attachment becomes part of that record once committed. Because of that, the check is to verify the attachment against the live record fields for this action, not against a folder of documents from a previous site.
To apply both checks together, use a like-for-like comparison at the moment of action. Look only at the live record fields you are changing, and confirm each one against what you intend. Do not rely on memory of a previous screen. This verify-before-you-commit approach is the practical safeguard, because once committed, the live record reflects that action as it stands.
Insider Tactics
The strategies below are non-obvious timing and verification tactics for working through California's Stormwater Multiple Applications and Report Tracking System. The purpose is not to move faster, but to build a traceable path of checks before committing to any live option. Use them at the moment of action, not as a substitute for the live record itself.
One non-obvious strategy is to treat the record view as a comparison tool against your own site materials, rather than assuming it matches them. Before selecting any action, pull the visible site elements for the exact boundary you intend to file for and compare them directly to a saved copy of your internal site map. If there is any mismatch between the two, do not try to reconcile it by choosing the option that seems closest. Instead, log that specific mismatch as an open question and only proceed once the live record answers it. This forces a like-for-like comparison between what you know and what the system is showing, without relying on memory.
For timing, the most useful tip is to create a personal review window that is independent of any stated deadline. Since program rules can be presented differently over time, verify the current deadline text directly on the live page at the moment you plan to act, not from an old screenshot or a saved note. At the same time, confirm the exact action you intend to take is still selectable at that moment. Availability can shift, so treating "still selectable" as its own check is just as important as reading the text itself.
Finally, keep a minimal decision log for each candidate action you seriously consider. For each one, record the question you needed answered, the exact place you checked it live, and the answer you received. This log does not need to be lengthy, but it creates accountability for your choices. As noted by the California Stormwater Quality Association, CASQA, the field relies on informed practitioners to stay current with evolving stormwater management approaches, and that same discipline applies to verifying your own filing path before committing to it.
Comparison
This section alone compares options side by side with a winner. When weighing two paths inside California's Stormwater Multiple Applications and Report Tracking System, the comparison must be like-for-like by elements, not by name. The first check is simple: take every element tied to your site and see if it appears on the live record for each option. If an option cannot show a direct link for an element, it does not qualify for a true side-by-side comparison.
Option one is a narrowly scoped path that only lists elements you can point to on the live record. Option two is a broader path that appears to cover more, but requires you to confirm each added element is actually tied to your site on that same live record. The deciding factor is provability, not reach. As noted by CASQA, stormwater quality management involves a large and diverse range of challenges, which means broad labels can exist while the actual record remains specific to each site.
The winner is the option with provable coverage. A broader path is not automatically better, and a narrower path is not automatically limiting. The only way to know is to compare terms line by line against the live record for both options at the same time. Do not add elements from one option to the other to force a match. If you must guess to complete the comparison, that option fails the test.
When each option wins comes down to the record itself. The provably narrow option wins when the live record fully matches your site with no unchecked elements. The broader option can only win if, after a strict line-by-line check, every element it lists is present on the live record for your site with no gaps. With CalMatters reporting that water officials agree capturing more stormwater is a top priority, the pressure to pick the broader path can be high, but that priority does not make an unverified option correct.
Before committing, run a two-column check: one column for elements on your site, the other for elements shown on the live record for the option you are considering. Only commit to the option where those two columns are equal with no unchecked items. That is the comparison rule to use before moving forward.
Frequently Asked Questions
What two live-record items does the guide say to check before committing?
It says to check the live record for the current step count and the applicable NOI deadline.
What verify-before-you-commit checks does the guide focus on?
It focuses on confirming the live record, the exact option, and the stated basis for any fee or deadline before submitting.
What should be verified about the live record before submitting?
Before committing, verify that the live record shows the exact facility name, address, receiving water, and permit category you intend to use.
Why should the portal record not be treated as the permit itself?
The portal record should be read alongside the permit document rather than treated as the permit itself.
What risk can a mismatch in the live record create?
A mismatch can cause a later report, modification, or termination to attach to the wrong site.
What does NOI mean in this context?
NOI means Notice of Intent to be covered by a general permit.
Quick answers
| What is SMARTS? | SMARTS is California's Stormwater Multiple Application and Report Tracking System, the state's online record system for stormwater permit applications and reports. |
| Should the SMARTS portal record be treated as the permit itself? | No, the portal record should be read alongside the permit document rather than treated as the permit itself. |
| What site details must be verified on the live record before committing? | You must verify the exact facility name, address, receiving water, and permit category you intend to use. |
| What does an NOI mean and what must be verified for it? | An NOI is a Notice of Intent to be covered by a general permit, and you must verify that the site and permit category match the live record. |
| What specific items should be confirmed on the live record before submitting? | Before submitting, you should confirm the live record, the exact option, the current step count, the applicable NOI deadline, and the stated basis for any fee or deadline. |
Also worth reading: Understanding Square Acres Precise Measurements and Urban Planning Applications in 2024: Understanding Square Acres Precise Measurements · 7 Key Urban Planning Applications of Generative AI 2024 Survey Results Revealed: 7 Key Urban Planning Applications · Your Complete Guide To St Louis Building Permit Applications: Your Complete Guide To St