Category: Managed IT Services

iPads are the easiest hardware a business ever buys. Someone opens the box, taps through the setup, installs three apps, and it works. No imaging, no domain join, no arguments.

That ease is exactly why the problem creeps up on you. Nobody plans an iPad rollout, because for the first twenty there is nothing to plan. Then a dozen more arrive, the apps need updating, somebody leaves with one, a passcode gets forgotten, and the person who has been quietly handling all of it starts spending real hours on it every week.

Here is where that curve actually bends, and what changes on the other side of it.

The Number Where Manual Setup Stops Working

It is lower than people expect, and it is not really about the count.

Twenty iPads handed to twenty people who each keep their own is manageable indefinitely. Twenty iPads that get passed between shifts, loaned to visitors, or reassigned when someone leaves is already past the line. The variable that matters is how often a device changes hands, not how many you own.

Three symptoms tell you that you have crossed it. Setting one up takes someone more than a few minutes and they do it from memory rather than a written standard. Nobody can say with confidence how many you have or where they are. And when a device comes back, getting it ready for the next person means someone physically sitting with it.

Any one of those is a signal. All three together means you are already paying for management in staff time, just not on an invoice where anyone can see it.

Apple Business Manager Is the Part You Cannot Skip

This is the foundation, it is free, and it is the step most businesses discover a year too late.

Apple Business Manager is the portal that links the hardware you bought to the organisation that owns it. It does two things that nothing else can. It lets devices bought through Apple or an authorised reseller enrol themselves automatically the first time they connect — a genuinely hands-off setup. And it lets you buy apps in volume and assign licences to devices or people, so an app licence returns to your pool when a device is reassigned instead of being stranded in a departed employee’s account.

The catch is that devices only flow into it automatically when they were purchased through a linked channel. A cupboard of iPads bought from a consumer retailer, or picked up over the years by different departments, does not appear. Those can be enrolled by other means, but the automatic path is closed to them permanently.

The practical conclusion is uncomfortable but worth stating plainly: how you buy the hardware determines what you can do with it afterwards. If you are going to run iPads in any number, route the purchasing through a channel that feeds Apple Business Manager before you buy the next batch. Buying through a managed program handles that linkage by default.

Supervision Has to Happen Before the Box Is Opened

Supervision is the state that separates a business iPad from a personal one, and it is the source of most of the capability you actually want.

A supervised iPad can have specific applications hidden, be locked to a single app for a kiosk or a point of sale, have web content filtered, be prevented from having its management removed, and be located when it goes missing. Without supervision you are limited to a much shorter list of polite requests the user can decline.

Supervision applies cleanly when a device enrols automatically on first setup. Applying it to a device already in service means erasing it, which is a very different conversation with the person holding it. This is the single most common expensive mistake in this area — a business enrols its existing devices without supervision to avoid disruption, then discovers eighteen months later that half the features they are paying for do not apply.

If you are setting this up on devices already in the field, bite the bullet during a natural break: an OS upgrade cycle, a school holiday, a slow week. Erasing thirty iPads once is cheaper than running thirty half-managed ones for three years.

Jamf Pro, Jamf School, or the Platform You Already Own

Three realistic answers, and the right one depends on what else you run.

Jamf Pro is the deepest option for Apple hardware and the one to pick if iPads are core to how the business operates — clinical settings, field crews, retail floors, anything where a broken device stops work. It handles complex app deployment, granular configuration, and reporting that stands up to an audit. It is also the most work to set up properly, which is a real cost, not a footnote.

Jamf School is simpler and cheaper, built for one-to-one programmes and shared carts. Despite the name it suits plenty of businesses running straightforward deployments — the same device doing the same job, many times over.

What you already own deserves an honest look before you buy anything. If the business is on Microsoft 365 with a plan that includes Intune, it handles iPads competently for ordinary use: enrolment, app deployment, passcode and encryption policy, remote wipe. Where it runs out is the Apple-specific depth — same-day support for new iPadOS features, the more intricate configuration, kiosk scenarios. For a business with thirty iPads doing ordinary work alongside Windows PCs, adding a second platform is often the wrong trade — the same calculation we walk through for Macs in a Windows business.

