bcom ICT runs service management practices based on ITIL 4, covering service desk, incident, request, problem and change management, service levels, configuration management and continual improvement. Royce Clark holds ITIL 4 Foundation certification. bcom ICT is not certified as an organisation against ITIL or ISO/IEC 20000-1.
Eight practices, and the question each one answers
Most providers put "ITIL-aligned" in the footer and leave it there. The reason it's worth more than that is that ITIL's practices map almost exactly onto the things clients worry about when choosing an IT provider — so here they are side by side.
| Practice | What you're really asking | How it works here |
|---|---|---|
| Service desk | Who do I call, and will a human answer? | One number and one email address, answered 8am to 5pm Monday to Friday. Outside those hours our digital assistant takes the details and logs the job for the next business day. Every request is logged, so nothing depends on someone remembering a corridor conversation. |
| Incident management | Something's broken. How fast do you come? | Faults are prioritised P1 to P4 by business impact and worked to published response targets. Restoring service comes first; understanding why comes after, as a separate piece of work. |
| Service request management | How do I get a new starter set up? | Requests are handled separately from faults, because mixing them means the new laptop request competes with the server being down. Requests are scheduled; faults are responded to. |
| Problem management | Will you fix the cause, or keep charging me for the same fault? | When a fault recurs, we open a problem record and chase the root cause. For managed clients that work is included — which is exactly the incentive difference between managed IT and break-fix. |
| Change enablement | Will you break something and disappear? | Changes that could disrupt your business are approved by you, scheduled, and have a documented backout plan before we start. High-risk work happens outside business hours. |
| Service level management | What have you actually committed to? | Response targets are published rather than negotiated privately, and reviewed with managed clients at their service reviews. |
| Configuration management | What happens to our documentation if we leave? | Every device, licence, credential and supplier is recorded in an asset register that belongs to you. You can request a copy at any time, not only on exit. |
| Continual improvement | Will anyone ever think about our IT strategically? | Managed clients get periodic service reviews covering what broke, what's ageing, what's coming out of support and what to budget for. IT that's only ever reactive gets expensive slowly. |
Keep it simple and practical
That's one of ITIL 4's own guiding principles, and it's the one that matters most for a business with eight staff. The full framework describes machinery for organisations far larger than yours or ours. Running all of it at your scale would cost you money and buy you meetings.
So we run the parts that change outcomes:
- Everything gets logged, so nothing lives only in someone's head
- Faults get prioritised by business impact, not by who shouted loudest
- Recurring problems get a root cause, not a repeat visit
- Nothing disruptive changes without your approval and a way back
- Your documentation is written down and belongs to you
- Someone looks at the whole picture periodically, not just the last ticket
We run the same disciplines a large IT department runs. We just run them at a size that suits a business with eight staff, and we explain them in English.
Where this is written down
Practices that only exist in conversation aren't practices. These are the pages where ours are set out in a form you can hold us to:
- Service levels — the P1 to P4 priority matrix, response targets, hours, escalation path and exit terms
- Onboarding — what happens in the first 30 days, including the documentation we build and hand to you
- ISO alignment — the standards behind these practices, and where we stop short of a certification claim
- Data handling — what we hold, where it lives and who can reach it
Royce Clark holds ITIL 4 Foundation certification. That is an individual credential — it does not make bcom ICT an ITIL-certified or ISO/IEC 20000-1-certified organisation, and we do not describe it that way.
Questions Gold Coast businesses ask us
Does bcom ICT follow ITIL?
bcom ICT's service management practices are based on ITIL 4, and Royce Clark holds ITIL 4 Foundation certification. bcom ICT is not certified as an organisation against ITIL or ISO/IEC 20000-1 — ITIL is a framework we work to, not a badge we've been audited for. Call 07 3041 8993.
Isn't ITIL overkill for a small business?
The full framework is, and we don't run it. ITIL 4's own guiding principle is 'keep it simple and practical', and that's the part we take seriously. What a small business actually needs from it is: requests get logged, faults get prioritised sensibly, recurring problems get chased, and nothing changes without warning. That's it. The rest is machinery for organisations far larger than yours or ours.
What's the difference between an incident and a request?
An incident is something broken — you had it, now you don't. A request is something new — a starter, a device, an access change. They're handled differently because they compete for the same people, and if they share a queue the new-laptop request will sit behind the outage or, worse, the other way around.
What is problem management, in plain terms?
Fixing incidents restores service. Problem management asks why it happened and stops it recurring. If your printer jams every Tuesday, incident management clears the jam each week and problem management finds out that a scheduled job is sending it a malformed file. Break-fix providers rarely do the second part, because they earn from the first.
How does change control work in practice?
For anything that could disrupt your business — a firewall change, a server update, a migration — we tell you what we're doing, agree a window, and have a way to reverse it before starting. Routine low-risk work like a patch on a single workstation doesn't need that ceremony, and pretending it does just slows everything down.
Do we get service reviews?
Managed clients do. They cover what broke and why, what's ageing or coming out of support, security posture, and what to budget for over the next twelve months. It's the difference between an IT provider and someone who answers the phone.
Want to see how this works on your systems?
The free review is where it starts — we look at what you're running and show you what we'd document, prioritise and fix first.