We use Verand, the product we build, to research and draft the writing on this site. Then a person reads it, checks the sources, changes what needs changing, and decides whether it goes out. We'd rather tell you that plainly than let you work it out.
We make software that drafts and checks writing for people in regulated work, and we run this blog on it. Hiding that would tell you something unhelpful about how we'd treat your content, so here it is: we draft what you read here with Verand, the same way our customers draft theirs.
We use it to gather research, to turn an outline a person has approved into a first draft, to suggest titles and headings, and to make the images at the top of a post.
We don't use it to decide what's true, what's fair, or what gets published. A person does all three, on every post, every time. If something here is wrong, that's a person's mistake and a person will fix it.
A first draft is a starting point. It isn't a finished post and we've never treated it as one.
One person holds editorial responsibility for this site, and their name is on the card rather than buried in a policy page. Every post has been read and approved by a person before it went live, and that person is accountable for what it says.
If you write to us about something on this site, that's who reads it. We'd rather name someone than hide behind a company, because a company can't be wrong and a person can.
It really is a sequence. Nothing here can be skipped by being in a hurry.
We write about something because someone asked us about it: a customer, a sales call, a support thread. We look at what people are searching for to help us decide how to word a piece and how far to go into it, never to decide whether a subject deserves writing about at all.
We read what's already been written on the question, go to the primary documents behind it, and pull together the facts a good answer would have to include. We turn that into an outline: the angle, the sections, the questions to answer, and what has to be checked before anything is written. A person reads and edits that outline before the drafting starts.
We write the first draft with Verand, from the approved outline, in our own voice, using things this company has actually built, spent, measured or got wrong. That draft is raw material. It's the step that saves us time, and it's the only step AI does on its own.
We run the draft through the same checks we sell to our customers. They look at how the piece is built, whether its claims are sourced, whether anything in it would be a problem to publish, and whether it covers what the outline said it would. The checks are strict and they're automatic, and they still aren't the part that decides.
Someone reads the draft end to end, opens every source it cites, and checks each number against the document it came from. They rewrite what's clumsy, cut what we can't stand behind, and add the things only a person who has done the work would know. This is the slowest step. It's also the one that makes the rest worth doing.
Nothing on this site publishes itself. There's no schedule, no queue and no setting here that sends a draft to the site without a person deciding to send it. If a post is live, somebody chose to make it live, and they had read it first.
Publishing isn't the end of it. We go back over what we've written, and when something we said stops being true, we change the text and change the last-updated date with it. If the change is more than a typo, we leave a short dated note at the foot of the post saying what we changed. We don't quietly edit a claim and carry on.
The short version: AI helps us write. People decide what we say.
All of it is work a person then reads, changes and takes responsibility for.
If we ever change one of these, we'll say so here and change the date at the top.
You shouldn't have to take our word for anything you could check yourself.
When we state a fact that isn't ours, we say where it came from and we link straight to it. Not a mention of a study, the study. Not a summary of a rule, the rule.
The regulator's own page, the statute, the agency that released the data, the paper itself. If we're leaning on someone else's reading of a document, we say that's what we're doing and we link the document too.
No marketing blogs, no pages written to rank, no forum posts, no press releases dressed up as research. If a claim only exists on pages that are selling something, we leave it out rather than pass it on.
If a figure comes from our own work, we label it as ours and say how we measured it, so you can judge it for what it is.
If we're writing about our own product, or about a competitor, we have an obvious interest in the answer and we'll say so in the text rather than let you find out later.
This one never changes. We don't re-date an old post to make it look new.
If this is later than the published date, something in the post changed, and there's a short dated note at the foot of it saying what.
Where a post depends on a rule, a rate or a figure that moves, we go back to it and check. If we can't stand behind a post any more and can't fix it, we'll say so at the top of it rather than take it down without a word.
A corrections policy is only worth the route it gives you. This one is a real inbox, read by the person whose name is on the work.
Send us the page and the sentence you're disputing. A source helps, and you don't need one to write to us.
If the sentence is wrong, we correct the text, change the last-updated date, and add a dated note at the foot of the post saying what changed and when. If a reader found it first, the note says so. We don't delete a claim quietly and move on.
If we disagree with you, we'll tell you why, in a reply, rather than edit the argument out of the post and say nothing.
Some standing limits, so nothing above is read as more than it is. Verand is a software company in Cheyenne, Wyoming. Nothing we publish here is legal, financial, tax or medical advice, and none of it replaces advice from your own professional. Where a post describes a regulation, it's describing our reading of the primary document, which we link so you can go and read it yourself. Where a post talks about our own product or a competitor, our interest is obvious and we say so in the text.
Content built to rank in
Google and get cited by
ChatGPT
Perplexity
Gemini
Claude, with every claim checked before it goes live.