Pinnacle's proposed RealPage consent decree is not a blanket ban on rental-pricing software. It draws a data boundary around competitors' nonpublic information, prohibits specified pricing features and cross-owner pooling, and makes continued software use depend on notice, certification, audits, and inspection. A court-appointed monitor is conditional: it follows an uncertified product choice or a court finding of noncompliance, not the mere existence of an algorithm.
The legal state also has two court gates. The September 4 stipulation proposes that Pinnacle comply with the terms while the Tunney Act process runs, but the accompanying procedure filing asks the court to sign that order. The reviewed documents do not show that interim order or the final judgment entered. Final judgment also needs publication, at least 60 days for public comment, a DOJ response, and a court finding that entry is in the public interest.
The question this map answers
Which data and pricing relationships would the proposed decree restrict, what proof lets Pinnacle use a revenue management product without a monitor, and which procedural gates remain before final judgment?
MyMap reviewed the proposed final judgment, Stipulation and Proposed Order, Competitive Impact Statement, procedure filing, and DOJ announcement at 4:03 AM Pacific Time on September 5, 2026. All were filed or published September 4. The reviewed court documents retain proposed-order status and do not show a judge's entry. The complaint allegations described in those sources remain allegations; the consent papers say there has been no testimony, trial, adjudication, or admission of fact or law.
In this map, external nonpublic data means competitively sensitive information from a third party, not data for a Pinnacle-managed property. A Defendant Property is a conventional multifamily property in the United States or its territories for which Pinnacle supplies revenue-management or related services; the definition excludes student, affordable, age-restricted or senior, and military housing. Runtime operation means what the product does while generating prices or recommendations; model training is the earlier process that creates or changes model parameters.
The first control is a typed data boundary
The proposed judgment does not treat every outside fact as forbidden. Public asking rents, publicly offered concessions, amenities, and availability can remain public data. Nonpublic information from the owner of the specific Pinnacle-managed property also occupies a different lane from a competitor's nonpublic information.
The prohibited edge is more precise: a covered pricing product cannot use external nonpublic data in runtime to price a Pinnacle property, send one Pinnacle property's nonpublic data to another owner or manager outside the allowed service relationship, pool nonpublic data across Pinnacle properties with different owners, or use a model trained on nonpublic data from outside the relevant owner. The restrictions follow the owner and data source, not just the vendor name.
That distinction matters operationally. A property manager cannot decide compliance from a product logo or a generic statement that a model uses “market data.” The review needs fields for property owner, data source, public or nonpublic status, training use, runtime use, disclosure destination, and pricing purpose. If those fields are collapsed into “third-party data,” the map loses the exceptions and the prohibited cross-owner joins.
The second control reaches pricing behavior
Even with acceptable data, the proposed decree would prohibit a product that incorporates a rental-price floor or limits decreases when that feature is based on disallowed nonpublic data. It also blocks a product from requiring Pinnacle to accept recommended prices or rewarding acceptance. A manually selected owner-specific floor is treated differently when it is not based on another owner's nonpublic data.
Pinnacle would also be barred from agreeing with a competing property manager or a non-client owner to use a particular revenue management product. The settlement separately prohibits disclosing, soliciting, or using competitors' nonpublic pricing information through direct or indirect channels, including calls, texts, shared documents, surveys, meetings, online forums, and software.
Those provisions show why “algorithmic pricing” is too broad a diagram label. The controlling document regulates at least four different relationships: data enters training, data enters runtime, software constrains a human pricing decision, and competitors coordinate outside the product. One compliant edge does not validate the others.
Product use becomes a proof workflow
Beginning 180 days after entry of the stipulation and order, Pinnacle must satisfy the product restrictions. Before using a revenue management product, it must provide DOJ 30 calendar days' written notice. A transferred property gets a 90-day compliance window from the transfer date.
For a non-RealPage product, the vendor must certify that the product satisfies the decree's restrictions or the product must otherwise qualify under the stated RealPage judgment route. The documents also describe a distinct RealPage path after a RealPage final judgment is entered. That cross-reference is a legal dependency; it should not be redrawn as an unconditional exemption for the vendor or for every version of its software.
Proof continues after selection. Pinnacle must adopt a written antitrust policy, designate a DOJ-approved chief antitrust compliance officer, train employees annually, audit revenue-management staff plus a random group of property-operations employees, collect annual attestations, and submit annual certifications. DOJ may inspect records, interview personnel, and review code or pseudocode for Pinnacle's proprietary pricing product.
The monitor is a conditional branch
The proposed judgment says no monitor is required when every pricing product Pinnacle uses has the required certification or is otherwise compliant under the product provision. A monitor branch opens if Pinnacle uses an uncertified or noncompliant product, or if a court finds a violation and DOJ applies for appointment. Pinnacle may suggest candidates, but DOJ selects the monitor subject to court approval.
If appointed, the monitor can examine compliance with product, communication, meeting, policy, and audit obligations; select up to 15 property-operations employees annually for review; interview personnel; inspect records; and report yearly. Pinnacle pays the monitor's costs. The monitor has no responsibility for operating Pinnacle's business and can end before the decree expires if DOJ determines the product-certification condition has been satisfied.
Certification is therefore not a decorative vendor letter. It is the edge that determines whether the ordinary audit-and-inspection lane remains sufficient or whether independent monitoring is added. The decree does not say certification proves every future action compliant; employee attestations, audits, government inspection, and enforcement remain separate controls.
The proposed interim order and final entry are different states
The stipulation asks the court to make the proposed terms operational during review and would give DOJ enforcement powers as if the proposed judgment were in force. It would also require Pinnacle to arrange and pay for the required newspaper notice once DOJ supplies the text and outlet. Those are proposed legal effects until the court enters the order.
The final-entry path is still open. DOJ must publish the proposed judgment and Competitive Impact Statement in the Federal Register and arrange the newspaper summary. The public-comment period runs for at least 60 days from the later specified publication. DOJ must consider comments, file and publish its response, and may then ask the court to enter judgment. The court may enter it only after finding the proposal in the public interest.
If entered, the judgment would ordinarily last five years, with possible early termination after three years on DOJ notice that continuation is unnecessary or no longer in the public interest. DOJ may challenge a violation occurring during the term for up to four years after expiration or termination. Those are enforcement windows, not a prediction that a violation will occur.
Confirmed, derived, and still unknown
The controlling sources confirm the defined data types and property scope; prohibited runtime, training, pooling, disclosure, pricing-feature, and coordination relationships; notice and certification requirements; compliance and inspection duties; conditional monitor triggers; the parties' proposed interim-compliance order; and the remaining Tunney Act and court-entry sequence.
MyMap derives the three-layer control map—data boundary, product-proof workflow, and enforcement branch—and the review table that records owner, source, visibility, training, runtime, destination, and purpose. Those are reproducible ways to test the terms, not additional court commands.
The sources leave unknown whether and when the court will enter the proposed interim order; whether and when the Federal Register and newspaper notices will appear; what public comments will say; whether DOJ changes or withdraws consent; when the court will decide final entry; which products and versions Pinnacle will use; what certifications will contain; whether a monitor will ever be appointed; and how the remaining RealPage litigation will be resolved.
The practical next step is to inventory each pricing product as a versioned data-flow record, not a brand name: list every training and runtime input, property owner, output recipient, price-floor or acceptance feature, vendor certification, notice date, and audit evidence. Keep the settlement tracker separate. “Stipulation filed,” “interim order entered,” “comment period open,” and “final judgment entered” are different legal states.