The question we ask before recommending either way: are the iPads incidental to the business, or are they how the business runs? That answer settles it more reliably than the device count does.

Declarations Instead of Commands

Worth understanding because it changes what you should expect, and it is the direction everything Apple is moving.

The older model was conversational. A server sent a command, the device acknowledged it, and the server asked again later to find out whether it stuck. Devices that were asleep, off the network, or simply busy drifted out of compliance silently, and you found out at the next check-in — which might be hours or days.

The newer model hands the device a declaration of how it should be and makes the device responsible for staying that way and reporting when its state changes. Settings apply faster, operating system updates are more reliable, and compliance reporting reflects reality rather than the last successful conversation.

What this means practically: if you are evaluating platforms, ask how fully each one implements this, not just whether it supports it. And if your current setup produces reports you have learned not to trust, that is very often what you are looking at.

Shared iPads and the Accounts Behind Them

If several people use the same device across a day, this is the feature that makes it work, and it is underused because few people know it exists.

Shared iPad gives each person their own sign-in on the same physical device, with their own data and settings, cached locally so switching is quick. A nurse, a shift worker, or a student signs in, sees their own environment, signs out, and the next person gets theirs. Compared to the common alternative — one generic account everyone shares, with everyone’s data mixed together and no way to tell who did what — it is a significant improvement in both usability and accountability.

It runs on managed accounts that your organisation creates and controls, and these can now federate with Microsoft Entra ID or Google Workspace, so people sign in with credentials they already have. That federation is what makes the feature practical; without it you are maintaining a second set of identities, which nobody sustains.

Two constraints to plan around. It needs storage headroom, because each cached user takes space, so the base-model 64GB devices are a poor fit. And not every application behaves well with fast user switching, so test the ones that matter to you before committing a cart to it.

Getting a Device Ready for the Next Person Without Touching It

The workflow that saves the most staff time is the least known one.

Return to Service lets a managed iPad be wiped and brought back to a fully configured, enrolled state remotely, connecting to the wireless network on its own without anyone tapping through setup. A device comes back from a departing employee, someone triggers it from a console, and it is ready for the next person without anybody sitting with it.

For a business reassigning devices a few times a year this is a convenience. For a shift-based operation, a seasonal workforce, or anywhere devices circulate constantly, it is most of the reason to be managed at all. When people ask what the platform actually buys them, this is usually the most concrete answer available.

iPad Questions, Answered

How many iPads before we need a management platform?
There is no fixed number. The real trigger is reassignment — if devices regularly change hands, you are past the point where manual setup makes sense, even at fifteen or twenty.

Can we manage iPads we already bought from a retail store?
Yes, but not automatically. They can be enrolled manually, and supervision requires erasing them. Devices bought through a linked purchasing channel enrol themselves on first setup with no hands-on work.

Do we need Jamf if we already pay for Microsoft 365?
Often not. If your plan includes Intune, it handles ordinary iPad use competently. Jamf earns its place where iPads are central to operations or where you need Apple-specific depth and same-day support for new iPadOS releases.

What happens to app licences when an employee leaves?
Bought in volume through Apple Business Manager, they return to your pool and can be reassigned. Bought on a personal account with a personal card, they leave with the person, along with the receipt nobody can find.

Can we lock an iPad to a single application?
Yes, on a supervised device. It is the standard approach for point-of-sale terminals, check-in kiosks, and display units, and it also stops a shared device wandering into general use.

Is it worth managing only twelve iPads?
If they are personally assigned and rarely move, probably not. If they are shared, circulated, or handle anything sensitive, the answer is usually yes — the value is in reassignment and recovery, not in the number of devices.

Not Sure Which Way to Go?

We run Apple deployments for businesses across Los Angeles, Orange County, and the Bay Area, and we will tell you honestly when the platform you already pay for is enough — that answer comes up more often than people expect.

