The SOCP refresh is actually worth reading this time
CBSA published the updated System Outage Contingency Plan on April 16, and for once the "clarity and consistency" line isn't pure bureaucratic filler. The last version predated full CARM rollout, so it still had one foot in the old portal world. This revision finally reconciles what happens when CARM Client Portal, the Release Prior to Payment system, or eManifest go offline after you've been forced to live entirely inside the new ecosystem.
The big shift: clearer bright lines on what constitutes a valid electronic submission attempt during an outage, and what triggers the fallback to paper. That matters because CBSA's tolerance for "I couldn't file electronically" has narrowed since CARM became the single point of entry for financial transactions. If you're used to the old dance where a quick call to your district office bought you latitude, recalibrate.
Electronic data submission is not optional unless it's actually impossible
The updated SOCP tightens the language around when you're allowed to bypass electronic filing. The test isn't "my broker's system is slow" or "the portal timed out once." It's whether CBSA's own commercial systems are confirmed down by CBSA, usually via a posted service alert or direct communication from the Border Commercial Consultative Committee working group.
That means if CARM Client Portal is sluggish but technically reachable, you're still expected to file there. If your internal systems can't talk to CARM because your API integration is flaking out, that's your problem, not an outage. The contingency plan only kicks in when CBSA declares the outage, not when your workflow hits a snag.
This has teeth now because Release Prior to Payment depends entirely on CARM being up and your financial security posted correctly in the portal. If CBSA systems go down and you're mid-shipment, you're potentially stuck at the border unless you know exactly which manual processes are still available and which aren't. The SOCP clarifies that for RMD and other Customs Act release types, you can revert to paper B3s and manual accounting, but the conditions are narrow and the documentation requirements are explicit.
What the fallback actually looks like
When CBSA confirms a commercial system outage, the SOCP permits:
- Paper B3 submissions for cargo release, but only if eManifest or CARM Release are confirmed unavailable.
- Delayed accounting document transmission, with specific timelines for when electronic submission must resume post-restoration.
- Manual cargo release at primary inspection facilities, but expect longer processing times and possible examinations that would've been waved through electronically.
What it does not permit:
- Skipping the RPP bond or commercial bond requirements. Even in an outage, financial security obligations don't evaporate.
- Indefinite delays on final B3 filing. The SOCP gives you a window, usually 5 business days post-outage, to get compliant electronic records into CBSA's hands.
- Using the outage as cover for sloppy data. Incomplete or incorrect paper submissions during an outage still generate post-release adjustments, and CBSA has been clear that CARM's audit trail for those corrections is more aggressive than the old D-memo routine.
SIMA goods and subject merchandise get no special carve-outs
One thing the updated SOCP doesn't do: create exceptions for high-risk or duty-sensitive goods. If you're importing subject goods under a SIMA order, the normal provisional duty and PRM requirements still apply during an outage. You're just filing them on paper instead of in CARM, and you're still on the hook for the same tight timelines on final determination and duty adjustments.
Same goes for origin claims under CUSMA, CETA, or CPTPP. The outage doesn't extend your proof-of-origin deadline or let you skip the commercial invoice backup. It just means you'll be couriering paper declarations to your local CBSA office instead of uploading PDFs to the Client Portal. Plan your document workflow accordingly, because if the outage hits on a Friday and you've got a Monday release deadline, you're not getting an automatic extension.
Broker capacity during outages is tighter than it used to be
Here's the operational reality: most brokers, including us, have leaned hard into CARM automation over the past year. We've built API integrations, streamlined portal submissions, and reduced headcount on manual data entry because the system was supposed to make that redundant. When CBSA systems go down and we revert to paper, that efficiency gain reverses fast.
If you're working with a broker who doesn't maintain dual-track capability for paper and electronic submissions, an outage will expose that gap immediately. You'll see delayed responses, missed release windows, and a scramble to find staff who still remember how to fill out a paper B3 correctly. The SOCP assumes brokers can pivot seamlessly, but capacity constraints are real, especially during peak periods like month-end or post-holiday cargo surges.
Our advice: test your contingency plan before you need it. Run a tabletop exercise with your broker where CARM goes offline the morning of a PARS release. Who calls whom? What's the fallback communication channel if email is down? Where do the paper documents get physically delivered, and who signs for them? Those details matter more than the policy language in the SOCP.
The compliance risk doesn't pause during an outage
CBSA has been explicit that outage contingencies are procedural, not substantive. Your obligations under the Customs Act, the SIMA regulations, and your importer obligations don't soften because the portal is offline. That means if you misclassify an HS code on a paper B3 during an outage, the correction process and potential penalties are the same as if you'd filed electronically.
Same for drawback claims, NRI penalties, and all the other trade compliance landmines. The SOCP gives you a process to keep cargo moving, but it doesn't give you legal cover for substantive errors. If anything, manual submissions increase risk because you lose the real-time validation checks that CARM usually provides.
If you're managing compliance in-house, make sure your team knows the difference between "the system is down so we're filing on paper" and "the system is down so the rules don't apply." The first is fine. The second gets you audited.
What to do before the next outage
Document your own internal contingency protocols now, while systems are stable. Know which CBSA offices handle your primary cargo volumes, and have direct contact info for your district Commercial Operations contacts. Keep a current copy of the SOCP in your shared drive, not just bookmarked on CBSA's website.
If you're relying on Release Prior to Payment, make sure your RPP bond is sized correctly and that your CARM financial security dashboard is accurate. An outage is the worst time to discover your bond limits are maxed out or your BN15 registration has a typo. Run a quarterly reconciliation, especially if your import volumes are climbing.
And if you're using multiple brokers across different ports or commodity lines, confirm they're all working from the same playbook. The SOCP is national, but broker interpretation and capacity vary. The last thing you need during a CARM outage is one broker filing paper B3s while another insists on waiting for the portal to come back online.
If your contingency planning is still more concept than checklist, or if you're not confident your current broker can handle manual fallback without chaos, get in touch. We run these scenarios every quarter, and we know which parts of the SOCP are theory versus practice.
Originally published at https://www.canflow-global.com/en/insights/cbsas-updated-system-outage-contingency-plan-what-actually-changes-when-the-ligh/.
