Documentation · Getting started

Preparing an IT project

What to include in your brief, how to set priorities and what a first technical proposal should establish.

Updated:

Start with the outcome

Describe what currently limits the business and what should work better afterwards. A useful brief can be short: more reliable connectivity, manageable IT or an application that removes manual work. The technical approach follows the context.

  • Identify users, locations and the most important systems.
  • Provide timing, an indicative budget and operating constraints.

Prepare environment information

A device list, a simple diagram and information about applications and existing providers help. If documentation is unavailable, describe what you know; the initial assessment scope can then be agreed.

  • Do not submit passwords, private keys or complete personal-data exports through the form.
  • Access and sensitive materials are transferred through an agreed secure channel.

From proposal to verifiable handover

A proposal should identify scope, dependencies, price or pricing approach, tests and continuing operation. Changes are approved so everyone understands the deliverables and how functionality is accepted.

  • Assign a project owner and change approvers.
  • Availability and support requirements are confirmed explicitly.

Documentation explains principles, preparation and technical decisions. Exact parameters, available capabilities, deliverables and support are confirmed for your deployment; binding terms are set out in the proposal, agreement and Legal section.