Regulatory Radar · Institutional
Regulatory Radar for a whole research office
One subscription, one card, and a seat for each named person who needs their own answers about 2 CFR 200, NIH, NSF and UKRI policy. $25 per seat per month, from 3 to 50 seats bought on this page — or an enquiry first, if that is how your institution buys things. This page is written to be read by the person who will have to defend the line item.
Seats
What institutional deployment actually means
A seat is a named person, not a login your office shares. That is a deliberate design decision and it has consequences worth understanding before you count heads.
One person, one seat
Each seat is attached to an email address and to the CASRAI account belonging to that address. The assistant’s daily allowance is counted per person, not pooled across the subscription, so one colleague’s heavy week cannot exhaust anybody else’s. Every seat gets the full 150 questions a day and the full 10 source passages of retrieval depth — there is no reduced-tier seat.
Changing the seat count
The number of seats you pay for lives on the subscription itself. The person who bought it opens the Stripe billing portal from their CASRAI account and changes the number there; Stripe prorates the difference on the next invoice. Nothing has to come through us for that.
Assigning and revoking a named seat
Today this part is done with us directly rather than in a self-service console: you tell us the addresses, we place the seats, and we change them when you ask. There is no team-admin screen on the site yet, and this page will say so until there is one. If a self-service roster is a requirement rather than a preference for you, say so in the form below — it is the kind of thing that decides what gets built next.
A revoked seat stops answering within a minute. Not instantly, and the difference is real rather than pedantic: entitlement is cached for sixty seconds, so a seat removed this second can answer one more question before the cache expires. If you need somebody cut off the moment they are walked out of the building, that is a minute you should know about.
If you reduce the seat count
Nothing is deleted. When more people hold seats than the subscription pays for, the seats accepted earliest keep working and the most recent ones stop; the roster stays intact so you can still answer “who had access, and when”. Raising the count again restores them in the same order. We would rather you found a colleague locked out than found their record gone.
What it does
Claim by claim, with the qualification attached
Each row is what the product does and, in the same breath, what that claim does not cover. If a row seems to be missing a caveat, that is worth an email — we would rather correct this page than a purchase order.
Ask CASRAI answers research-administration questions and cites its sources.
It is retrieval, not a trained model: your question is matched against a vectorised corpus of 72,264 passages (counted 2026-09-03; the subscriber dashboard shows the live figure, so you can check us), the 10 best-matching passages are put in front of a language model, and the answer carries links to the passages it used. Nothing is trained or fine-tuned on your questions, and answers are validated for groundedness before they are shown. It can still be wrong; the citations are there so you can tell when it is.
150 questions a day, for each seat.
A per-person allowance rather than a pool the office shares. It resets daily. In practice nobody has hit it, but it is a real ceiling and it is stated here rather than discovered.
A dashboard of newly published regulatory, funding and compliance items.
Checked on a daily schedule against 6 official government and funder feeds (U.S. Federal Register, U.S. Federal Register — research & grants agencies, Grants.gov, Regulations.gov (open comment dockets), NSF News, UKRI) alongside CASRAI's own published content. Filterable by source, and every item links straight out to the original notice — you are meant to read the source, not our summary of it.
The dashboard tells you when the pipeline last ran.
This is the row we would want if we were buying. "The feed is quiet" and "the job has not run since Tuesday" look identical on screen, so the dashboard reads the ingest run ledger and shows the last successful run, flagging it when it is stale. You do not have to take our word for whether the thing is running — the page tells you, including when the answer is unflattering.
An API and an MCP server, for a seat that wants to script it.
Seats can mint API keys and call the assistant from their own tooling rather than through the web console. The daily allowance is the same allowance — scripting does not buy more of it.
Before you evaluate it
What we are not selling you
Everything here is something a competitor's page would leave out. You would find all of it in week one anyway, and finding it after a purchase order is much worse than finding it now.
The daily email digest does not deliver. Do not count it.
Our main product page describes a daily email carrying the same items as the dashboard. That email has never sent to anybody. The mail credentials it needs are not provisioned and its scheduled job is switched off, so as of today it is a plan and not a deliverable. The dashboard carries those items and works; the email does not, and it should not appear anywhere in your evaluation until we can tell you it has started. If that is the feature you actually wanted, tell us in the form — that is useful information and it will not offend anybody.
There is no team-administration console yet.
Seat counts change in the Stripe billing portal, but adding and removing the named people on those seats is done by asking us. For an office of a handful of people that is a two-line email; for a large rollout it may be a genuine objection, and it is a fair one.
No customer list, because there is almost nothing to list.
You will not find testimonials, institution logos, ratings or a “trusted by” count anywhere on this site, and that is not an oversight. Regulatory Radar is new and has one paying subscriber. If being an early customer is a problem for your process, it is better that you know that in the first minute rather than after a reference call. If it is not a problem, being early is worth something: what gets built next is decided by a very short list of people, and you would be on it.
It is an assistant, not an authority.
Answers cite their sources so you can check them, and you should. Nothing here is legal or regulatory advice, nothing replaces reading the notice, and no answer should be the last step before a submission. What it saves is the search, not the judgement.
Data handling
What is stored, for how long, and where it goes
Written for the person who has to fill in a data-protection form about it. Every statement below describes what the code does, not what a policy document aspires to.
Questions are stored; the answer text is not kept indefinitely.
Questions are logged before the answer is generated — the ones we fail to answer are the most useful records we have. By default the question text is redacted after 400 days and the answer text is dropped after 90. The anonymised shape of a question (its category, its normalised form) is kept, because that is what tells us which guidance to write next.
Personal data is scrubbed at the point of writing, not afterwards.
Question text and any feedback comment pass through a PII scrubber at the last point before a durable write, regardless of whether the caller already scrubbed them. A belt-and-braces arrangement on purpose: the scrub that matters is the one nothing can bypass.
IP addresses are never stored raw.
They arrive at the logging boundary already pseudonymised with a pepper that rotates at midnight UTC, and a raw address is rejected rather than written. The pseudonym itself is dropped after 30 days by default.
The model provider is told not to keep anything.
Every request to the model carries provider.data_collection = "deny". That is a published commitment with no configuration switch to turn it off — the flag that records the operator's understanding of it can be unset and the header is still sent, and the service logs a warning about it. Your questions are not training data for us or for anybody downstream.
API keys are stored as hashes.
A key is shown to you once, at creation. What we hold is a SHA-256 hash, compared in constant time; the plaintext is never written down on our side. A lost key is replaced, not recovered — which is the correct behaviour and worth knowing before somebody asks us to look theirs up.
Erasure is a supported operation.
A data-subject erasure request deletes the rows rather than redacting them, and there is a maintained tool for it rather than an ad-hoc query. Ask us and we will run it.
If your DPO needs something more formal than this section, ask in the form below and say what shape it needs to be in. We would rather answer a real questionnaire than publish a document that sounds like one.
The organisation
Who you would actually be buying from
Procurement will ask this before it asks anything else, so it is on the page rather than in an email.
CASRAI — Consortia Advancing Standards in Research Administration Information — is not itself a separately incorporated legal entity. It is operated as a charitable programme of The Health Initiative, a registered U.S. 501(c)(3) nonprofit, under a fiscal-sponsorship arrangement. That sponsor is the entity with the legal and financial standing: it holds funds, signs agreements and receives grants on the programme’s behalf.
Editorial decisions sit with the CASRAI Editorial Board and the working groups, which are distributed across the UK, the Netherlands, Canada, the United States and Australia. There is no single head office and no postal address to put on a supplier form — correspondence goes through the editorial address. Our imprint and terms set out the rest, including the governing law.
If your institution’s supplier-onboarding process needs a counterparty with its own company number, the honest answer is that today that counterparty is the fiscal sponsor and not CASRAI. Tell us early in the form below rather than late — it is a solvable problem when it is raised in week one and an awkward one in week six.
Money
How payment works, and what it cannot do
Consistent with what the main product page already tells a single subscriber. Read the second half of this section before you start an internal approval.
Payment is by card, on Stripe’s own checkout page. The subscription is monthly, in USD, at $25 per seat per month. There is no minimum term, no automatic escalation and no cancellation fee — the person who bought it cancels in the billing portal themselves and access runs to the end of the month already paid for. Every payment produces an itemised Stripe invoice, emailed to the payer, carrying the name and billing address entered at checkout. There are no partial refunds.
Between 3 and 50 seats you start it yourself — choose the number of seats further down this page and press Subscribe. Whoever pays becomes the owner of the subscription: they hold the billing portal, and they are the only person who can change the seat count or cancel.
What we cannot do today
- Purchase orders. We cannot accept a PO, raise an invoice against one, or work to net-30 payment terms. There is no accounts-receivable function here to do it with.
- Institutional invoicing on terms. The Stripe invoice follows the payment; it is a receipt, not a request for payment your finance office can process first.
- Tax identifiers. No sales tax or VAT is added, and we cannot record an institutional tax ID on the account.
- Non-USD pricing. A card issued outside the United States applies its own exchange rate, so the amount that appears on a reimbursement claim will not be exactly $25 per seat.
In practice that means a departmental card, or a named person paying and reclaiming. If neither of those works at your institution, say so in the form — we would rather tell you honestly that we cannot meet your finance office’s requirements than take a payment that turns into a reconciliation problem for you six weeks later.
Buying for one person instead? The single subscription is $29 a month and you can buy it yourself in about a minute on the main Regulatory Radar page — no conversation needed.
Two ways to do this
Buy the seats, or talk to us first
Both are real routes and neither is the consolation prize. A three-person office should not have to wait for a call, and a procurement process should not be handed a card form.
Buy seats now
Card payment, on Stripe’s own page, in about a minute
For an office that can put this on a departmental card today. Choose the number of seats and pay; nobody has to talk to us first. Once the payment lands you become the owner of the subscription and place the seats yourself — today that means telling us the addresses, which is a two-line email and is described in full above.
3 seats · $75/month$25 per seat per month, USD, on one subscription.
Regulatory Radar for teams$25.00 / seat / month · USD
- Seats
- 3
- Monthly subscription
- $75.00 · 3 × $25.00
Cancel anytime from your billing portal. No contract, no minimum term, no cancellation fee. Seats can be changed on Stripe’s page before you pay, and afterwards in the billing portal — Stripe prorates the difference.
Stripe’s page collects your email, name and billing address — the last two appear on your invoice. Institution is optional.
Talk to us
Request a call
A real conversation with somebody who can answer for the product, not a demo booking that lands you in a sales sequence. Nothing here signs you up to anything and nothing here takes a payment — if you would rather just buy the seats, that control is directly above this form.
Or skip the form
Email [email protected] with as much or as little as you like. It reaches the same people and depends on nothing on this page working.
Useful things to include if you have them: roughly how many people, what you are currently doing instead, and the one question that would settle it either way.
Related
Elsewhere on this site
Regulatory Radar
The product page, including the single subscription you can buy without talking to anybody.
For institutions (free)
CRIS integration notes, compliance mapping, training kits and policy templates. CC-BY 4.0, no fee.
Parent organisation
The fiscal-sponsorship arrangement, and the entity behind the programme.
Imprint
Who operates the site, and how to reach us in writing.
Terms
Governing law and the terms a subscription is bought under.
Ask CASRAI
The assistant itself. Try a question before you decide anything.
