Service Delivery and Account Operations

GCom Pro | Version 1.0 | October 5, 2026

Purpose

Turn delivery signals into clear decisions, accountable work and verifiable outcomes. This pack covers triage, service reviews, staffing decisions, change handoffs and account risk.

Use This Pack

Start with the metric definitions. Select the relevant SOP, record evidence in the mock operating log and verify the task in Source data. Supporting templates are included for escalation, service review, capacity and project economics.

Demonstration Boundary

Fictional portfolio demonstration. Roles, targets, records and examples are illustrative. No real ticket handling, customer communication, system changes or contractual service commitments are authorized by this playbook.

Current Capabilities

The MSP tab reports fictional tasks, statuses, workstreams, due dates, budgets and actual spend. It does not calculate contractual SLA performance, engineer utilization, account health, renewal revenue or project profit.

Document Control

Mock owner: Service Delivery Manager. Status: demonstration draft. Review quarterly and whenever fields, calculations or operating rules change. A reviewer should trace each metric to the source and record the review date before adoption.

Contents

Operating rhythm and roles • Dashboard metric dictionary • SOP 01 Ticket triage and escalation • SOP 02 Service-level review • SOP 03 Engineer capacity allocation • SOP 04 Project and change handoffs • SOP 05 Account risk and renewal review • Four working templates.

A mock human operating model; publishing this document does not enable new automations.

Daily Delivery Review

Service Delivery Manager checks freshness, Stuck tasks, overdue open work and missing fields. Select up to three priorities, assign accountable roles and record the next review. Due-date reviews require inspecting the source; the Needs attention card counts Stuck tasks only.

Weekly Service Review

Service Delivery Manager reviews delivery exceptions and budgets with the Technical Lead and Account Manager. Separate verified measures from proposed SLA, labor or commercial measures. Record decisions and follow-up dates.

Monthly Account Review

Account Manager reviews service evidence, sponsor concerns and renewal actions. Finance Reviewer validates any commercial calculations. No MSP account-health score or renewal forecast is generated by this dashboard.

Ownership

Service Analyst owns intake until handoff acceptance. Technical Lead owns technical assessment and staffing proposals. Change Owner owns scope, approvals and rollback evidence. Service Delivery Manager owns prioritization and escalations. Account Manager owns relationship follow-up. Data Steward owns reconciliation.

Operating Log

Record task reference, accountable role, evidence, decision, timestamp, next action and next review. Use a mock task update or separate exercise log for severity, approvals and timestamps: these are not dedicated MSP dashboard fields.

Demo Refresh Rules

Only approved DEMO | records are eligible. Maintain 20–30 unarchived tasks, at least six open and 2–4 labeled data-gap tasks. Never reopen Done work. Keep unknown values blank. Inspect cycle markers before retries, read back writes and retry failed publication without repeating successful changes. Browser polling is not a continuous event stream.

Definitions below describe the implemented MSP task dashboard.

Open Work and Completion

Open work = all DEMO | tasks minus Done tasks. Completion = Done / total tasks, rounded to a percentage. Active status grouping excludes Done and Stuck. Completion is task count based, not weighted by hours, budget or business value.

Needs Attention

Counts Stuck tasks. It does not include every overdue task, incident or at-risk client. The attention signal selects a Stuck task by due date, with undated work last.

Budget and Spend

Reported totals sum available values, with missing counts disclosed. Comparable utilization = matched spend / matched budget on rows containing both amounts. Remaining matched budget = matched budget minus matched spend. Neither represents margin or a forecast cost to complete. A missing amount is not zero; a zero denominator cannot establish utilization.

Workstream Charts

Progress shows Done / task count for the three largest workstreams by task count. Cost comparison shows the three largest workstreams by reported budget. Different chart selections and incomplete amounts can explain apparent differences.

Due-Date Distribution

Six weekly buckets begin with Monday of the current UTC week. Tasks are grouped by due date regardless of status, including Done. Undated and out-of-window tasks are excluded. This is neither a historical completion trend nor an engineer-capacity forecast.

Data Completeness

Checks Status, Workstream, Next Action, Due, Budget and Actual Spend. A filled field is not proof of accuracy or acceptance. Deliberate missing-field examples remain labeled and visible.

Proposed Capabilities

SLA attainment needs case timestamps and contractual clock rules. Capacity needs planned hours and availability. Margin needs revenue and a complete cost basis. Account risk and renewal reporting need account-level evidence and dates. The Customer Success account cohort is separate and is not MSP data.

Owner: Service Analyst; Service Delivery Manager accountable

Trigger

New fictional request, a changed impact or a blocked service task.

Inputs

Task history, impact evidence, service scope and an identified accountable role.

1. Check Duplicates and Scope

Find the existing DEMO | task. Reuse it if the same issue is still open. Record the affected fictional service, impact and evidence; no real customer data.

