If you have saved a shortlist, start with those service names. The action adds labels to empty candidates; enter each document reference, proposed window and commitment from the written SLA. Your required service, severity and window stay as entered.
The five SLA timers
Acknowledgement
StartAgreed intake event
StopAgreed acknowledgement returned
Define whether an automated acknowledgement counts.
Work start
StartAgreed actionable-ticket event
StopQualified investigation or action begins
Identify the actor and the first action that starts work.
Mitigation
StartAgreed incident-start event
StopImpact reduced or a workaround in place
Define the observable reduction in business impact.
Restore
StartAgreed incident-start event
StopService usable at the specified level
State the service condition that counts as restored.
Resolution
StartAgreed resolution-start event
StopAgreed resolution or closure criteria met
Identify the acceptance owner and the closure criteria.
The connectors show definitions, not elapsed durations. Replace the example start events with the agreed service clauses.
Copy each proposed target with its units and calendar. Define the start, stop and permitted pauses so an acknowledgement, first action and service restore remain separate commitments.
Read the completeness counts
The tool checks ten criteria: scope, severity, five timer definitions, pause rules, escalation, and reporting/remedies/exit terms. The clause statuses describe your document review:
- Written - the proposed document defines the criterion for the service you are comparing.
- Partial - the answer needs clarification or a timer lacks its target or measurement definition.
- Missing - the clause has not been supplied or checked.
A timer marked Written counts as Partial until both its target and measurement rule are entered. A complete document can still contain an unsuitable service commitment, so review the actual targets and responsibilities as well as the counts.
Compare the measurement before the number
| Proposed wording | What to clarify |
|---|---|
| Fast response | The target, start event and action that stops the timer |
| Response within a stated interval | Whether response means acknowledgement or useful work; elapsed or business time |
| Restore target with an approval hold | Who authorizes a pause, how it is logged and what restarts the timer |
| Same target under different calendars | Timezone, staffed hours, holidays and the authoritative ticket timestamps |
The tool preserves the text you enter. It does not convert business hours to elapsed time or infer that differently written targets are equivalent. Use the SLA guide's calendar example to settle those definitions. When reviewing a supplier's delivery percentage, check the request counts and severity split behind it.
Turn gaps into proposal questions
Open each candidate's question list in the report. Add the applicable agreement version, clause reference and service window. Ask for missing definitions in the same RFP before comparing written quotes.
Then sample the proposed workflow in a NOC pilot or help desk pilot. Document completeness and observed delivery answer different parts of the buying decision.
Keep your comparison
Use Keep this comparison for later to save a worksheet file and reopen your inputs. It includes drafts for all three candidates, even if fewer are currently selected. Opening a file restores the fields for review; build a fresh comparison before interpreting its completeness counts.
Use a blank Word SLA worksheet or Markdown SLA worksheet to keep the proposed targets, measurement rules and unanswered questions.
Copy the report, download it as Markdown or print just the comparison. Inputs stay in this tab and are not uploaded or saved automatically. Keep confidential client details in your approved systems and retain the original proposals alongside your notes.