GENIUS
IT SOLUTIONS LIMITED

IT enquiry guide

Define the need.
Explore the next step.

Six areas to help frame an IT and technology enquiry.

Requirements before solutions

Prepare the information that matters.

These topics describe enquiry areas for discussion. Service availability, products, technical suitability and delivery arrangements are subject to confirmation.

01

Understand the environment

IT requirements & planning

Begin with the tasks your technology needs to support. A clear overview helps identify the scope of the question before possible approaches are considered.

  • Describe the users, locations and workflows involved.
  • Identify the systems relevant to the requirement.
  • Explain the desired outcome, priorities and constraints.
02

Review the equipment

Hardware & workplace technology enquiries

Equipment enquiries should connect specifications to intended use. Supply options, compatibility and availability need confirmation for the particular requirement.

  • State the intended workload, quantity and required specifications.
  • Identify existing peripherals and compatibility needs.
  • Clarify installation, licensing and warranty questions before purchasing.
03

Connect the workplace

Network & connectivity discussions

A connectivity enquiry needs context about the environment and the behaviour being observed. Avoid sending passwords or network credentials in the initial message.

  • Describe the affected locations, devices and connections.
  • Explain whether the issue is intermittent or continuous.
  • Identify existing equipment and any restrictions on changes.
04

Consider the applications

Software & digital workflow enquiries

A software discussion starts with what users need to do. Describe the current process and where a proposed change should make a difference.

  • Identify applications, versions and relevant integrations where known.
  • Explain the tasks or information flows involved.
  • Discuss licensing, access, testing and ownership requirements.
05

Prepare the review

Troubleshooting & support enquiries

A concise account of a technical issue helps define the next questions. Availability, response arrangements and any support commitment require separate confirmation.

  • Describe the symptoms and when they began.
  • Provide relevant error text with sensitive information removed.
  • Explain the impact and any steps already taken.
06

Agree the change

Implementation & handover requirements

Before work begins, make the scope and responsibilities understandable. Change planning should account for access, dependencies and how the result will be reviewed.

  • Confirm deliverables, exclusions and approval points.
  • Discuss maintenance windows, backup responsibilities and any rollback needs.
  • Agree acceptance, documentation and any ongoing support separately.

Ready to discuss?

Send the context, not your credentials.

Include a summary of the requirement and relevant system information. Remove passwords, access tokens and personal data from screenshots or error messages before sharing.

Contact GENIUS