Skip to content

Public sample

Illustrative sample — not a customer assessment

This page shows the shape of an environment assessment deliverable. Bracketed fields are placeholders for a real engagement. Final findings and service targets are developed for your environment.

Download sample PDF Book a discovery call Assessment overview
Illustrative sample — not a customer assessment. Final findings and service targets are developed for your environment. Assessment scope and fee are agreed before work starts. Response times remain TBD until mutual approval.

Cover

Prepared for
[Client / Company Name]
Prepared by
Mazden Tech
Assessment date
[Date]
Sites in scope
[City / site list — confirmed during discovery]
Users / devices (approx.)
[# users] · [# devices]

1. Systems / applications register

Lean inventory of in-scope systems. Access verification records named custodians only — no passwords, MFA codes, or secrets are collected on this worksheet.

Illustrative systems register (blank / generic placeholders)
System / app Tech admin Business owner Criticality Key dependencies
[e.g. Illustrative — Identity / email][Name / role][Name / role][Critical][Identity · network · upstream]
[e.g. Illustrative — Line-of-business app][Name / role][Name / role][Important][Depends on…]
[System name][Name / role][Name / role][Standard][Dependencies]
[System name][Name / role][Name / role][Convenience][Dependencies]

Suggested criticality labels (confirm during assessment): Critical · Important · Standard · Convenience.

2. Prioritized findings (illustrative structure)

Issue priority list — blank sample rows
Priority Finding Affected systems / process Suggested next step
P1[Finding title][System / process][Stabilize / project / vendor]
P2[Finding title][System / process][Stabilize / project / vendor]
P3[Finding title][System / process][Stabilize / project / vendor]

3. Proposed severity framework

Definitions below are proposed for workshop confirmation. They are a design input — not an active service promise until approved in writing. Numeric acknowledgement, update, and restoration targets stay [TBD / agreed].

Sev1

Critical business process down with no workable workaround, or a broad outage of a core service.

Sev2

Material multi-user degradation with only a partial workaround.

Sev3

Limited user or function impairment; business continues with an acceptable workaround.

Sev4

Service requests, how-to questions, and planned changes.

Response design columns — targets to agree (not published guarantees)
Severity Coverage hours Ack / initial response Update cadence Workaround / restore Full resolution
Sev1[TBD / agreed][TBD / agreed][TBD / agreed][TBD / agreed][TBD / agreed]
Sev2[TBD / agreed][TBD / agreed][TBD / agreed][TBD / agreed][TBD / agreed]
Sev3[TBD / agreed][TBD / agreed][TBD / agreed][TBD / agreed][TBD / agreed]
Sev4[TBD / agreed][TBD / agreed][TBD / agreed]N/A[TBD / agreed]

Business recovery goals — recovery time objective (RTO: how quickly a system should be usable again) and recovery point objective (RPO: how much data loss is acceptable) — are recorded separately from provider response commitments. Security incidents follow an agreed incident-response path. Third-party restore outcomes depend on the upstream vendor.

4. Suggested next steps

  1. Customer reviews register, findings, and proposed severity definitions.
  2. Agree numeric targets and coverage hours in writing (or defer items).
  3. Confirm onboarding phases: inventory → access verification → stabilize → ongoing scope.
  4. Proceed to Managed IT commercial terms only after mutual approval.
Start with a discovery call Download this sample as PDF Back to services