What a Dispute Must Set in Motion
This chapter follows what the RentGrow complaint says should happen after an applicant challenges a tenant-screening report. The key issue is not whether a dispute ticket exists, but where the alleged error came from and what the reporting company must do next. Readers will be able to distinguish a reseller’s specialized dispute path from a general reinvestigation, follow the two possible routing branches, and see why calling a dispute “invalid” can determine whether evidence is corrected, sent upstream, or left outside the process.
A dispute is a change in the report’s lifecycle. Before the dispute, RentGrow has assembled information for a landlord or property manager. After the dispute, someone must decide whether the problem lies in RentGrow’s own assembly or in the information supplied by another consumer reporting agency. That classification is not a clerical afterthought. It determines who investigates, what information moves between companies, and whether a correction can return to the housing decision.
The reseller path is a branching duty
The FCRA contains general procedures for consumer reporting agencies when a consumer disputes the completeness or accuracy of information. The complaint describes that general path as requiring a reasonable reinvestigation and a record of the current status of the disputed information, including modification or deletion when appropriate. But the complaint also says that resellers are excluded from most of those general reinvestigation obligations and are subject to a specialized requirement under section 611(f).
On the complaint’s account, a reseller that receives a dispute must first determine whether the disputed item is incomplete or inaccurate because of the reseller’s own act or omission. The first branch is therefore causal, not merely administrative. Did the problem arise when RentGrow matched, assembled, merged, or presented the information? Or did the problem originate in the database of the consumer reporting agency that furnished the item?
If RentGrow’s own act or omission caused the problem, the complaint describes a duty to correct or delete the information. If the problem did not result from RentGrow’s act or omission, the reseller must convey the notice of dispute and the relevant information supplied by the consumer to each consumer reporting agency that provided the disputed item. A reseller can depend on an upstream agency for the source record without being allowed to skip this determination. The routing decision is the point at which distributed data ownership becomes an operational responsibility.
The two branches correspond to different kinds of failure. A duplicate created when RentGrow merges or displays two entries as separate may be an error in RentGrow’s own work, even if both entries originated with a vendor. A later change in a criminal or civil record may require the source agency to investigate if RentGrow did not create the underlying item. The same dispute can contain both questions: the source record may have changed, and RentGrow may also have presented the earlier version in a misleading way. The complaint’s framework does not permit a company to answer one question by assuming the other has been resolved. It calls for a determination of the reseller’s own role and, when appropriate, a handoff of the dispute to the source.