Call (213) 873-7620 or book a free IT assessment and we will look at what you have, how it moves, and what it would take to run it properly.

Related reading: What Is EDR? · Windows 10 After October 2026

An employee resigns on a Friday afternoon. By Monday, someone has collected the laptop, HR has the paperwork, and everybody considers it handled.

It is usually not handled. The laptop is the visible part and the least important one. What matters is the forty or fifty places that person could still sign in from any device in the world — and in most businesses, nobody has a list of those places.

We are called in after this goes wrong often enough to recognise the pattern. Here is the sequence that actually protects the business, in the order it needs to happen.

The First Hour Is About Access, Not Hardware

The single most important action is also the one most often skipped: disable the account and invalidate the sessions.

Changing a password is not enough on its own. A browser that is already signed in stays signed in, sometimes for weeks, because the session token was issued before the password changed. Someone can walk out of the building, open a laptop at home, and still be inside your email. The step that closes this is revoking active sessions and refresh tokens, and it takes about thirty seconds when someone knows to do it. Where sign-in runs through one corporate identity, it is a single action rather than forty.

The order that works: disable the account, revoke active sessions, remove the second factor enrolment so it cannot be used to re-authenticate, then convert the mailbox rather than deleting it. Deleting is the instinct and it is the wrong move — we will come to why.

Do this at the moment of separation, not at the end of the day. For a voluntary departure with notice, that means the moment the last day arrives. For anything involuntary, it means while the conversation is happening, not after it.

Where Access Actually Hides

Your directory covers what your directory knows about. The exposure lives in what it does not.

Applications signed up for directly. Every service a department adopted with a corporate card and a work email. Marketing tools, design software, scheduling apps, the analytics platform somebody trialled in 2023. These are the ones that outlive an employee by years.

Shared logins. The social accounts, the domain registrar, the account with the freight company, the bank portal with one login the finance team passes around. If a departing person knew any shared credential, it has to change, and there is no automated way to know which ones they knew.

Personal devices. Company mail configured on a personal phone is the most common one. If it was set up outside your management, removing it is a conversation rather than a command.

Keys and tokens rather than passwords. API keys, SSH keys, personal access tokens, service accounts created under an individual’s name. These are invisible to a normal offboarding checklist and they do not expire. For any technical role, this is the category that matters most and gets checked least.

External systems. Client portals, vendor extranets, the building access system, the alarm code, the shared drive a customer granted access to. None of it is yours to disable, which is exactly why it has to be on a list.

The Mailbox Is a Business Record, Not a Person’s Inbox

Deleting a departed employee’s mailbox to save a licence is the most expensive small saving in this whole process.

That mailbox holds contract negotiations, client commitments, vendor agreements, and the paper trail of whatever the person was in the middle of. You will want it during a dispute, an audit, or a customer relationship that turns sour eighteen months later. In litigation, having destroyed it is materially worse than the storage cost of keeping it.

What to do instead: convert it to a shared mailbox, which generally removes the licensing cost while preserving the contents, and give the manager access. Set up forwarding or an auto-reply that names a real human being — not a generic address — so clients are not writing into silence. Keep it for as long as your retention policy says, and if you do not have a retention policy, this is the moment to write one.

The same logic applies to files. Personal storage areas disappear with the account unless you transfer ownership first. Do that before disabling anything, not after, because recovering it afterwards is a support ticket and sometimes an impossibility.

Getting the Laptop Back, and What If You Cannot

For anyone in the office, this is a solved problem: collect it on the last day and check it in against an asset record.

Remote staff are where this quietly falls apart. A prepaid shipping box sent before the last day, with a deadline and a named person expecting it, recovers the hardware far more reliably than an email asking them to send it back. Companies routinely lose machines simply because nobody made returning one easy.

If a device does not come back, you need to have decided in advance what you can do about it. A machine enrolled in management can be locked or wiped remotely; an unmanaged one cannot, and that is a decision you made months earlier whether or not you realised it. Encryption is the backstop — an encrypted disk with the account disabled is a brick to anyone who has it, which converts a data breach into an inventory write-off.

