Calen Editorial Guidelines
Last updated 28 August 2026
1. Purpose and Scope
Calen publishes original content across two separate publications, plus our glossary and help resources, to help finance and engineering teams understand cross-border payments, tax compliance, and financial automation. Our Engineering blog is reserved strictly for engineering conversation: architecture deep-dives, API changelogs, and other technical writing aimed at developers and integrators. Our Blog covers everything else, including company news, product updates, and industry insights, aimed at a broader business audience. These guidelines set out the editorial standards our writers, engineers, and reviewers follow across both publications so that everything we publish is accurate, useful, and clearly attributable.
These guidelines apply to every piece of content published under the Calen name, whether written by an in-house engineer, a member of our product or marketing team, or an external contributor working with us.
2. Editorial Independence and Review
Our Engineering blog exists to document real engineering work, not to promote Calen beyond what is genuinely relevant to the topic at hand. Writers are free to describe technical trade-offs, limitations, and lessons learned honestly, including where a first attempt at a feature did not work as intended. Our Blog exists to share company news, product announcements, and industry perspective with a wider audience, and follows the same standard of honesty without assuming technical background.
Every article passes through review by at least one subject matter expert with direct knowledge of the topic before publication, and a second editorial pass to check clarity, structure, and tone. Articles that describe compliance, tax, or regulatory topics are additionally reviewed by our legal and compliance function before they go live.
3. Sourcing and Accuracy Standards
Factual claims about tax rates, regulatory requirements, or third party products are checked against the primary source, such as the relevant regulator's own published guidance, at the time of writing. Where a claim depends on information that changes over time, such as a tax threshold or a foreign exchange rate, the article notes the date the figure was accurate as of.
Content is written in plain, direct language and avoids unnecessary jargon. Where a technical or legal term is unavoidable, we explain it in context or link to our glossary.
4. Corrections Policy
If a reader identifies a factual error in a published article, we investigate promptly and correct the article as soon as the correction is verified. A material correction is noted at the top of the article along with the date it was made. Minor corrections, such as typographical fixes, are made without a formal note.
You can report a suspected error or ask a question about anything we publish by emailing editorial@calen.finance.