Example IT Scenarios for Edmonton Businesses

The scenarios below are illustrative. They describe situations that Edmonton businesses commonly face and how we approach each one. They are composites, not accounts of specific clients, and they contain no client names or results. We include them so you can see how we think before you call.

A lawyer leaves and the firm needs the files, not the risk

The situation. An associate gives two weeks’ notice. Their mailbox holds active client correspondence, their laptop has locally cached documents, and they are signed in to the practice-management system on a personal phone.

What we would do. On the last day we block sign-in and active sessions, move the mailbox to a supervising lawyer, collect the laptop and wipe it after preserving anything that must be kept, and remove access to the document system and shared drives. We record each step so the firm can show what was done.

What changes. Client files stay with the firm, the departing lawyer’s access ends the same day, and there is a written record. The checklist then becomes the firm’s standard offboarding procedure. See IT support for law firms and our cybersecurity service.

Imaging stops at ten in the morning

The situation. A dental clinic has a full schedule when the sensor software on one operatory workstation will not start.

What we would do. We begin remote troubleshooting immediately. If the fault is the workstation itself, a pre-configured spare can be swapped in so the room is working again, and settings and images are restored from backup on the failed machine afterwards. We then find the cause, such as a bad update, a failing drive or a licence problem, and fix it in the other rooms before it repeats.

What changes. The clinic can keep working through the day using its downtime procedure, and the cause is removed rather than repeated. See IT support for dental and medical clinics and backup and recovery.

The internet drops on a busy Saturday

The situation. A retailer with three stores loses the main internet line at one location on a weekend, and card payments stop.

What we would do. A well-built store network keeps the payment terminals on their own secured network with a cellular backup connection that takes over automatically. We design and test the failover, monitor each store’s connection, and keep the configuration identical across locations so a fix at one store works at all of them.

What changes. A line outage becomes an alert instead of a closed till, and the owner can see which store, which line and for how long. See IT support for retail and network setup.

A new jobsite needs to be online by Monday

The situation. A contractor wins a project outside the city. The site trailer has no wired service, and the project team needs current drawings on tablets.

What we would do. We set up cellular-based connectivity in the trailer, kept separate from the office network, and give the site team access to that project’s drawing folders through cloud storage with permissions limited to the project. When the job finishes, we remove the access and retire the equipment.

What changes. The site has connectivity from day one, drawings live in one place, and nothing is left exposed after handover. See IT support for construction and cloud services.

A convincing email arrives during tax season

The situation. A bookkeeper receives a message that appears to come from a client and asks them to open a “revised slip”.

What we would do. Email filtering stops most messages like this before delivery. For the ones that get through, multi-factor authentication limits what a stolen password can do, and staff know to report rather than open. If someone does click, we reset the account, review recent activity on the mailbox and check the device.

What changes. A mistake becomes a contained, reported incident instead of a breach of client records. See IT support for accounting firms and our guide to multi-factor authentication.

Files are encrypted on a Monday morning

The situation. Staff at a twelve-person office arrive to find documents renamed with an unfamiliar extension and a note demanding payment.

What we would do. We isolate the affected computers from the network, work out how far the problem spread and confirm which backups are clean. Recovery is a restore from a tested backup, not a payment. Then we close the way in, often a reused password or an unpatched system, and add the controls that were missing.

What changes. The office returns to work from known-good copies, and the incident is documented along with what changed afterwards. See IT support for offices, how to prevent ransomware and how to write an incident response plan.

Talk to us about your situation

If one of these looks familiar, call +1 (587) 400-9991 (also on WhatsApp) or send us a message. You can also read about our managed IT services in Edmonton.