How IT services work
Seven stages, from first enquiry to follow-up review
A clear process protects both sides. Each stage sets out what the client provides, what NetixSky Services reviews, what gets confirmed, and why the stage matters at all.
- Written at every stage Scope, assumptions and dependencies recorded, not just discussed.
- Access by agreement Access level, authorisation and removal confirmed before work starts.
- No implied guarantees Outcome limitations stated at the point they become relevant.
Before stage one
What this process is designed to avoid
NetixSky Services Ltd supports IT service enquiries shaped around current systems, cloud platforms, network requirements, user needs, access permissions, supplier arrangements, support scope, and agreed service terms.
Problems this prevents
- Work carried out before the environment is properly understood
- Scope that grows without anyone agreeing to it
- Administrative access granted informally and never reviewed
- Recommendations that a licence tier does not actually permit
- Supplier dependencies discovered halfway through delivery
- Configuration knowledge held by one person only
What the client always keeps
- A written scope covering inclusions, exclusions and assumptions
- A record of access granted, by whom, and its removal position
- Documentation of systems, suppliers and configuration decisions
- A clear list of open risks and deferred items
- Direct ownership of their own platform accounts and licences
The seven stages
Each stage has an input, a review and a confirmed output
Stages can overlap and not every enquiry needs all seven. Where a stage is skipped, that is a decision recorded in the scope rather than an omission.
- 01
Submit IT Services Enquiry
- Client provides
- A short description of the business, the systems in use, and the IT, cloud, network or operational issue you want support with.
- NetixSky reviews
- Whether the enquiry sits within the IT services, cloud support, network, systems administration, digital operations, review or planning areas NetixSky Services works across.
- Confirmed at this stage
- That the enquiry has been received, and what additional context is needed before anything is discussed in detail.
Why it matters Starting from a written description keeps the conversation grounded in the actual problem rather than assumptions about it.
- 02
Share Current Systems, Users and Requirements
- Client provides
- Details of users, devices, email and file platforms, business software, approximate user numbers, and what needs to change or improve.
- NetixSky reviews
- How the systems relate to each other, where the dependencies sit, and which areas are likely to influence any recommendation.
- Confirmed at this stage
- A shared written picture of the current environment, including anything still unknown or awaiting information.
Why it matters Recommendations are only as reliable as the information behind them. Gaps are recorded rather than filled with guesses.
- 03
Review Cloud, Network, Devices and Supplier Context
- Client provides
- Cloud platforms and licence types in use, internet provider details, network equipment, hardware suppliers and any existing IT arrangements.
- NetixSky reviews
- Platform limitations, licence implications, network dependencies, supplier boundaries and where third-party terms will shape what is possible.
- Confirmed at this stage
- Which parts of the environment NetixSky Services can support directly, and which depend on a third party.
Why it matters Cloud providers, internet providers and software vendors set their own rules, service levels and availability. Those boundaries need to be visible from the start.
- 04
Confirm Scope, Access, Security and Responsibilities
- Client provides
- Confirmation of who can authorise access, what security requirements apply, how data should be handled, and which approvals are needed.
- NetixSky reviews
- What access is genuinely required for the agreed work, what can be done without elevated access, and what responsibilities sit on each side.
- Confirmed at this stage
- A written scope covering the work included, the work excluded, access arrangements, security expectations and responsibilities.
Why it matters Clear scope and access boundaries protect the business, keep expectations realistic and avoid assumptions about who is responsible for what.
- 05
Plan Support, Configuration or Improvement Work
- Client provides
- Preferred timing, operational constraints, quiet periods, change-approval requirements and budget guidance.
- NetixSky reviews
- Sequencing, dependencies, risk points, rollback considerations and anything that needs a supplier or provider before it can proceed.
- Confirmed at this stage
- A practical plan with an order of work, dependencies, known risks and indicative timings.
Why it matters IT changes affect people who are trying to do their jobs. Planning around the business reduces disruption and surprises.
- 06
Deliver Agreed Support and Documentation
- Client provides
- Timely access, on-site availability where needed, user feedback and sign-off at agreed checkpoints.
- NetixSky reviews
- Progress against the agreed scope, issues that emerge during the work, and anything that changes the original assumptions.
- Confirmed at this stage
- What was carried out, what was configured, what remains outstanding, and written documentation of the resulting setup.
Why it matters Documented work can be handed over, audited and picked up later. Undocumented work becomes a dependency on one individual.
- 07
Review Follow-Up, Risks and Future Improvements
- Client provides
- Feedback on how the setup is performing in real use, plus any new business plans that may affect IT.
- NetixSky reviews
- Remaining risks, deferred items, licence and supplier renewals, capacity pressure and areas worth planning for next.
- Confirmed at this stage
- An agreed list of follow-up items, open risks and possible next-stage priorities.
Why it matters IT environments change constantly. A short structured review keeps decisions deliberate instead of reactive.
Transparency
Nine things stated openly in every engagement
These are the areas where unstated assumptions cause the most damage, so each one is addressed explicitly.
-
Access permissions
What access is required, who authorises it, how it is granted and when it is removed. Sensitive credentials are never requested through public channels.
-
Current systems
What exists, how it is configured and which parts are unconfirmed. Gaps are recorded rather than filled with assumptions.
-
Licences
Licence entitlement determines what can actually be configured. Where a requirement needs a higher tier, that is stated up front.
-
Cloud platforms
Provider-controlled features, admin limits, retention behaviour and availability. No partner or reseller status is held or claimed.
-
Network setup
Physical constraints, equipment capability and internet provider performance, all of which shape what is achievable.
-
Suppliers
Existing providers, vendors and manufacturers with their own costs, lead times, service levels and contract requirements.
-
Security requirements
Practical measures agreed openly, with no security guarantee, certification claim or incident-prevention promise.
-
Data handling
How business information should be handled during the work, agreed in advance and documented alongside the scope.
-
Support boundaries
What is inside the agreed scope, what sits outside it, and how out-of-scope requests are handled.
No guaranteed outcomes
The limits that apply across every stage
These notes appear throughout the site because they apply throughout the work, not only at the point of contract.
Client responsibility
Client responsibility includes providing accurate system information, access permissions, supplier details, licensing information, data handling instructions, security requirements, user feedback, approvals, and timely communication.
Legal, data protection, cybersecurity, insurance, procurement, employment, sector-specific, and regulatory requirements should be reviewed with appropriate specialists where required.
Stage one
Start at stage one with a written IT services enquiry
Describe the business, the systems in use and the difficulty you want addressed. Everything after that follows the process above.
- No payment details are collected through this website.
- Passwords, credentials, API keys and private keys should never be sent through a public form.
- Support is subject to agreed scope, confirmed in writing before work begins.