How we write
The blog is here to help you finish your book. This page says who writes it, how, and what to do when we get something wrong.
Who writes
Articles on this blog carry the byline “the Write in a Click team”. The team is the people who build Write in a Click: we choose what the blog covers, write the rules every article follows, and answer for what it says.
We write for authors working on a book, mostly around a job and a life. Each article tries to answer one question a writer actually brings, such as how to get past chapter one or how to revise a sagging middle.
How an article is made
Our team sets the topics and the questions. A language model drafts each article from that brief, following our brand book: plain words, no hype, and no promises we cannot keep.
Before anything is published, the draft must pass checks we wrote ourselves: length, structure, links, banned words, and a trace of every factual claim to its source. A second model reviews the draft against the brand book. A draft that fails is revised, and if it still fails it is not published.
Featured images are made by an image model and labelled as illustrations. We do not show them as photographs of real people or places.
A person does not read every article before it goes live. When we find something we would not have written ourselves, or a reader points it out, we change it or take it down.
Where claims come from
Facts about Write in a Click come from our own product pages and documentation. Numbers about other tools or about writing come with a source, or they are left out. We do not invent statistics, quotes or testimonials.
When an article compares Write in a Click with another app, it says so, and it links to the full comparison so you can judge for yourself.
Corrections
If an article is wrong, out of date or unfair to another product, tell us and we will fix it. Revised articles show the date they were last updated.
Write to success@writeinaclick.com with the article's address and what needs fixing. For how Robin works inside the app, see our transparency statement.
