Follow-up after the reporting demo
Email thread Quarrington Care Network: documents · sales
After the reporting demo, Trent Nakamura said referral counts did not tie to his report and asked which source wins, how records are traced, and who owns a broken connector. He wants a written answer before any pilot.
What was said
What this says
Current to 11 Oct 26After the reporting demo, Trent Nakamura said referral counts did not tie to his report and asked which source wins, how records are traced, and who owns a broken connector. He wants a written answer before any pilot.
Ask: Trent wants to know which source wins when the CRM and his report disagree, how a record is indexed and refreshed, and which of his reports the brain would replace. He will send three reports, including the monthly volume reconciliation that did not tie.
Customer view: He says none of this is a blocker yet, but he will not sign off on something he cannot check. A pilot depends on Hannah Lowe's write-up.
Next: Jordan Pike committed to written answers on refresh, traceability and connector notification. The proposal value of £62,000 stays while scope is settled.
The thread
Updated 9 Oct 26Messages
Jordan Pike 20 Feb 2026 16:40Hi Danielle, hi Trent, Thanks for the questions yesterday. Trent, I appreciated you pushing on the numbers. Here's where we are. Two things came out of the session that I want to answer in writing: - how the brain treats referral counts when your own reports and the source systems disagree - what the connector set-up asks of your team Hannah will put the detail in writing. To be transparent, I would rather she checks every line than that I answer from memory. We are still working toward 16 Apr 2026 for paperwork, and the proposal value stays at £62,000 while we settle scope. Trent, what else is missing for you to say yes to a pilot? Thanks, Jordan
Trent Nakamura 24 Feb 2026 16:49Jordan, Thanks. My notes from the demo: - The referral counts for one hospital did not tie to my numbers. Yours were higher. I need to know which source wins when the CRM and my report disagree. - I want to see exactly how a record gets indexed and how often it refreshes. I'll reconcile it myself, but only if I can trace it. - Who owns a broken connector? If it stops loading, do I find out, or do the liaisons? - I do not want to build one-off reports for things the brain can answer. Show me which of my current reports it would replace, and which it would not. None of this is a blocker yet. I just won't sign off on something I can't check. Trent- Jordan Pike 24 Feb 2026 17:41Trent, Danielle, Fair points, Trent, and thanks for laying them out so clearly. Here's my straight answer. On which source wins, the brain does not quietly pick one. It shows where the sources differ, and your team decides the rule. On refresh and traceability, Hannah will write up the nightly refresh and how a record can be traced back to its source. On broken connectors, your admins are notified, and I'll have that confirmed in writing rather than promise it here. On your reports, Hannah will go through them with you and mark which ones the brain would answer and which stay yours. Trent, if you can send two or three of the ones you care most about, we'll use those. Danielle, I know you need this for the leadership team. We'll keep the timing in view. Thanks, Jordan
- Trent Nakamura 26 Feb 2026 11:10Jordan, That works. I'll send three reports this week: - the referral trend by hospital - the liaison activity summary - the monthly volume reconciliation, which is the one that did not tie If Hannah can show how the brain handles the third, I'll be much more comfortable. I'd also like her write-up before we talk about a pilot. Trent