Managed IT for Parksville and Qualicum Beach.
Valley Edge is based in Port Alberni, at the other end of Highway 4. No Oceanside address is claimed on this page or in the structured data behind it. What is here is managed IT written for a business that is not the same size in February as it is in July.
Parksville · Qualicum Beach · Coombs · Errington · Nanoose Bay · Bowser
- Licences counted against payroll, not habit
- Seasonal accounts opened and closed on a date
- Projects booked for the shoulder season
- Your Microsoft 365 tenant stays yours
You are not one size all year. Your IT bill almost always is.
Oceanside runs on a summer. Resorts, restaurants, attractions, the trades that serve them and the shops living off the traffic all staff up in spring and back down in the fall. Nearly every per-user cost in IT is billed monthly whether the person is working that month or not. Nobody sets out to pay for a July crew in January. It happens because releasing a licence is a job with no owner, and it compounds quietly across seasons.
Licences against actual headcount
Count the seats being paid for, count the accounts that signed in this month, and subtract. On a business that swings between a winter core and a summer crew the gap is rarely small, and it has usually been open longer than one season. This is the least interesting work on the page and it is frequently the first line item that pays for itself.
Checked each season, not each year.
Accounts closed on the way out
A seasonal departure is not an event the way a permanent one is. The last shift simply happens and the account stays. Each of those keeps a mailbox live, keeps a seat billing, and keeps a door open into the business. Offboarding here has to be a list run on a date twice a year rather than a decision taken individually every time.
A list with a date on it.
Devices that come back, and devices that do not
A laptop, a tablet at a counter, a phone with the booking app on it. In a business with real turnover, hardware goes home in September and stays there unless somebody is counting. A managed inventory is the difference between knowing that in October and finding it out in May when the thing is needed.
Counted, not remembered.
Most of it is at a counter. Not at a desk in an office.
A resort, a restaurant, a clinic and a shop all have the same shape: a machine at the front that several people use, a card terminal beside it, a booking or property system behind it, and a network the public is sitting on. That is a different problem from an office where everybody has their own laptop, and most managed IT is written for the office.
The shared login is the hard part, and it is worth doing properly
Multi-factor authentication and any kind of per-user audit trail assume a single named human behind each account. A front desk covered by six people across three shifts does not work that way, and telling an operator to stop sharing the login without handing them something workable means they keep sharing it and stop mentioning it. The version that actually holds is individual sign-in on the device with the shared application session kept separate, screens that lock on their own, and a decided answer for what happens when somebody cannot get in halfway through a shift. It is more work to build than a shared password. It is also the only version that is still true in August.
Guest wifi that is genuinely separate
Visitors sharing a network with the till, the booking machine and the office is common, and it is the cheapest thing on this list to fix properly: its own network, its own credentials, no route to anything that matters, and enough bandwidth left over that the business side does not slow down when the parking lot fills.
Payments stay with the payment people
Card terminals and the compliance around them belong to the payment provider and the card brands, and a managed IT agreement does not quietly take that on. What it does cover is the network segment the terminal sits on and keeping that away from everything else, which is the part that usually has not been done.
July is not the month. October is, and that is not negotiable.
A migration, a hardware replacement, a tenant change or a network rebuild all contain a day where something is briefly worse than it was the day before. In a business with a peak season there is a correct time of year for that, and the whole calendar can be planned around it. It is the easiest thing on this page to get right and one of the most commonly ignored.
- Late fall and winter: the projects. Migrations, replacements, tenant changes, anything that needs a day where something is briefly worse
- Spring: onboarding as a repeatable list. Accounts, licences, devices and access created the same way every year instead of improvised under pressure
- Peak: nothing changes that does not have to. Patching, monitoring, backup and support carry on; projects do not start
- Fall: the closing list. Accounts closed, licences released, devices collected, and what is being paid for brought back down to the winter number
The value of writing the year down is that the expensive decisions stop getting made in the busiest month, which is the only month they were ever getting made in.
The visitors leave in September. The population does not.
Parksville and Qualicum Beach carry one of the oldest median ages of any community of their size in Canada, and that is the other business here: dental and optometry practices, hearing and physiotherapy clinics, notaries, law offices, financial advisers, home care and the trades that keep houses standing. Small premises, few staff, and records they are required to keep, protect and be able to produce.
- Personal information held by a private business in British Columbia is governed by the Personal Information Protection Act, and professional bodies set retention requirements on top of that
- A backup answers what a file looked like last week. Retention answers whether a record from a decade ago still exists and whether anything can still open it
- Clinical and practice software belongs to the vendor who publishes it. The machine, the account, the network and the backup around it are what an agreement covers
The obligation belongs to the practice and its regulator. Making it possible to meet is the IT half of it.
- Between two and fifteen staff, one or two rooms, and a practice manager who already has a full job
- The network was usually set up by whoever sold the practice software, and has not been looked at since
- One failure stops the whole day: the machine at reception, the one server under the desk, or the internet
- Support has to arrive without a site visit, because a site visit is tomorrow at the earliest
This is why remote capability matters more here than a van does, and why the inventory comes first.
- An older client base means the phone, the printed letter and the front counter are current channels, not legacy ones
- Online booking that half works is not a smaller problem than none, it is a phone call you now have to take twice
- Text size, colour contrast and forms that can be completed without a fight are a business requirement rather than a preference
This is a design constraint with a census behind it, not an assumption about anybody. It is also the argument for testing a front end against the people who will actually use it.
We run nine people in February and twenty-four in July. How is that handled?
By counting twice a year instead of once. Per-seat costs are billed monthly whether the person is working or not, so a licence left open after a summer that ended in September is money leaving every month until somebody notices. The workable arrangement is a seat count reviewed at the start and the end of a season, licences released as soon as they stop being used, and a written opening and closing list so it happens on a date rather than when it occurs to somebody.
Can our seasonal staff share one login at the front desk?
They can, it is the most common arrangement in hospitality, and it is exactly why nobody can say afterwards who did something. The version that survives a busy Saturday is sign-in per individual on the device with the shared application session handled separately, screens that lock themselves, and an agreed answer for what happens when somebody is locked out mid-shift. A control that gets ignored at two in the afternoon on a long weekend is not a control.
When would the disruptive work actually get done?
Out of season, deliberately. Migrations, tenant changes, hardware replacement and network rebuilds all contain a day where something is briefly worse, and there is a correct time of year for that in a business with a peak. The quiet months get the projects. The busy months get patching, monitoring, backup and support and nothing else. If something genuinely cannot wait until October, that is said plainly rather than dressed up as routine.
Our booking system is run by the software company. What is left for you?
Everything it sits on. The machine, the account that signs into it, the network it has to reach, the device at the counter, the backup of whatever can be exported, and being the one who calls the vendor when it stops working instead of leaving that to whoever is free. The agreement names which applications are covered that way, so it is settled in writing rather than argued about during an outage.
Do you come out to Parksville?
For the physical work, yes, booked. Everything that does not need hands — a licence, a mailbox, a permission, a patch, a password reset, most of what breaks in software — is done from here, which is faster than any drive. Port Alberni is at the other end of Highway 4, so a visit is a scheduled thing, and a business that needs somebody on site regularly should have that written into the agreement rather than assumed.
No Oceanside office. The other end of Highway 4.
Valley Edge is in Port Alberni, which makes Oceanside the closest market to it that is not its own. The work genuinely reaches Parksville, Qualicum Beach, Coombs, Errington, Whiskey Creek, Nanoose Bay, Bowser and Deep Bay. Remote for the large majority of a managed agreement, scheduled on site for the parts that are physical, and that is a service area rather than a second address.
Tell us what your July looks like.
How many people, how many logins, and how many seats you are still paying for from last summer. We will tell you what the gap is worth and what closing it actually takes.
info@valleyedgeconsulting.io · 778-488-8618