The study would test whether first touches rest on evidence or on a generic pitch.
Question and scope
This is a proposed research protocol, not a report of completed findings. It asks how often a first-touch note names the source and the trigger. The result would describe the note, not the rep's effort. A control that depends on memory is not yet a control.
The protocol does not measure whether the buyer replied. It measures whether the reason for contact was documented. Write the deadline as a date and a local time. If the source is unclear, route the question instead of guessing.
Population and unit of analysis
Define the population as first-touch notes created during a stated window. The unit is one note, with the source, the trigger, the buyer, and the message recorded. Keep the evidence with the record rather than in a separate log. Record the exception and the person who approved it.
Link the note to the account so the same touch is not counted twice. Write the deadline as a date and a local time. If the source is unclear, route the question instead of guessing. Review the first few notes together before the process expands.
Definitions and measures
Define source as a record that can be opened and checked. Define trigger as a specific change or event. Measure both separately. Record the exception and the person who approved it.
Report the source rate and the trigger rate. A note can name a source without explaining why it matters. Record the exception and the person who approved it. A short note with four fields is easier to use than a long narrative.
Evidence standard
Link each note to the source and the account record. A note that says the company is growing without a source is weak evidence. Review the first few notes together before the process expands. Keep the original note beside the corrected version.
Record the date the source was checked. A stale source may be wrong. Review the first few notes together before the process expands. Update the template when the same question appears twice.
Sampling and collection
Use a census of the notes if the volume is manageable. If sampling is necessary, stratify by segment and rep. Keep the evidence with the record rather than in a separate log. Ask whether a new reviewer could act on the record without a conversation.
Pilot the classification on a few notes and compare the reviewers. Clarify what counts as a trigger. Keep the evidence with the record rather than in a separate log. Review the first few notes together before the process expands.
Analysis and reporting
Report the source and trigger rates by segment and rep. Show the notes that had no source. Ask whether a new reviewer could act on the record without a conversation. If the source is unclear, route the question instead of guessing.
Present the results as a description of the note, not a judgment about the rep. Name the template change. A short note with four fields is easier to use than a long narrative. Write the deadline as a date and a local time.
Limits and sources of error
The source may exist but not be linked. Mark it as unlinked rather than absent. Use the same format for every handover so the next reader can scan it. Separate what was observed from what was assumed.
The note may be written after the touch. Record the date. Use the same format for every handover so the next reader can scan it. A control that depends on memory is not yet a control.
Review cadence
Repeat the review after a template change or at the same interval each quarter. Compare the same segments and the same definition. Separate what was observed from what was assumed. Review the first few notes together before the process expands.
Assign the follow-up to the sales lead and set a date. The protocol should produce a specific decision about the first-touch template. A short note with four fields is easier to use than a long narrative. Name the owner in the same line as the action.
Sources
Apply the operating question
Use the finding to define one source, output, review owner, and exception path inside a real workflow.
Discuss the workflow