# Lead-response review worksheet

RevSet Labs · Updated September 27, 2026
Guide: https://revsetlabs.com/resources/speed-to-lead/

Purpose: identify whether first replies move actual inquiries forward. This worksheet is not a conversion forecast or an industry benchmark.

## Define the review

- Channel:
- Arrival-date range:
- Office timezone and staffed hours:
- Reviewer:
- Selected cohort: ten consecutive inquiries, including unresolved ones.
- What counts as a useful response for this inquiry type:

## Repeat for each inquiry

Use anonymized identifiers; do not publish customer messages or private contact details.

- Record ID:
- What the customer needs:
- Details already supplied:
- Original arrival timestamp:
- Integration receipt timestamp:
- Acknowledgement delivered timestamp (or unknown/failed):
- First useful response timestamp (or unresolved/unknown):
- Question answered or useful question asked:
- Owner and next action:
- Unsupported promise? Explain:
- Duplicate or unnecessary message? Explain:
- Booking status: offered / confirmed / not applicable / unknown:

## Calculate without hiding missing records

- Acknowledgement time = delivered acknowledgement minus original arrival.
- Useful-response time = first useful response minus original arrival.
- Integration delay = system receipt minus original arrival.
- Preserve unknown timestamps as unknown; do not substitute zero.
- Report the full cohort size, answered count, unresolved count, and failures.
- Label seconds/minutes consistently. Do not compare differently defined clocks.

## Choose one improvement

- Repeated gap:
- Proposed rule or message change:
- Human owner:
- Acceptance test:
- Next comparable cohort to review:
- Actual observation after the change:

A ten-inquiry sample can surface problems but cannot establish a reliable revenue or conversion uplift. Keep those claims separate from observed workflow behavior.