← Knowledge Hub

Vantablack practical guide

Read a use case as a decision, not a promise

Understand the decision, identify what can change the route and prepare the right questions for your setup.

VANTABLACK / THE CONNECTED ROUTE

Use the case to understand the decision.

Follow the numbered route
Select a checkpoint for detail
  1. 01Read the operating modelView checkpoint

    Business facts and scope to clarify

  2. 02Find the real constraintView checkpoint

    Sources, evidence and open questions

  3. 03Compare the optionsView checkpoint

    Required records and responsibilities

  4. 04Separate evidence from outcomeView checkpoint

    Evidence, review and unresolved gaps

  5. 05Apply the lesson to your scopeView checkpoint

    Written scope and acceptance

Overview of the guide below. Confirm the requirements for your exact scope; an overview is not an approval.

Open full-size topology ↗
Read the steps
  1. Read the operating model — Business facts and scope to clarify
  2. Find the real constraint — Sources, evidence and open questions
  3. Compare the options — Required records and responsibilities
  4. Separate evidence from outcome — Evidence, review and unresolved gaps
  5. Apply the lesson to your scope — Written scope and acceptance
01 / Decision point

Start with the client’s operating model

Ask what the client wanted to do and which assumption made the request difficult.

The interesting issue is often who delivered the service, where it happened or what a regulator required.

02 / Decision point

Follow the causal chain

A useful case explains the constraint, the alternatives considered and why a route fitted the recorded facts. A licence name without that reasoning does not tell you whether the same solution suits your company.

03 / Decision point

Separate analysis from results

An investigated route is not proof that a licence was issued. A historical result is not a future guarantee. Use the case to prepare better questions for a fresh assessment, including what would change the recommendation.

Your next step

Bring the business model to the conversation.

Tell us what you will sell, who your customers are, who delivers the work and where you will operate. We use these details to check requirements with the relevant authority before preparing a proposal for your business.

Setup Assistant
Apply this to your business

How should I evaluate a setup recommendation?

Why this matters

A sound recommendation explains permitted activities, the benefits and limits of each option, and the requirements still to be verified.

What could change the answer?

Recommendations should reflect changes in your business requirements rather than remain tied to a fixed package.

Check these details first

  • The facts used to reach the recommendation
  • Alternatives and reasons for the shortlist
  • Written scope, costs and responsibilities
  • The conditions that would change the answer

Choose your next step

Get support