Separate response, arrival and resolution in HVAC service reporting

Get approved definitions before calculating

A commercial account may ask how quickly requests receive attention. Begin with the reporting owner’s actual definitions of receipt, response, arrival and resolution, including any approved clock boundaries. Record the definition version and timezone. AI can extract candidate events from authorized notes, but it should not invent a service standard or interpret an agreement.

Keep this reporting preparation distinct from contractual compliance. If business-hours rules, paused periods or event definitions are unclear, flag them for the responsible owner. Do not choose an industry-standard response target to complete a report that lacks its own approved rules.

Use a fictional same-day event trail

Under a deliberately simple elapsed-time example with no pauses, a request arrives at 9:00, an employee acknowledges it at 9:20, the technician arrives at 11:00 and the responsible person documents resolution at 13:30. The response interval is 20 minutes, arrival interval is two hours and resolution interval is four hours 30 minutes, each measured from receipt. These are example definitions, not benchmarks or promised service levels.

If the last entry only says technician departed, the resolution field stays unknown. If a timestamp has no timezone or the visit crosses a clock change, stop the calculation until the reporting owner clarifies the time basis. Preserve recorded time and normalized time separately so the reviewer can reconstruct any calculation.

Review event evidence and exclusions

Use one row per milestone with source record, timestamp, event meaning, uncertainty and reviewer. Ask the service manager to verify that the right event was selected, then check interval arithmetic independently. Report excluded or unresolved requests alongside the denominator; a fast average built only from convenient complete cases can hide gaps.

For an account conversation, state the reporting period, approved definitions and number of usable records. Avoid claiming compliance, causation or staff performance from a small incomplete sample. The assistant must not edit time records, close tickets or generate service credits. Pilot the ledger on known examples and measure event-classification errors before using it to support a customer discussion.

Release checklist

• Use supplied definitions and timezone.
• Keep acknowledgement, arrival and resolution separate.
• Show missing milestones and excluded records.
• Verify event choice and interval arithmetic.

Source context and limits

Jobber’s appointment documentation provides context for visit records. The milestone definitions and illustrative arithmetic here are our reporting method, not vendor promises, agreement interpretation or employee evaluation guidance.