A Public Protocol for Tracking RAYSolute's Own Calls
RAYSolute is building a public, honest protocol to track its own feasibility and investment-readiness verdicts against what actually happens afterward. This page sets out the rules for that tracking, published before any result exists to report against them.
Why this is different from our case studies
RAYSolute already publishes case studies describing real engagements. This protocol is a stricter, additional standard we are building on top of that practice, not a replacement for it.
Case studies, published today
RAYSolute publishes narrative case studies describing real client engagements: the problem a school or institution brought to us, how we approached it, and what happened. These are written after an engagement concludes, drawing on the full picture available at that point.
Accountability protocol, in development
This protocol is a stricter, calibration-style standard we are building in addition to our case studies. A target is frozen at the moment a verdict is issued, before the outcome is known, and every verdict is later measured against that frozen target on a fixed schedule, using a scoring rule decided in advance.
To be direct: the case studies published today were not written against these rules, and this page does not claim they were. This protocol governs feasibility and investment-readiness calls entered into the register going forward, once it is built.
What the protocol will track
Once built, entries move through the register under rules fixed in advance, not chosen after seeing how a project turned out.
Which engagements qualify going forward: formal feasibility studies and investment-readiness assessments where RAYSolute issued a defined verdict. Only calls entered under this protocol count toward it; nothing is added retroactively.
The enrollment, financial or readiness target used to judge an outcome is fixed at the moment the verdict is issued, not reconstructed afterward once results are known. A target set after the fact would make the whole exercise meaningless.
Each verdict is checked against its target at a fixed point after issuance, described by category, such as a Year-1 checkpoint or a Year-3 checkpoint, rather than whenever the result happens to look favorable.
The rule for what counts as a hit, a miss, or a call still too early to score is decided before the protocol goes live and does not change to fit a particular result.
How small samples will be handled honestly
A track record with only a handful of entries is easy to make look better or worse than it is. These commitments hold regardless of how few or many entries the register holds at any point.
Commitments that apply from the first entry onward
- Raw counts are published before any percentage or rate, so a reader can see exactly how much data a figure rests on.
- No hit rate or accuracy rate is published below a minimum sample size fixed in advance; until the register clears that threshold, only raw counts are shown.
- A miss stays published exactly like a hit. Nothing is filtered out because the result was unfavorable.
- Every vintage of calls is shown together. RAYSolute does not choose which year's calls to display and which to leave out.
Confidentiality commitments
These limits do not loosen as the register grows or as RAYSolute wants a stronger track record to show. They apply to every entry, at every stage.
Never published
- A client's name or the name of the institution
- A city, campus or any location detail that could identify the project
- Exact enrollment, fee or financial figures
What will be published
- The calendar year the verdict was issued
- A coarse project category, such as greenfield versus expansion, or K-12 versus higher-education
- The verdict category RAYSolute issued
- Banded outcome ranges, never exact figures
Governance
A protocol like this only means something if the person keeping score has no reason to make the numbers look better.
This protocol is owned by a function kept structurally separate from business development. The person deciding whether a call was a hit or a miss has no stake in winning the next engagement.
Once live, the register is published on a fixed schedule, not whenever the numbers happen to look favorable.
If the rules in this protocol change, that change is published as a visible, dated update to this page. Nothing is redefined quietly.
Questions About How We Approach Accountability
If you have a question about this protocol, or about how RAYSolute approaches accountability for your own engagement, send us a note.
Common questions about this protocol
Answers below match the FAQPage schema embedded on this page so AI assistants can surface them directly.
Is this live yet?
No. What you are reading today is the protocol itself, the rules for how RAYSolute will track and publish outcomes, published before a single result exists to report. That order matters: publishing the rules first is the only way to prove they were not written after the fact to fit a result RAYSolute already knew. Live data follows only once resolved calls exist to report against these fixed rules.
Will you publish the calls you got wrong?
Yes. A verdict that did not hold up stays in the register exactly like one that did, with the same visibility and the same detail. Excluding or quietly dropping a miss would defeat the purpose of publishing a track record at all, so misses are never filtered out once they enter the register.
Will individual clients ever be identifiable?
No. RAYSolute will never publish a client's name, a city or campus-identifying location, or exact enrollment, fee or financial figures for any entry in this register, at any time. What will be published is limited to the calendar year a call was made, a coarse project category, the verdict category, and banded, never exact, outcome ranges. That ceiling is permanent and does not loosen as the register grows.
How is this different from your case studies?
RAYSolute already publishes narrative case studies describing real engagements and how we approached them. This protocol is a stricter, additional standard built on top of that practice, not a replacement for it: targets frozen at the moment a verdict is issued, a fixed scoring rule decided in advance, and defined resolution windows, rather than a story written after the fact. The case studies published today were not written against these rules, and this protocol only governs calls entered into the register going forward, once it is built.