Shabbat Readiness Checklist for digital businesses.
A practical checklist covering websites, payments, CRM, automations, cloud jobs, monitoring alerts, backups, access requests, and support coverage — so nothing creates unintended business activity on Shabbat.
- Map every system that can act on Shabbat
- Classify passive vs business-generating actions
- Decide pause, delay, block, route, or release
- Plan the post-Shabbat release workflow
Built from real operations
Each line item reflects a system that quietly keeps working after sundown — the storefront, the payment gateway, the nurture sequence — so your review starts from how the business actually runs, not a generic template.
A clear decision for each item
For every system you choose one outcome — pause, delay, block, route, or release — turning an abstract policy into concrete, auditable settings your team and leadership can sign off on.
Ready for the release
The final section covers what happens after Shabbat ends: how queued orders, messages, and jobs are released in order, so customers and operations resume smoothly without a backlog scramble.
Why a structured checklist matters
Complexity scales with your digital footprint
A single digital business can run dozens of systems in parallel — a storefront, a payment processor, email marketing, CRM pipelines, marketing automations, cloud batch jobs, webhooks, and alerting pipelines. Each one may fire actions on its own schedule without any human instruction. Without a systematic review, there is no reliable way to know which of these will act on Shabbat, or whether that activity is passive uptime or active business generation.
Halacha requires intentional design, not hope
The halachic framework for digital commerce during Shabbat is not satisfied by good intentions. What matters is the actual behavior of each system: whether a transaction completes, whether money changes hands, whether an automated agent takes a business action on behalf of a Jewish owner. A checklist forces you to move from 'I think it's probably fine' to 'I have reviewed each system and made a deliberate, documented decision about each one.'
One missed system can undermine everything
Observant business owners who invest deeply in Shabbat compliance regularly miss one or two systems — a third-party integration added months ago, a cron job configured by a contractor, a fallback email sequence nobody remembers. Working through a systematic checklist ensures the review is complete. The written audit trail demonstrates due diligence to rabbinical authorities, business partners, and investors who need to understand the compliance posture.
The 8-step readiness checklist
- 1
Map every system in your stack
Create a complete inventory: website, mobile app, payment gateway, CRM, email platform, marketing automations, cloud batch jobs, cron tasks, webhooks, API integrations, monitoring tools, and third-party services. Include anything added in the past 12 months — new integrations are the most common compliance gaps.
- 2
Classify passive vs business-generating
For each system, determine whether it performs passive uptime (serving cached web pages, maintaining infrastructure health) or active business actions (processing orders, charging payment methods, sending commercial email, creating CRM records, triggering fulfillment, or updating customer-visible data). Only active systems require a compliance decision.
- 3
Decide the behavior for each active system
Choose exactly one outcome for each active system: Pause (stop the action until Shabbat ends), Delay (accept but queue for release after Havdalah), Block (reject with a clear message to the customer), Route (hand off to a non-observant service or team member), or Release (allow with documented halachic justification). Record the decision and the authority behind it.
- 4
Set up monitoring and alert routing
Configure your monitoring so that non-urgent alerts are held in a queue during Shabbat and released at its end. Define which categories constitute a true emergency — physical safety, security breaches, material service outages — and create a dedicated escalation path for those alone. All other alerts wait. Document the threshold for each alert category in writing.
- 5
Configure the post-Shabbat release
Design the release sequence: which queues flush first, in what order systems re-activate, and how long to stagger each batch to prevent downstream cascades. Define the exact trigger — a scheduled cron after Havdalah time, a manual action, or a webhook from a Shabbat time API. Verify that queued items release in the correct order and that customers receive appropriate follow-up communications.
- 6
Test before a real Shabbat
Run a simulated Shabbat test in your staging environment or during a short Friday afternoon window before sunset. Confirm that queues fill correctly, that alerts route as expected, that blocked transactions return the right user-facing message, and that the post-Shabbat release executes in the correct order. Fix any failures and re-test before going live.
- 7
Communicate the policy to your team
Brief every relevant team member and vendor on the Shabbat policy: what systems are paused, what releases after Havdalah, who is the on-call non-observant contact for genuine emergencies, and what customers will see if they attempt a transaction during Shabbat. Ensure support staff know how to respond to Shabbat-related inquiries without creating an unintended business transaction.
- 8
Document, audit, and review on a schedule
Keep a written record of every decision made in steps 1–7: the date of the review, the halachic authority consulted, and the exact configuration applied to each system. Set a reminder to re-run the full checklist after any significant tech-stack change, after adding new vendors or integrations, and at least once annually — or before each major holiday season if your volume spikes around Yom Tov.
Frequently asked questions
Does 'passive uptime' mean I don't need to configure anything for my site to stay online?
Correct, for static content. If your website serves cached pages without triggering new transactions — no new orders, no sign-ups being processed, no real-time pricing calls — it can remain fully online. Compliance configuration applies to any interactive element that creates or completes a business action. Serving a product listing page is passive; accepting a checkout form submission is active.
What should I do if I have a system I can't pause or reconfigure?
First confirm under halachic analysis whether the action it performs qualifies as a forbidden business transaction. If it does and cannot be paused, the next step is to route it: hand the action to a non-observant team member or third-party service during Shabbat hours. If routing is also impractical, document the situation fully and consult a posek before Shabbat — never leave an active system unaddressed and assume it will be fine.
How far in advance should I complete this checklist?
Complete a first-pass review at least four weeks before your target compliance date. This gives time to configure each system, run tests, fix edge cases discovered during testing, and re-test. After initial implementation, re-run the checklist whenever you add a new integration, bring on a new vendor, or deploy a feature that touches payments, signups, or customer communications.
Should I involve a rabbi or halachic authority in this process?
Yes. The technical checklist identifies what each system does; the halachic analysis determines whether that activity is permitted or requires modification. Bring your completed inventory and proposed decisions to a posek before finalizing any configuration. ShabbatCloud can provide technical documentation and system-behavior reports to support that conversation, so the posek can evaluate business behavior rather than technical architecture.
Does the same checklist apply to Jewish holidays (Yom Tov)?
Largely yes. The system-by-system approach and the five decision outcomes apply to Yom Tov as they do to Shabbat. The key difference is timing: Yom Tov windows vary by holiday and location, diaspora communities observe two days for most holidays, and some Yom Tov restrictions differ from Shabbat at the halachic level. Configure your scheduler with the full holiday calendar — ShabbatCloud provides Yom Tov times alongside Shabbat times — and run the same compliance review ahead of each major holiday season.
Ready to implement?
ShabbatCloud helps you move from this checklist to a working configuration — in your stack, for your business, with documentation that stands up to rabbinical review.