Provenance
Internal alias, community, earliest supported source timestamp and channel, Caring.com notice time, and the alert or CRM reference.
For senior living operators
Verified July 22, 2026 · Reviewed against Caring.com's current partner guidance
The narrow job: a Caring.com lead or tour alert arrives, but your community already has the prospect in its own records or received the lead from another source. Put the earlier source, network notice, applicable response window, and reporting status in one local chronology.
Free, private, one-record tool
Enter dates only. The calculator runs in this browser, uploads nothing, stores nothing, and never asks for a prospect's name or contact information.
Caring.com's published partner workflow says a partner that does not report a pre-existing lead by the applicable deadline can remain responsible for the associated referral fee if the prospect later moves in. The same page says the lead or tour alert contains a Report Duplicate link and asks the community to identify the original source.
That makes the operational problem more specific than a general referral-fee disagreement: preserve the earlier record, find the real deadline, use the official route, and keep the response. GeezerKeeper organizes those steps but does not perform or adjudicate them.
The minimum record
Internal alias, community, earliest supported source timestamp and channel, Caring.com notice time, and the alert or CRM reference.
The business-day window or exact contract deadline, the internal check-by date, and whether the duplicate was reported, confirmed, declined, or closed.
Do not copy family names, medical details, financial information, government identifiers, passwords, or identity documents into this narrow ledger.
See the paid workspace
This illustrative record uses the same columns as the purchased local chronology. It shows entered facts and a weekend-only reminder; it does not decide attribution or a fee.
| Record | Community | Direct touch | Network notice | Check-by / status | Chronology signal |
|---|---|---|---|---|---|
| Lead-2026-014Illustrative internal alias | Sample Community | Jul 17, 9:20 AMOfficial website form | Jul 20, 11:15 AMCaring.com tour alert | Exact: Jul 24Estimate: Jul 27 · Open | Entered direct timestamp is earlier.Review the alert, contract, and supporting records. |
Illustrative data only. The purchased workspace is interactive, stores records only in that browser, exports CSV or print, and uploads no prospect data. The actual alert and contract control.
A $59 exception layer
Caring.com already supplies the duplicate-report route. GeezerKeeper covers the awkward cross-record layer around it: which source came first, when the notice arrived, what deadline applies, and whether the network confirmed the result.
One professional location. One-time purchase. Instant browser access. No phone number required at checkout.
Caring.com's current public guidance says five business days from the lead send date or the deadline in the partner contract. Use the actual alert and agreement; the workspace's check-by calculation skips weekends only and is an internal reminder.
No. The earlier timestamp is a fact, not a contract result. Use Caring.com's official duplicate route and review the applicable agreement and records.
No. The workspace neither sends nor submits anything. It keeps the local chronology, deadline basis, and status while the operator uses Caring.com's official alert link.