CLOUDEK · ENQUIRY GUIDE

A defined project
with explicit change control.

This page explains topics for discussing a time-bounded infrastructure project or modernization. It is not a project offer or promise of delivery. Scope, dependencies, commercial terms and authorization must be agreed in writing before work.

Enquiry only. No fee, timeline, migration, deployment, capacity or outcome is established here. A recommendation or assessment does not authorize implementation.

✓ Named systems and exclusions✓ Approved change record✓ Acceptance evidence defined
01PROJECT BASELINE

Define the objective

State the intended outcome, in-scope systems and environments, exclusions, prerequisites, customer dependencies, milestones, deliverables and objective acceptance evidence. Identify named technical and business owners.

02CHANGE CONTROL

Approve each implementation

Every production change needs a separate authorized change record with the exact action and affected systems, implementation window, prerequisites, impact, stop conditions, rollback plan and post-change verification. Out-of-scope work requires an agreed change to the project scope.

Before any project work

  1. Confirm customer authority, decision makers, technical owners and environment boundaries.
  2. Accept the project scope, exclusions, dependency owners, milestones, fees, tax/payment/cancellation terms and dates in writing.
  3. Agree access, evidence exchange, retention, deletion, and handling of any third-party dependencies.
  4. Approve the specific change, window, rollback or stop conditions and acceptance evidence before implementation.
No implied authorization

This guide is not a quote, booking, contract, change request, security promise, acceptance record, customer authorization or evidence of available delivery capacity. It does not authorize access, migration, deployment or changes. Do not share credentials, customer exports or diagnostic data until an approved channel and written scope are in place.