What a Tenant-Screening Report Actually Does
This chapter examines the operating role of RentGrow’s tenant-screening report: what enters the system, what RentGrow adds by assembling and evaluating it, and how the result reaches a landlord or property manager. The practical goal is to distinguish four things that are easy to blur together—a source record, a reporting intermediary, a screening report, and a housing decision. Once those boundaries are clear, the FCRA duties described in the RentGrow complaint become easier to understand as responsibilities attached to specific handoffs, not as abstract legal labels.
The starting point is the report’s purpose. The complaint alleges that RentGrow sold Tenant Screening Reports through its ScreeningWorks Pro product to rental property owners and management companies. Those reports could include credit information, criminal and eviction records, rental history, historical addresses, and a determination of whether an applicant met, conditionally met, or did not meet the customer’s rental criteria. The report therefore occupies a middle position: it is not the original record, but it is also not a passive envelope carrying someone else’s data unchanged.
One report, several relationships
A public record is an entry maintained by a government entity or obtained from a public-record source. An upstream consumer reporting agency or vendor may gather such entries, organize them, and furnish information to another company. The complaint describes RentGrow obtaining information from other consumer reporting agencies, public-record vendors, jurisdictions, and additional data sources. RentGrow then assembled information for a report used by a third party. Each step can preserve, lose, or change context.
A source record usually answers a narrower question than the screening report does. A court system may record that a case was filed, that a judgment was entered, or that a proceeding reached another disposition. A data vendor may package that information with identifiers and send it to a reporting company. RentGrow’s product, by contrast, is presented to a customer who wants help deciding whether an applicant meets rental criteria. The report must therefore connect records to a person, decide which entries refer to the same matter, and communicate enough context for the customer to interpret them. Those are not merely different screens for the same data. They are different functions with different opportunities for error.
The output also need not be a single numerical score. The complaint describes a determination that an applicant met, conditionally met, or did not meet a property manager’s criteria. That determination can be based on several report components and a customer’s screening rules. The retained evidence does not show the full decision process of any particular landlord. The safe conclusion is narrower: RentGrow’s report is designed to influence a housing decision, and the way it organizes information can affect the starting point from which that decision is made.
The applicant is the subject of the report, but not simply another data point in the diagram. The applicant’s identity and history determine which records should be connected to the report. The applicant can also request information in the file and dispute what the report says. That creates a two-way relationship with RentGrow: the company prepares a report about the applicant, while the applicant may ask what information and sources the company holds and challenge the result.
The landlord or property manager occupies a different role. They use the report to help select tenants. The complaint describes the report as a factor in determining rental eligibility, not as a legal command that automatically decides every application. That distinction matters. A screening result can influence a decision without being identical to the landlord’s final judgment. At the same time, the difference does not make the report unimportant. If the report says that an applicant does not meet the stated criteria, the landlord may have little reason to investigate the underlying records unless the report, the applicant, or the process creates an opportunity to do so.
RentGrow’s role is consequently broader than forwarding a document. The company’s report can combine several kinds of information, decide how records are related, and present the combination in a form that a customer can use. Even if an upstream source supplied an accurate item, RentGrow’s treatment of that item may affect how a reader interprets it. A court filing, a judgment, an address history, and a credit entry do not carry the same meaning. Putting them into one screening product requires decisions about identity, relevance, grouping, status, and display.
Those decisions also determine what each party can see. The landlord or property manager generally receives a customer-facing result, while the applicant may need to request a file disclosure to learn what the reporting company retained and where it came from. The upstream agency may see the record it furnished but not the way RentGrow combined it with other entries. RentGrow may have access to the internal links among all of these pieces, yet the complaint alleges that some source information was not disclosed to consumers. A report can therefore be understandable to its seller and still opaque to the person who must correct it.
The system can be represented this way:
This is a relationship model, not a claim about RentGrow’s undocumented software architecture. Its purpose is to show what crosses each boundary. Public records and vendor information enter through source relationships. RentGrow assembles the information into a screening report. The report produces or carries an eligibility signal to the landlord or property manager. The applicant can send a dispute to RentGrow, but a dispute may also have to reach the agency that furnished the item. The report is therefore both an output and a junction: multiple inputs arrive there, and several parties rely on what leaves it.
That junction creates hidden dependencies. If an upstream agency sends records from different repositories, RentGrow must determine how they relate. If a vendor uses an address or name not present in the original application, the match may depend on information the applicant does not know was used. If a report is sent to a property manager and later corrected, the correction has to remain connected to the report and reach the people who relied on the earlier version. The complaint and CFPB guidance support examining these interfaces; they do not reveal every internal rule RentGrow may use.
At each interface, a different question becomes important. At the source boundary, is the record current and legally available? At the matching boundary, does the information identify this applicant rather than someone with a similar name or address? At the reporting boundary, are several entries separate events or stages of one proceeding? At the decision boundary, does the customer understand what the report does and does not establish? At the dispute boundary, can the company identify whether its own assembly caused the problem or whether the source agency must investigate? Thinking in interfaces prevents a vague conclusion that “the database was wrong” from hiding the particular choice that needs correction.
Why the legal labels matter
The Fair Credit Reporting Act regulates the function of consumer reporting, not merely the format of a database. The complaint alleges that RentGrow operated as a consumer reporting agency because it regularly assembled and evaluated information about consumers, for fees, to furnish consumer reports to third parties through interstate commerce. It also alleges that RentGrow acted as a reseller because it assembled and merged information from other consumer reporting agencies without maintaining a database from which new consumer reports were produced.
These are allegations in a federal complaint, not a final determination of liability. But the classifications explain why the company’s position in the information chain matters. A business that only maintains a government record and a business that combines records into a report for a landlord do not perform the same function. A business that resells information from other reporting agencies may depend on those agencies while still making its own choices about assembly, presentation, and dispute routing. The legal category follows what the business does with information, not whether a computer performs the task.
The reseller label also does not mean that RentGrow necessarily owns every underlying record. It describes the part of the activity in which a company assembles or merges information from other reporting agencies for a third party. That distinction matters when responsibility is assigned. An error may already exist in an upstream record, or it may arise when RentGrow matches, combines, labels, or displays information. The complaint’s account of the law requires the reseller to make that distinction when a consumer disputes an item. A system can have distributed ownership of data and still require a definite answer about who must act next.
Nor does a legal classification tell us what a particular report contained or how a particular landlord decided. It establishes the kind of activity the complaint says RentGrow performed and the duties that follow if the classification and facts are proved. That is enough to organize the analysis, but not enough to infer an undocumented algorithm, a universal customer workflow, or a final outcome for every applicant.
The complaint organizes the relevant duties into three connected groups.
First, a consumer reporting agency must use reasonable procedures to assure the maximum possible accuracy of the information concerning the individual in the report. “Accuracy” here is not limited to whether a string of names or case numbers appears in a source. It includes whether the report concerns the right person and whether the information is presented in a way that does not create a false impression about the person’s history. The CFPB’s advisory opinion makes this broader interpretation concrete by discussing duplicate entries, missing dispositions, and records that are no longer legally accessible to the report user.
Second, when a consumer requests a file disclosure, the complaint describes a duty to provide all information in the file and the sources of that information. This requirement gives the applicant a way to see what the reporting company relied on and to challenge an error closer to its origin. Source disclosure is therefore part of the accuracy system. It can reveal that a supposed second event is a duplicate, that a record came from an unexpected vendor, or that an identifier used for matching does not fit the applicant.
Third, a consumer reporting agency has duties when the completeness or accuracy of information is disputed. For a reseller, the complaint describes a specialized route: the reseller must determine whether the problem resulted from its own act or omission. If it did, the reseller must correct or delete the information. If it did not, the reseller must convey the dispute and relevant information to the agency that supplied the item. The classification affects who must act next, but it does not turn the dispute into someone else’s problem by default.
This three-part structure is useful because it follows the report through time. Accuracy governs preparation. File and source disclosure give the applicant a view into the preparation. Dispute duties provide a route for changing the report when the view is wrong. A failure in any one part can weaken the others. A company cannot meaningfully investigate a dispute if it has not preserved enough information to identify the source. A source disclosure cannot fully repair a report if a correction is not carried into the version a landlord uses. And a dispute process cannot protect an applicant if an accurate underlying event is displayed as several events.
The report is a boundary, not a black box
The report’s middle position also clarifies what the evidence does not establish. The complaint describes RentGrow’s alleged business relationships and practices, but it does not provide a complete technical architecture or establish that every report used every source or procedure described. The CFPB advisory opinion supplies an official interpretation of FCRA accuracy obligations for background screening; it does not independently prove each allegation about RentGrow. A careful account must keep those roles separate.
What the system model does establish is the location of the accountability question. It is not enough to ask whether a vendor supplied a record or whether a landlord made the final choice. The relevant question is what happened between those points: how RentGrow combined and evaluated information, what it disclosed to the applicant, how it handled a challenge, and what the landlord received. That is why a tenant-screening report should be treated as a decision-support system with regulated interfaces, not as an unexamined mirror of public records.
The most revealing failures will occur at those interfaces. When several sources describe one proceeding, the report must preserve the relationship among them rather than making one case appear to be several. That is where the question of duplication becomes a question about the risk signal a landlord sees.