Whatever comes back, do not hand it to the next person still carrying the old profile. Wipe and rebuild. It takes an hour and it prevents the category of incident where somebody finds a predecessor’s files on a machine they were given.

The Departure Nobody Planned For

Everything above assumes two weeks’ notice and a civil exit. Plan for the other kind, because that is when the gaps cost real money.

For an involuntary termination, access should be cut during the meeting, not after it. That means HR and IT coordinate on a time, and someone is ready to execute at that minute. The usual failure is a well-intentioned delay — waiting until the person has left the building, by which point they have had forty minutes on a phone.

Where there is genuine concern about the circumstances, preserve before you change anything. Take a copy of the mailbox and the files first, then disable. Once accounts start getting altered, reconstructing what was there becomes an expensive forensic exercise rather than a copy operation.

And write down what a departing person had access to, on the day they leave. Six months later, when a question arises, that list is the difference between a short answer and a very long investigation.

What Should Exist Before Anyone Resigns

All of this is straightforward when the groundwork is in place and close to impossible when it is not.

Three things to have ready. An inventory of every service the business pays for and who can sign in to each — this is the one nobody has and the one that makes everything else possible. A named owner for each of those services, so there is someone to ask. And a written sequence with the steps in order, so the process does not depend on whoever happens to be available that afternoon.

Single sign-on is what turns this from a checklist into a switch. Where staff reach applications through one corporate identity, disabling that identity closes most doors at once. It is worth doing for that reason alone, separate from any security argument, and it pays for itself the first time somebody leaves in a hurry.

Offboarding Questions, Answered

How quickly should access be cut off?
At the moment of separation. For a resignation with notice, the last working day. For an involuntary termination, during the conversation rather than after it.

Should we delete the account to save the licence?
No. Disable it and convert the mailbox to shared storage, which usually removes the licence cost while preserving the contents. Deleting destroys business records you may need for years.

What if the employee will not return their laptop?
A managed machine can be locked or wiped remotely. An unmanaged one cannot, which is why full disk encryption matters — with the account disabled and the disk encrypted, the hardware is a loss rather than a breach.

Do we have to change shared passwords every time someone leaves?
Any shared credential the person knew, yes. This is the strongest practical argument for replacing shared logins with individual accounts, which makes a departure a single revocation rather than a scramble.

How long should we keep a former employee’s files and email?
As long as your retention policy specifies, and longer if there is any hint of a dispute. Most businesses land between one and seven years depending on their industry and what their clients require of them.

What about access to systems that belong to our clients?
Notify the client and ask them to remove the account, then confirm in writing that they did. You cannot revoke it yourself, and an orphaned account on a customer’s system is their exposure and your reputation.

Want This Running Without You Thinking About It?

For the businesses we support, departures follow a documented sequence with a record of what was done — access closed the same day, mailboxes preserved properly, hardware tracked, and a written list of what that person could reach. Nobody has to remember the steps at four o’clock on a Friday.

Call (213) 873-7620 or book a free IT assessment and we will start with the inventory of who can sign in to what, which is usually the eye-opener.

Related reading: Dark Web Monitoring for Business · CCPA Compliance in 2026

Your staff are already using AI at work. Not the tools you approved — the ones they found. A marketing coordinator pasting a client list into a chatbot to draft outreach. A bookkeeper uploading a spreadsheet to summarise it. A manager asking a free tool to rank job applicants.

None of them think they are doing anything wrong, and mostly they are not. The problem is that nobody wrote down where the line is, so every employee is drawing it themselves, differently, and you will find out where they drew it during an incident.

A written acceptable use policy is the cheapest control available here. It is a document, not a project. Here is what belongs in it, section by section, and what we see go wrong in each.

Why a Verbal Understanding Is Not a Policy

Three things a document does that a conversation cannot.

