Business Continuity Planning for New Jersey Businesses: A Practical Checklist

Business continuity planning has a reputation for producing thick binders nobody opens. For a New Jersey business with 10 to 200 employees, it does not need to be that. It needs to be a short, tested answer to one question: if we could not use our office, our systems, or our people tomorrow morning, how would we keep serving customers and paying staff?

This checklist is organized around the events that actually interrupt South Jersey businesses — coastal and river flooding, prolonged power outages, ransomware, a key person being unavailable, and the plain building problems (fire, burst pipe, failed HVAC) that close an office for days. It is written for owners and operations leads. IT is one section of it, not the whole thing.

First: what you are protecting

Before any technology, write down three lists. Keep them to one page each.

Critical functions. The five to ten things that must keep happening: invoicing and payroll, answering the phone, scheduling patients or jobs, fulfilling orders, meeting regulatory deadlines. For each, note how long you can go without it before real damage occurs — that number is your recovery time objective, and it drives every other decision.

Critical people. Who is the only person who knows how to do each critical function? Those single points of failure are the most common cause of a bad week, and the cheapest to fix: cross-train one more person, and write the procedure down.

Critical systems and data. Which applications and which data each function depends on. Include the obvious (email, accounting, your line-of-business system) and the easily forgotten (the shared spreadsheet the whole office runs on, the vendor portal only one person has a login for).

The continuity checklist

1. Communication

  • A current contact list for all staff — personal cell numbers and personal email — stored somewhere that is not your office or your company email.
  • A decided method for reaching everyone fast (a group text, a phone tree, a Teams channel that works from phones).
  • A customer-facing message ready to adapt: what happened, what still works, how to reach you.
  • Your phone system can forward or re-route calls from outside the office. Cloud-based phone systems such as 3CX make this a settings change; a traditional on-premises PBX may not survive the outage at all. See business phone systems.

2. Backup — the part that fails most often

  • Every critical system is backed up, including cloud services. Microsoft 365 and most SaaS tools do not back up your data in the way most people assume; a deleted mailbox or an encrypted SharePoint library is your problem to restore.
  • At least one copy is somewhere a ransomware attacker inside your network cannot reach — an offline or immutable copy, not just a second drive in the same building.
  • Someone has actually restored a file, a mailbox and a whole system from backup in the last 90 days and timed it. A backup that has never been restored is a hope, not a plan.
  • You know how long a full restore takes. If your recovery time objective is four hours and a full restore takes two days, you have found your biggest gap.

Rivell's data backup and disaster recovery page explains how we structure this for small organizations.

3. Working from somewhere else

  • Staff can securely access the systems they need from home — with multi-factor authentication, not just a password.
  • Laptops or a plan for them. If your team is on desktops, the first day of an office closure is lost before it starts.
  • Any system that only runs on a server in your office is identified, and you know whether it can be reached remotely, moved to cloud hosting, or lived without for a week.
  • Paper or offline fallbacks for the two or three things that absolutely cannot stop (a printed schedule, a manual invoice process).

4. Power and connectivity

  • Battery backup (UPS) on the network equipment and any on-site server, sized to shut things down cleanly — not to run the office.
  • A second internet path for the office (a cellular failover router is inexpensive) if your phones or point-of-sale depend on it.
  • An understanding of what happens to your systems in a multi-day outage. Many South Jersey businesses learned during past storms that a generator for the lights does not help if the internet provider's equipment down the street is dark.

5. Cyber incident response

Ransomware is now the most likely "disaster" for a small organization, and it needs its own short plan:

  • Who to call first — your IT provider, your cyber-insurance carrier's hotline, and (for incidents involving personal data) legal counsel. Write the numbers down on paper.
  • The order of operations: isolate affected machines, do not wipe anything before evidence is preserved, do not pay or negotiate without insurance and counsel involved.
  • Whether your cyber-insurance policy requires specific controls — multi-factor authentication, endpoint detection, tested backups — and whether you actually have them. Carriers increasingly deny claims when the application said yes and the reality was no.
  • Notification obligations. New Jersey has data-breach notification requirements, and regulated industries (healthcare, finance, legal) have their own. Know who you would have to tell and how quickly.

The New Jersey Cybersecurity and Communications Integration Cell (NJCCIC) publishes free guidance and incident reporting for New Jersey organizations and is worth bookmarking. Rivell's cybersecurity services page covers the controls most small organizations need.

6. People and vendors

  • A one-page "if I'm not here" document for each critical role — where things are, how to do the week's essentials, who to call.
  • A list of key vendors (payroll, bank, insurance broker, IT, landlord, utilities) with account numbers and contacts, stored off-site.
  • An agreement with your IT provider on response times during an incident. If you have a managed services agreement, this should already be in it; check. If you rely on break-fix support, understand that you will be in a queue with everyone else affected by the same storm.

7. The plan itself

  • Written down, short, and stored in at least two places that would survive the event — a cloud drive and a printed copy at a manager's home, for example.
  • Reviewed twice a year. Staff change, systems change, phone numbers change.
  • Tested once a year in a low-key way: pick a Friday afternoon, declare the office closed, and have three people run the critical functions from home. The gaps you find in two hours are the ones that would have cost you a week.

How disaster recovery fits in

People use "business continuity" and "disaster recovery" interchangeably. They are not the same. Business continuity is the whole-business plan above. Disaster recovery is the IT portion: how systems and data are restored, in what order, how fast. A good disaster recovery setup makes most of the IT checklist items a matter of configuration rather than heroics — replicated systems that can be switched on elsewhere, backups that restore in hours, remote access that already works. Rivell's disaster recovery services page describes how that is designed and priced for New Jersey organizations.

Who this matters most for

Every business benefits, but some New Jersey organizations have no margin at all:

  • Medical and dental practices — patient records, scheduling and billing stop together, and HIPAA has its own contingency-plan requirement. See healthcare IT.
  • Municipalities, police and EMS — public safety systems cannot wait for a vendor callback. See municipal IT.
  • Law firms — court deadlines do not move because your server did. See law firm IT.
  • Manufacturers and contractors — production schedules and job sites depend on systems most people in the building have never seen. See manufacturing IT.

Frequently asked questions

How much does a business continuity plan cost?
The plan itself costs time more than money — a few working sessions for a small organization. The spending is in the gaps it reveals: proper backup, a second internet connection, laptops, cloud hosting for a system that only runs on a server in your office. Those are priced individually; Rivell's pricing guide explains how backup and disaster recovery are typically structured in a managed services agreement.

How often should we test our backups?
Automated checks should run constantly. A human should restore something real at least quarterly and run a full-system restore test at least once a year.

Is cloud storage the same as backup?
No. Sync services (OneDrive, Google Drive, Dropbox) faithfully sync a ransomware-encrypted file across every device. Backup keeps separate, point-in-time copies you can go back to. You need both.

We are small — ten people. Is this overkill?
Shrink it, don't skip it. For ten people the whole plan fits on two pages: contact list, backup that has been tested, remote access with MFA, who to call for a cyber incident, and one person cross-trained on payroll.

Next step

The fastest way to find the gaps is to have someone look at your current setup against this list. Rivell offers a no-cost IT assessment for New Jersey organizations that covers backup, recovery time, remote access and security controls, and ends with a written summary you keep either way. If you would rather start by talking, contact us.

Facebook
Twitter
LinkedIn