Manage
Devices and workstations
A laptop that’s ready on day one, built like every other one in your firm, kept current from one place and watched so problems surface before your people notice.
Every device set up the same way. Then kept that way.
Your people notice a laptop that works: the software their work runs on, their files, the printer down the hall. What keeps it that way runs underneath. Every device in your firm is built from one documented baseline, so a model, a matter or a spreadsheet opens the same way at the desk, at home and on the road. Setup is done by tested scripts, not by hand, so nothing depends on one person remembering how it was done. Updates come from one place, and every device is watched centrally. The device list that results is your inventory: who has which machine, in which state.
What we set up
One build, every device, written down.
The baseline is decided with you once and documented. From then on every laptop and workstation follows it, in the office, at home, on the road and abroad.
-
One documented baseline
Operating system settings, the software your work runs on and the access rules, written down once. A new device is built from it, and a device that drifts from it is brought back.
-
By script, not by hand
Software, printers and settings are put in place by tested scripts that check before they change anything. Running one twice changes nothing. Every device is set up the same way, so nothing depends on who did it.
-
Tested before it touches your laptop
More than 150 test scenarios run across our scripts before one reaches a client. Then a dummy machine with your real setup, then a pilot group at your firm, and only then everyone. Nothing installs unless its fingerprint or its vendor’s signature checks out.
-
Software by role
Which software a device gets follows the team it belongs to: the structural team’s workstations get the CAD tools, the front office doesn’t. Adding a machine to a team is one change in a list.
-
Updates from one place
Operating systems and applications are kept current centrally, on every device. Every patch goes to the pilot group first, so a bad one is caught by a few people, not the whole firm.
-
Watched centrally
Every device reports in: its updates, its disk, its protection. Problems surface on our screens before your people notice, and a device that stops reporting is followed up.
By platform
Where the work differs.
Most devices follow the same build. CAD workstations are the exception, and they have their own page.
On record
In your documentation and the monthly report.
- Every laptop, workstation and server: who uses it, its build and its patch level
- The baseline, as it’s set, and the software catalogue by team
- What changed on which device, logged with the date
- Devices reaching the end of their life, ahead of next year’s budget
The same list feeds your evidence file, so the question “which devices do you manage, and are they current?” has an answer on the day it’s asked.
What usually goes wrong without it.
-
Every laptop set up differently
Built by hand, from memory, by whoever had time that day. Six months later no two machines are alike, and the one that works is the one nobody dares to touch.
-
The device nobody enrolled
A conference-room PC or a spare laptop that never made it into management gets no updates and no monitoring, for years. Nobody notices until someone sits down at it on deadline day.
-
Updates that wait for a quiet moment
Rolled out by hand when someone has time, which on a busy floor is never. The gap between a fix being published and being installed is where attacks land.
Also under Manage
- Service desk Every request lands with an engineer who can fix it, and stays with them until it’s fixed.
- Microsoft 365 Accounts, licences, Teams, SharePoint and Entra ID, administered in your own tenant.
- Joiners and leavers The right access on day one, gone on the last day, by script, so nothing is forgotten.
- Printers and plotters Office printers and large-format plotters deployed straight to the devices that need them.
- Licences and vendors Microsoft licences sized to your people, and one call for every vendor your IT depends on.
- The first 30 days Access secured, what we find documented, every system on the monitoring, then a welcome review.
Questions we get
Do you look after CAD and BIM workstations too?
Yes. They follow the same baseline where they can and get their own rules where they can’t: the software your projects depend on, such as Revit, AutoCAD, iTWO and Bluebeam, licence servers and the drivers it all runs on. The CAD workstations page says how.
What about working from home or from a site office?
The same build, the same access rules and the same monitoring wherever your people work, so a file opens the same way at the desk and in a site container. A private laptop gets as far as the sign-in page, and no further.
Do we have to buy devices through you?
No. A device bought through us arrives set up from your baseline; one you buy yourself is set up the same way, by time from the price list. Both ways are fine with us.
What happens when a laptop breaks?
Your people’s files live in your own Microsoft 365 tenant, not on the machine, and every device is built from the same baseline by script. So a replacement is set up the same way, and work carries on from the files where they were.
Start
How many of your devices would you vouch for today?
In a first call we go through how your devices are set up and updated today, which ones nobody is sure about, and what one documented build would change for your firm.
- No first level
- No surprises
- Pilot before you buy