It gives employees permission. Most people are guessing, and a surprising number have quietly stopped using tools that would genuinely help them because nobody said it was allowed. An unwritten rule suppresses the useful behaviour along with the risky one.

It gives you something to enforce. Discipline for violating a rule nobody published is difficult to defend, in an employment dispute and in a room with your own staff.

And it gives you something to show. Clients ask. Insurers ask. Anyone doing vendor due diligence on you asks, and increasingly they ask in writing. “We handle that informally” is a bad answer to give a customer whose data you hold.

Name the Tools, Not the Technology

The most common drafting mistake is writing rules about “artificial intelligence” in the abstract. Employees cannot apply that, because they do not think of the transcription feature in their meeting software or the summarise button in their inbox as artificial intelligence. They think of it as a button.

Write a list instead. Approved tools, named, with what each one may be used for. Then a short section on what to do about anything not on the list — who to ask, and how long an answer takes. Make requesting a new tool easy, because a slow approval process is how shadow usage starts.

If you have not settled which tools belong on that list yet, that is a separate exercise and worth doing deliberately rather than by default. Keep the list in a place that can be updated without reissuing the policy. An appendix or an intranet page referenced by the policy works; a list baked into a signed PDF does not, and will be out of date within a quarter.

The Data Rules Are the Whole Document

If you write nothing else, write this section. It answers one question: what may never be typed, pasted, or uploaded into one of these tools?

Be concrete. “Confidential information” means nothing to a staff member at 4pm on a deadline. Name the categories your business actually holds — client financial records, patient information, employee files, unreleased designs, anything under a customer NDA, source code, case files. List them explicitly, because the person reading this is trying to do their job, not parse your definitions.

Then explain the distinction that most people have never had explained: a consumer account and a business account are not the same product. Free and personal-tier tools frequently reserve the right to train on what you submit. Business and enterprise tiers generally contractually do not. This is the single most useful thing a policy can teach, and it is the reason the approved-tools list exists at all — not because the technology differs, but because the contract does.

Finish with the practical rule that covers the cases you did not anticipate: if the information would need an agreement in place before you emailed it to an outside company, it needs one before you paste it into a tool.

Hiring and Employment Decisions Need Their Own Clause

This is where California businesses have an obligation most have not registered.

Regulations under the Fair Employment and Housing Act, in effect since 1 October 2025, cover automated decision systems in employment. The definition is deliberately broad — any tool that assists or replaces human discretion in screening, ranking, or evaluating candidates. A manager using a general-purpose chatbot to sort a stack of résumés is inside that definition, whether or not anyone bought software for the purpose.

Two consequences for the policy. First, employment screening should be a named, restricted use rather than something left to a manager’s judgment. Second, the regulations carry a four-year record retention requirement for material related to those decisions — which means the relevant use needs to be visible and documented rather than happening in someone’s personal browser tab.

The same logic applies to performance reviews, promotion decisions, and disciplinary write-ups. Say plainly whether these tools may be involved, and if so, who reviews the output before it becomes a decision.

Disclosure, Review, and Who Signs Their Name

Three questions the document should answer without hedging.

Does work that goes to a client need to say it was assisted? Different businesses answer differently and both answers are defensible, but employees need to know which one is yours before they send something.

Who is accountable for accuracy? The answer should be the person who sends it, stated in those words. These tools produce confident, well-formatted, incorrect output — invented citations, plausible figures, misremembered contract terms. Whoever puts their name on the work owns every claim in it.

What gets a second pair of eyes? Anything going to a client, anything with numbers in it, anything with legal or regulatory content. A sentence is enough.

Enforcement Only Works If You Can See It

A policy with no visibility is a statement of hope. You do not need to monitor keystrokes, but you should know which of these services your network is reaching and who is signed in to them. Most businesses already have the telemetry to answer that and have never run the report.

Blocking everything is the wrong instinct. It drives people to their phones, where you have no visibility at all and no business-tier contract protecting the data. Approve a good option, make it genuinely easy to get, watch for what else appears, and treat a tool that keeps showing up as a signal that your approved list has a gap rather than that your staff are delinquent.

