# Meraki project brief

Configlane · Editable discussion template · 10 September 2026

This template supports an initial assessment. Estimates and open questions are
enough. It is not a quotation or a service commitment. Do not include passwords,
API keys, serial-number inventories or confidential network plans. Access is
established later through an agreed secure handover process.

## 1. Starting point

- Business / role (internal IT, management or IT service provider):
- Single site, campus or distributed sites:
- Approximate site and device count:
- Existing Meraki estate or new deployment:
- Current owner of dashboard access and operations:

## 2. Required engagement

- Design / rollout / wireless / SD-WAN / takeover / ongoing operations:
- What should improve for users?
- Which responsibilities stay with internal IT or your service provider?
- Critical applications and typical devices:
- Guest access, specialist systems or existing authentication:

## 3. Prerequisites and timing

- Preferred start and possible maintenance windows:
- Circuits, cabling and on-site contacts available?
- Next licence renewal or current support contract end date:
- Known incidents, documentation gaps or unresolved dependencies:
- Ownership, organisation control and authorised handover established?

## 4. Ongoing support

- Required service hours and escalation contacts:
- Expected volume of recurring changes:
- Responsibility for circuits, vendor support and replacement hardware:
- Required reports, checks and documentation:
- Requirements for a future service exit or handover:

## 5. To agree together

- Outcome and scope of the first engagement:
- Acceptance criteria and evidence:
- Project work, hardware, licences and service fees shown separately:
- Excluded services and required preparation:
- Approval owners and next step:

Enquiry: https://www.configlane.io/en/kontakt?topic=meraki