Person & role
Start with what the person does, where they work and what they need to reach.
Business IT
When device setup, accounts, applications and access are handled differently each time, people lose hours before they can work. Kritical gives joiners, movers and leavers a clear, repeatable workplace setup and support path, with the dependencies made visible before the start date arrives.
On this page
Jump to the part that matches the problem or decision in front of you.
A repeatable process beats a scramble every time someone joins or leaves.
Accounts, licences and access get sorted reactively instead of before the first day.
Nobody has a checklist, so offboarding depends on someone remembering to do it.
Two people in the same role end up with different software, different access, and different problems down the track.
A repeatable checklist your team can run without reinventing it each time.
Device, accounts, shared resources and access approvals identified against the role, location and applications involved.
Configuration, updates, application installation and enrolment in the agreed management service, checked for compatibility before deployment.
Files transferred, sign-in assistance and an introduction to the tools they'll use, with timing agreed in advance.
Access, equipment, business information and linked services addressed with a documented retention and transfer plan.
We aim to provide continuity through a consistent lead or delivery group where the agreed scope and service model support it. Your proposal sets out the contact model, cover and handover arrangements that apply.
Tell us your current onboarding process and timeline, and we'll quote against it directly.
So you know exactly what a new starter costs to onboard, versus what ongoing management costs afterwards.
Cost depends on equipment availability, access approvals and application requirements for each role. Setup and deployment work is quoted as a one-off; ongoing support is a separate scope choice, so a workplace-setup quote never quietly becomes an unplanned managed-IT commitment.
Start with what the person does, where they work and what they need to reach.
Prepare a suitable device with the agreed operating system, security and applications.
Connect identity, collaboration, files and business systems with the right permissions.
Give the user a clear starting point and give support teams a useful record of the setup.
Tell us the start date, role and location as early as possible — notice period matters most for equipment and access approvals. We confirm the checklist, dependencies and a realistic preparation schedule. The first setups under the agreement establish the repeatable process your team can run for every future starter.
See the scoped price before you commit to anything.
Use these guides to see which technologies can help with the job in front of you.

Device selection, deployment and lifecycle planning for Apple in the workplace.

Apple device management, enrolment and administration, with the product and delivery scope agreed together.

Equipment specification and purchasing discussions covering configuration, availability and deployment requirements.
Yes. We assess existing equipment first, then confirm what can be prepared through the standard setup and what needs repair, replacement or extra work.
That depends on equipment availability, access approvals and application requirements. Tell us the start date early so dependencies and a realistic schedule can be confirmed.
Ongoing support is a separate scope choice. The quote explains the deployment handover, any agreed assistance period and the available continuing service arrangement.
Yes. We document one repeatable checklist and confirm what varies by location, and record the standard plus any approved site-specific variation.
Role changes get the same discipline as onboarding — access, applications and equipment reviewed against the new role, not left as-is by default.
Yes. We scope shipping, remote sign-in assistance and access approvals for a starter who's never coming into an office, alongside the same checklist used for an in-office setup.
Basic orientation to the tools they'll use is part of a practical handover. Deeper application-specific training is scoped separately where a role needs it.
Tell us what you want to achieve, what you have today and when it matters.