Review the document quarterly. This is one of the few policies where an annual cycle is too slow — the tools change faster than that, and so does what your people are doing with them.

Policy Questions, Answered

How long should this document be?
Two to three pages. Longer and nobody reads it, which defeats the purpose. The approved tool list lives separately so it can change without reissuing the policy.

Do we need one if we have not approved any tools?
Especially then. A business with no approved tools and no policy is not a business without AI use; it is a business with unmonitored AI use. The policy is what converts that into a decision.

Should employees sign it?
Yes. Acknowledgement at onboarding and again at each material revision, recorded the same way you record your other handbook acknowledgements.

Can we just tell people not to put company data into these tools?
You can, and it will be ignored within a month, because the tools are useful and the rule offers no alternative. A workable policy names what may be used and for what, rather than issuing a prohibition that quietly becomes optional.

Our staff use the version built into software we already pay for. Does that count?
Yes, and it is the most commonly missed case. Features embedded in tools you already license still process your data and still belong on the approved list, with their settings reviewed rather than assumed — the assistant bundled into Microsoft 365 being the usual example.

Who should own this document internally?
Usually operations or HR, with IT supplying the tool list and the visibility. Assigning it to IT alone tends to produce a technical document that the people it governs do not read.

Want a Draft to Start From?

We write these for the businesses we support — the policy itself, the approved tool list, the settings that make the business-tier protections actually apply, and the reporting that shows what is being used. It usually takes a couple of conversations rather than a project.

Call (213) 873-7620 or book a free IT assessment and we will show you what your network says is already in use.

Related reading: CCPA Compliance in 2026 · Dark Web Monitoring for Business

The lease is signed. Somewhere between 30 and 120 days from now, your people need to walk into a space that works — phones ringing, files opening, printers found, calls connecting. IT is the workstream that quietly decides whether day one feels like a fresh start or a fire drill, and it is almost always the workstream that gets started last.

We have stood up and moved dozens of offices across California. The pattern almost never varies: the things that derail a move are ordered too late, and the things that get ordered first are the things nobody needed to rush. Here is the sequence we actually use, working backward from move-in day.

Order Your Circuits Before You Order Anything Else

This is the single most common way an office move goes wrong, and it is entirely avoidable.

Dedicated fiber routinely takes 45 to 90 days to install, and in older buildings it can run longer. If the building is not already lit by the carrier you want, you are waiting on construction, permits, and a landlord’s willingness to let someone open a riser. None of that compresses because your lease started.

• Order the primary circuit the week the lease is signed. Not after the floor plan is final. Not after the furniture is picked. That week.
• Order a second circuit from a different carrier on a different physical path. Two circuits from the same provider through the same riser is one circuit with extra billing.
• Get the install date in writing, then assume it slips. Have a bonded LTE or 5G failover ready to carry the office for the first few weeks. It is cheap insurance and you will reuse it as permanent failover.

What Only Your Landlord Can Tell You

Ask these before you finalize anything, because the answers move your timeline more than any decision you will make yourself:

• Where is the MPOE, and how do we get from there to our suite? The minimum point of entry is where carrier service physically lands in the building. The path from there to your space is yours to build, and it is sometimes not obvious.
• Which carriers are already lit here? An existing carrier can often turn service up in days instead of months.
• Who controls the telecom riser, and what does access cost? Some buildings require a specific vendor and charge accordingly. Budget for it now rather than discovering it in week six.
• What are the rules for after-hours work and freight elevator access? Cabling crews and equipment deliveries both depend on this, and both get scheduled weeks out.

Design the Network Before the Furniture Plan Is Locked

Cabling is poured concrete. Once walls close and furniture lands, changes cost three to four times what they would have cost on paper.

Access point placement, floor boxes, drop locations, and conference room cabling all depend on where people and walls will actually be. That means your network design and your space plan have to be built together, not in sequence. Get the drop count right the first time and add 20 percent — the cheapest cable you will ever run is the one pulled while the ceiling is already open.

