The study would test whether the stop rule is applied the same way or depends on the collector.
Question and scope
This is a proposed research protocol, not a report of completed findings. It asks how consistently dunning sequences are paused when a dispute is raised. The result would describe the stop rule. Update the template when the same question appears twice.
The protocol does not measure whether the dispute was valid. It measures whether the sequence stopped. A control that depends on memory is not yet a control. Keep the original note beside the corrected version.
Population and unit of analysis
Define the population as disputes raised during a stated window. The unit is one dispute, with the sequence, the pause time, and the resume condition recorded. Name the owner in the same line as the action. Separate what was observed from what was assumed.
Link the dispute to the account so the same dispute is not counted twice. If the source is unclear, route the question instead of guessing. Keep the boundary visible in the place where the work is assigned. Use the same format for every handover so the next reader can scan it.
Definitions and measures
Define suppression as the sequence being paused after the dispute is recorded. Define consistency as the same rule applied across collectors. Record the date and the source so the next reviewer can repeat the check. Record the exception and the person who approved it.
Report both separately. Name the owner in the same line as the action. A control that depends on memory is not yet a control. Use the same format for every handover so the next reader can scan it.
Evidence standard
Use the dispute record and the sequence log. A note that says paused without the time is weak. Write the deadline as a date and a local time. Ask whether a new reviewer could act on the record without a conversation.
Record the date and the collector. Record the exception and the person who approved it. If the source is unclear, route the question instead of guessing. Separate what was observed from what was assumed.
Sampling and collection
Use a census of the disputes. If sampling is necessary, stratify by collector. Keep the original note beside the corrected version. Use the same format for every handover so the next reader can scan it.
Pilot the classification on a few disputes and compare the reviewers. Clarify how a dispute raised by phone is treated. Separate what was observed from what was assumed. Keep the evidence with the record rather than in a separate log.
Analysis and reporting
Report suppression and consistency by collector. Show the disputes where the sequence continued. If the source is unclear, route the question instead of guessing. Ask whether a new reviewer could act on the record without a conversation.
Present the results as a description of the stop rule, not a ranking of collectors. Separate what was observed from what was assumed. Ask whether a new reviewer could act on the record without a conversation. Keep the boundary visible in the place where the work is assigned.
Limits and sources of error
The dispute may be recorded in a different system. State the systems included. Separate what was observed from what was assumed. Update the template when the same question appears twice.
The sequence may be paused manually. Record the action. A control that depends on memory is not yet a control. A short note with four fields is easier to use than a long narrative.
Review cadence
Repeat the review after a rule change or at the same interval each quarter. Compare the same collectors. Ask whether a new reviewer could act on the record without a conversation. Test the rule on one real account before applying it to the queue.
Assign the follow-up to the collections lead and set a date. The protocol should produce a specific decision about the stop rule. If the source is unclear, route the question instead of guessing. Write the deadline as a date and a local time.
Sources
Put the protocol into operational context.
Discuss the queue, evidence, ownership, and safeguards that apply to your workflow.
Discuss your workflow