2. Classify the Impact

Use the escalation template. Record severity and rationale in the mock log. Do not infer severity from revenue or task budget.

3. Assign and Acknowledge

Record the receiving role, immediate next action and due date. Keep accountability with the sender until the receiving role accepts. Retain any customer acknowledgment as a mock draft.

4. Escalate Blockers

Use Stuck when a named dependency prevents progress; record its owner and next decision. For urgent impact, assign the mock incident lead and next update time.

5. Validate Resolution

Compare evidence with original acceptance criteria. Complete only after acceptance and all six required task fields are present. A workaround may leave follow-up work open.

Exception

If impact or timing is unknown, record the uncertainty and escalate for assessment. Never substitute a due date for a measured response timestamp.

Completion Evidence

Unique task reference, impact rationale, accepted owner, action/date and resolution evidence or an explicit open blocker.

Dashboard Connection

Status, open work, Stuck count and completeness; no measured response or resolution SLA.

Owner: Service Delivery Manager

Trigger

Weekly mock review or a reported missed commitment.

Inputs

Task source data, prior decisions and, if supplied, a separate mock case log and service agreement.

1. Confirm Freshness

Check source and as-of timestamp. Treat stale or fallback data as provisional and record the limitation.

2. Review Delivery Exceptions

Inspect Stuck and overdue open tasks, missing information and workstream progress. Distinguish blocked work from measured SLA breaches.

3. Validate Any SLA Calculation

Only with case-level evidence: define eligible cases, service hours, time zone, paused clock rules, target and exclusions. Preserve received, response and resolution timestamps.

4. Reconcile the Denominator

Calculate compliant eligible cases / eligible cases for the specified metric and period. Unknown evidence is unmeasurable, not compliant. Disclose coverage separately; zero eligible cases means not applicable.

5. Record Corrective Actions

Use the service review template. Assign owners and dates for recurring issues; verify actions at the next review without claiming a trend from a single snapshot.

Exception

Without the additional case records, report SLA performance as not measured. Do not label task completion or due-date compliance as contractual attainment.

Completion Evidence

Dated review with coverage, supported findings, decisions, assigned actions and next review date.

Dashboard Connection

Task progress and budget measures are implemented. Contractual SLA calculations are proposed and remain in the mock log.

Owner: Technical Lead; Service Delivery Manager approves priorities

Trigger

Weekly planning or an overload/dependency signal.

Inputs

Open work, priorities, skill requirements and a separately prepared capacity worksheet.

1. Establish Available Hours

For each mock role and week, record scheduled hours less leave, existing commitments and a stated contingency allowance. Do not subtract the same commitment twice.

2. Estimate Demand

Record remaining effort, required skills, dependencies and confidence per work item. A task count or budget is not an estimate of engineering hours.

3. Compare Demand and Capacity

Allocate by role and week. Planned load = allocated hours / net available hours. Zero availability with demand is a coverage gap; blank availability means unknown.

4. Resolve Over-Allocation

Propose moving work, changing sequence or assigning a suitably qualified mock role. Record the effect on dates and acceptance of the revised plan.

5. Update Delivery Records

Read back changed dates, status and next actions. Keep acceptance decisions and hours in the worksheet; do not imply that the task dashboard calculates labor utilization.

Exception

If estimates or calendars are missing, mark the plan provisional and obtain evidence. Urgent work displaces other work only through an explicit prioritization decision.

Completion Evidence

Balanced or explicitly escalated weekly plan with role, hours, dependencies, priority decision and review date.

Dashboard Connection

Due-date distribution supports scheduling discussion only. Planned load and actual billable utilization require additional records.

Owner: Change Owner with Technical Lead acceptance

Trigger

A deliverable moves between roles or a fictional change reaches a decision gate.

Inputs

Scope, acceptance criteria, dependencies, budget/spend and a mock change record.

1. Define Readiness

Document scope, affected fictional services, proposed window, acceptance criteria, owner and receiving role. Identify unresolved dependencies.

2. Review Cost and Risk

Inspect paired budget/spend and missing amounts. Estimate remaining cost separately if possible. Record risk, contingency and approval authority in the mock log.

3. Prepare the Handoff

Include validation steps, mock rollback plan, decision checkpoints and communication draft. Any real production action is outside this demonstration.

4. Accept or Reject Readiness

Receiving role acknowledges ownership. Missing critical evidence blocks the handoff; preserve the blocker and next action rather than marking Done.

5. Validate and Close

Record simulated test results and acceptance. Reconcile spend with evidence, keep follow-ups owned and mark Done only when required fields and completion evidence are present.

Exception

Unapproved scope or absent rollback evidence keeps a change pending. Missing spend remains unknown; remaining budget does not prove sufficient funding.

Completion Evidence

Accepted handoff, recorded approval decision, mock validation/rollback evidence, reconciled costs and owned residual actions.