A move is also the least expensive moment you will ever have to standardize hardware. Mismatched laptops, docks, and monitors accumulated over years get cleaned up in one purchase cycle, and every device after that is one you chose deliberately. If capital is tight, this is where a hardware-as-a-service arrangement earns its keep.

Conference Rooms Deserve Their Own Budget Line

Nothing burns goodwill faster than a room that cannot start a call while six people watch. Conference room AV gets treated as furniture and it is not — it is a networked system with cabling, power, display, audio, and a platform decision behind it.

Pick one platform. Deploy it identically in every room. A room that behaves differently from the room next door generates tickets forever, and the people filing them are usually your most senior.

A Move Is the Cleanest Security Reset You Will Ever Get

You are rebuilding the network anyway. That makes this the cheapest possible moment to fix the things that are hard to fix later:

• Enforce SSO and multi-factor authentication everywhere before day one. Rolling out identity controls during a move is one project. Rolling it out afterward is a change-management exercise with an audience.
• Enroll every device before it ships to the new office. A device that arrives already managed never has to be chased down at someone’s desk.
• Segment the building systems. Badge readers, cameras, thermostats, and visitor kiosks all live on your network now. They belong on their own VLAN, away from everything that matters.
• Retire what you are not taking with you. Old servers, old firewalls, and old accounts are easiest to decommission when they are physically in front of you in an empty room.

The Two Weeks Before, and the Weekend Itself

By this point the work is logistics rather than design:

• Test both circuits under real load, not with a speed test. A circuit that passes a speed test and fails at 40 concurrent video calls has not been tested.
• Confirm every static IP, firewall rule, and DNS record that points at the old location. This is where the surprises live.
• Label everything before it goes in a box. Photograph every rack and every cable run before you unplug it.
• Decide what happens if the new circuit is not live on move day, and write that plan down before you need it.
• Print a one-page day-one guide: Wi-Fi, printers, conference rooms, and who to call.

Then have IT physically on site for the first two days. The day-one ticket queue is a fact of life — the only question is whether someone is standing there to clear it in minutes or whether it sits in a queue for a week while people form opinions about the new office.

What This Actually Costs, and Who Should Do It

Most companies moving offices hit the same fork: assign it to whoever handles IT internally, or bring in a team that does this routinely.

The honest math is about frequency, not competence. Your internal person may be perfectly capable and will still be doing it for the first time in this building, learning its quirks on a deadline, while also keeping the current office running. A team that stands up offices regularly has already made the mistakes somewhere else. Under a few hundred people, a partner is usually both faster and cheaper — and the work is a few weeks rather than a few months.

Either way, start the circuits this week. Everything else on this list has slack in it. That one does not.

Questions We Get on Every Office Move

How far ahead should we start planning the IT side?
Ninety days is comfortable. Sixty is workable. Thirty means you are building the office around whatever connectivity you can get, rather than the other way around.

Can we keep our phone numbers?
Almost always, yes. Number porting takes two to four weeks and is one of the few items that genuinely cannot be rushed at the end, so start it early even though it feels minor.

What if the new circuit is not ready on move day?
This is common enough that it should be planned for rather than feared. A bonded wireless failover carries a normal office workload well enough to keep people working while you wait.

Do we need to re-cable if the space already has cabling?
Test it before you trust it. Existing cabling is frequently the previous tenant’s, of unknown category and unknown condition. Certification testing is inexpensive relative to discovering the problem after everyone has moved in.

Should we move our server, or is this the moment to go cloud?
A move is the natural decision point, because you are paying to relocate the hardware either way. If the equipment is more than three or four years old, the relocation cost is often better spent on migration.

Planning a Move?

We handle office standups and relocations for companies across Los Angeles, Orange County, and the Bay Area — circuits, cabling, network design, conference rooms, security, and someone standing in the new space on day one. It is included in our managed service, not billed as a separate project.

Call (213) 873-7620 or book a free IT assessment and we will walk the space with you.