HOW WE WORK
The problem is where the conversation starts.
A new starter is a good way to show how we work, because the laptop is only one part of it. We find out what the person needs and work out which parts depend on each other. Then we hand each part to whoever actually controls it, and check the result on their own desk.A new employee arrives and the laptop isn't the whole job.
A computer can be ready while the person using it still can't work. Their account, licence, files, applications, security settings and outside systems each depend on different decisions. Any one of them can hold up the whole result.
- 01What looks ready
The computer starts and the employee can sign in.
- 02What has to connect
Email, files, applications, permissions and security controls.
- 03What may sit elsewhere
Access owned by a client approver, software vendor or other provider.
Tell us what you can see. That's enough to start.
A new employee may be able to sign in while Outlook keeps asking for a password, a shared folder is missing or an application refuses access. We don't expect the person reporting it to diagnose which account, licence or permission sits behind those symptoms.
We begin with what changed, who is affected and what they need to do. Then we look for the connection between the visible problems. Two symptoms with one dependency behind them are different work from two unrelated faults.
The visible problem is evidence. It isn't necessarily the whole explanation.
One outcome can contain several jobs and several owners.
A copied account can miss access the new role needs or carry access it shouldn't have. A licence can exist without its services being ready. MFA can be switched on without anyone having finished setting it up. An outside application can need a login only its supplier can create.
We separate those parts before changing anything. We say what we'll handle, what needs approval from you, what belongs to another provider and how the finished work will be checked.
- What we handle: agreed licensing, permissions, applications and security setup.
- What we need from you: decisions such as who should approve access for the role.
- What another provider owns: supplier accounts, services or approvals only they can provide.
- How we check it: from the employee's working device, using the access they need.
The order is part of the work.
We deal with the dependencies in an order that avoids creating misleading failures. Identity and licensing come before the applications that depend on them. Permissions come before anyone expects folders to appear. Security registration happens while the person can confirm it themselves.
We also check inherited access instead of assuming the previous role is a safe template. Copying an account can be a useful starting point, but it isn't an access decision.
We won't skip an approval, a supplier's setup or a security check just to hit a date. If another provider owns a dependency, we raise it early with the right provider, and tell you before any coordination time is charged.
Working means working where the job is done.
We check the result from the employee's device and account, not only from an administration screen. That means opening the files and applications the role needs and confirming email and security prompts. It also means making sure new work is being saved somewhere that's actually protected.
We then separate what's complete from what's still open. Every unresolved item gets an owner and a next step. A ticket being closed isn't evidence that the person can do their job.
Trust grows when the difficult part is explained as clearly as the easy part.
Different needs call for different shapes of support.
Onboarding may be one piece of managed support, a defined project, prepaid support or a one-off request. The arrangement doesn't change the method: understand the need, map the dependencies, agree the work, check the result and state what remains.
Remote support is our main delivery method, with onsite assistance where agreed and practical. Our business hours are Monday to Friday, 8:00 am to 6:00 pm, Sydney time. Weekends and public holidays by appointment, arranged in advance. If you need cover outside these hours, we can build it into your support agreement. Without that, we'll still help in the evenings when we can, but we can't guarantee it.
A date doesn't make every dependency ours.
If access, a connection or a provider approval belongs to somebody else, we name it and raise it early with the right provider. We tell you before any coordination time is charged, and we won't call onboarding complete while that dependency is unresolved.