Direct record
Internal alias, community, earliest timestamp, direct channel, and the internal source that supports it.
For senior living operators
A Place for Mom referral fee dispute? Build the factual timeline first.
Verified July 22, 2026 · Reviewed against A Place for Mom's current service page and terms
The narrow job: your community may have a direct website form, call, walk-in, tour, or professional referral on file before a later referral-network notice arrives. Put those two records in one chronology before anyone argues about attribution.
Boundary: an earlier timestamp is not proof of legal attribution or automatically a contract answer. GeezerKeeper organizes facts; it does not decide whether a fee is owed, cancel a referral, create a tamper-evident audit log, or send a dispute.
Why two records matter
A Place for Mom's current service page says participating senior living communities pay it when a referred family moves in. Its current terms also say certain disclosures to participating organizations may continue for normal business practices, including billing matters, until those matters are closed.
Those public pages do not expose the private contract governing a particular provider or say that one timestamp controls every attribution question. The practical first step is therefore a bounded chronology supported by the operator's own records.
Six useful fields
Record enough to review. Not enough to create a new privacy problem.
Network record
Referral network, notice timestamp, and the subject line or CRM reference that identifies the notice.
Keep family names, medical details, financial information, government identifiers, passwords, and identity documents out of this narrow ledger.
What the $59 workspace does
- stores up to 250 chronology records only in the purchaser's browser;
- states whether the entered direct or network timestamp is earlier without deciding attribution;
- exports the factual chronology to CSV and provides a clean print view;
- also includes the co-brandable private-search handout for clients; and
- requires no account, subscription, prospect import, or CRM integration.
Not another CRM
Use the records you already have.
This is for the awkward exception your CRM or spreadsheet leaves scattered: a direct touch and a later referral notice that need to be reviewed together. It does not replace your system of record.
One professional location. One-time purchase. Instant browser access. No phone number required at checkout.
Using Caring.com too? Caring.com publishes a specific duplicate-lead response window and alert workflow. See the deadline tracker use case →
Primary sources
- A Place for Mom: How Our Service Works — the published provider-paid compensation model.
- A Place for Mom Terms of Use — provider forwarding, billing-matter language, and the boundary around family-provider transactions.
Plain answers
Does an earlier direct inquiry cancel an A Place for Mom referral fee?
GeezerKeeper cannot determine that. An earlier timestamp is a chronology fact, not a contract ruling. Review the applicable agreement, internal records, and qualified advice before acting.
What should the chronology contain?
Use an internal record ID, the community, the earliest supported direct-touch timestamp and channel, the referral-network notice timestamp and reference, and a non-sensitive note identifying the supporting record.
Does the workspace upload prospect data?
No. The chronology stays in that browser until the purchaser exports or clears it. Use internal aliases and exclude sensitive information.