Support and maintenance planning guide

Annual effort baseline

Use the role matrix to define annual person-days for each support role. Year 1 normally carries higher effort because teams complete knowledge transfer, stabilize production support, tune monitoring, close inherited backlog, and establish the first governance cycle.

SLA sizing logic

The estimator links the selected SLA model with incident capacity, change capacity, QA coverage, DevOps coverage, security maintenance, support scope, and evidence readiness. Higher SLA models require more mature support coverage and stronger evidence.

Cost forecasting method

Role-wise costs are calculated from annual person-days and daily rates. Annual escalation and contingency are applied to produce a proposal-ready forecast for five, seven, or ten years.

Governance evidence

Support plans should be backed by an SLA, RACI matrix, escalation matrix, monitoring plan, backup plan, patching plan, release plan, knowledge transfer plan, and monthly service reporting cadence.