Dashboard Connection

Project status and budget comparison are implemented. Forecast-to-complete and profit require the separate economics worksheet.

Owner: Account Manager; Finance Reviewer for commercial decisions

Trigger

Monthly mock review or a service concern with potential relationship impact.

Inputs

Linked task evidence plus a separate fictional account record with renewal timing and commercial context.

1. Establish the Account Record

Record fictional account reference, owner, renewal date and evidence date. Missing renewal timing is unknown; never borrow dates from the Customer Success cohort.

2. Assess Evidence

Review unresolved service issues, delivery commitments, sponsor feedback and value evidence. Describe risks and hypotheses separately; a Stuck task is not an account-health score.

3. Create the Recovery Action

Assign a specific outcome, accountable role and review date. Link the existing task and define acceptance evidence.

4. Review Renewal Readiness

Validate the contract timeline and outstanding issues. Record a mock next step. Treat proposed expansion as an opportunity, not committed revenue or a guaranteed result.

5. Confirm the Outcome

Review recovery evidence and record any mock commercial decision with explicit approval. Preserve history and verify source task updates; do not invent account-level financial changes.

Exception

Without account and contract evidence, describe the risk qualitatively and keep renewal value unmeasured. Growth depends on customer needs, execution, pricing, retention, market conditions and other factors.

Completion Evidence

Dated account review with evidence, unknowns, owner, recovery outcome, renewal next step and review date.

Dashboard Connection

Supports Client Health and Renewals workstreams as task categories. MSP health scores, ARR and renewal forecasts are not implemented.

Copy these structures into a mock operating log. Targets below are illustrative, not contractual.

Escalation Matrix

P1: widespread critical service loss with no workaround → mock incident lead; immediate triage, proposed updates every 30 minutes. P2: significant degradation or limited workaround → Technical Lead; proposed hourly updates. P3: limited impact → Service Analyst; next business-day review. P4: planned request → backlog owner; agree a date. Record severity rationale and agreed cadence for each case.

Escalation Record

Case/task reference: ____ | Impact and evidence: ____ | Severity/rationale: ____ | Accountable role: ____ | Received timestamp/time zone: ____ | Next update: ____ | Dependency owner: ____ | Decision/approval: ____ | Acceptance evidence: ____

Service Review Agenda

Period and snapshot timestamp → prior actions → blocked/overdue work → missing evidence → budget exceptions → supported service measures → decisions and owners → next review.

Service Review Record

Review date/owner: ____ | Source and freshness: ____ | Metric/definition: ____ | Eligible population: ____ | Measured records: ____ | Unknown/excluded records and reasons: ____ | Finding: ____ | Action/owner/due: ____ | Decision evidence: ____

Illustrative SLA Calculation

A mock log contains 20 eligible cases: 16 measured on time, 2 measured late, 2 with missing evidence. Measured attainment = 16/18 = 88.9%; evidence coverage = 18/20 = 90%. Do not count unknown cases as compliant. If a contract requires another denominator, document and follow that rule instead. This calculation is not a dashboard feature.

Additional records are needed for these worksheets; all worked values below are fictional.

Capacity Worksheet

Week: ____ | Role/skills: ____ | Scheduled hours: ____ | Leave: ____ | Existing commitments: ____ | Contingency: ____ | Net available: ____ | Proposed allocation: ____ | Load: ____ | Displaced work/approval: ____ | Review date: ____

Capacity Example

40 scheduled − 8 leave − 6 existing commitments − 4 contingency = 22 net available hours. Proposed new allocations of 26 hours imply 118.2% planned load and a 4-hour gap. Move or reassign four hours through an approved mock decision. This is planned load, not actual billable utilization.

Project Economics Worksheet

Project/task: ____ | Period and cost basis: ____ | Approved budget: ____ | Actual cost to date: ____ | Estimated remaining cost: ____ | Forecast total cost: ____ | Approved project revenue: ____ | Forecast margin: ____ | Missing evidence: ____ | Decision/owner: ____

Economics Example

Budget $30,000; actual cost $18,000; remaining estimate $8,000; approved revenue $40,000. Forecast cost = $26,000; forecast budget headroom = $4,000; forecast margin = ($40,000 − $26,000)/$40,000 = 35%. Actual remaining budget of $12,000 is a different measure. The example assumes a complete and consistent cost basis; dashboard spend alone does not establish it.

Unknowns and Controls

If revenue or cost evidence is missing, leave margin uncalculated. Zero revenue has no meaningful margin percentage. Avoid double-counting labor, vendor charges or commitments. Record period, assumptions and reviewer; forecast results are estimates, not promises.

Logic Review Checklist

Confirm chart label and formula → identify required source fields → test one complete example → test one missing-value example → check denominators and date boundaries → reconcile source/readback → record reviewer and document version. Treat any proposed measure as unimplemented until its data model and calculations are verified.