Tregovia Editorial Policy: How We Verify Content

Editorial Policy: How We Verify What We Publish

This blog publishes buying guides, workflow templates, comparisons, and operational analyses for service businesses. Most of it is read by people making software and process decisions with real money attached. This page describes the standards every article is held to before it goes live - so you can judge for yourself how much weight to give what you read here.

The short version: claims are verified against primary sources, prices carry verification disclaimers because they change, numbers we didn't measure don't get published, and every quote is from a real person.

Feature Claims Are Checked Against the Product

When an article says Tregovia does something, that claim has been verified against the product's actual implementation - not against our own marketing pages, not against older articles, and not against what a feature's name implies.

In practice this means:

• Words like "supports", "includes", "automatically", and "tracks" are only used when the capability has been confirmed to exist and work as described.
• If a capability is partial, requires an add-on module, or depends on configuration, the article says so - including the module's price.
• If a capability doesn't exist, the claim is removed rather than softened. We have deleted claims from our own published articles for exactly this reason, and we treat those removals as corrections, not embarrassments.
• Claims about who can use a feature (staff, administrators, or clients) are verified before the article implies access.

Pricing: Ours from the Source, Theirs with Disclaimers

Tregovia pricing in articles comes from the live pricing configuration - the same source that bills customers. The base plan is EUR 47/month; module add-ons are stated with their individual prices whenever an article's total depends on them.

Competitor pricing is researched live at the time of writing, and every competitor price in every article carries a disclaimer to verify current pricing at the vendor's own site. This isn't hedging - vendor pricing genuinely changes without notice, regional pricing differs, and a comparison article that silently ages is worse than no article. We do not copy competitor prices from other blogs, from review aggregators, or from our own earlier articles.

Numbers We Didn't Measure Don't Get Published

Software marketing is full of suspiciously precise percentages. Our rule is simpler: an unmeasured number is not published as a result.

• When an early user reports an outcome qualitatively but no baseline was measured, our write-up says exactly that - see the "What We Can and Can't Claim" section in our veterinary clinic early-user story for what this looks like in practice.
• When an operator shares their own estimate - like the salon owner's no-show cost estimate in our no-show reporting-gap analysis - it is presented as their estimate, attributed as reported evidence, and never converted into a general performance claim.
• Industry statistics are used sparingly and framed as ranges, not precision we don't have.

Quotes and Stories Are Real, and Anonymity Is Honest

Every testimonial and user story on this site is from a real person, shared with permission. When someone asks not to be named or pictured, we attribute by role only - "Owner, small-animal veterinary clinic" - and state that the name is withheld on request.

What we will not do: attach invented names to real quotes, use stock portraits to imply real identities, or publish composite "customers" assembled from multiple conversations without saying so. Anonymized-but-real beats named-but-fake, every time.

Comparisons Are Written to Survive Us Losing

Comparison and alternatives articles follow three rules:

1. Both sides get their "when to choose them" section. Every comparison names the situations where the competitor is the better fit - marketplace discovery, US insurance billing, or whatever the honest answer is.
2. Our sections are labeled. Where an article describes Tregovia, it says explicitly that this blog is published by Tregovia and the section is our positioning, not neutral analysis.
3. The article should be useful to a reader who never becomes a customer. Methods like slot-based no-show counting or deposit policy design are explained so they work in any software, because that's what makes the article worth citing at all.

Scheduling, Updates, and Corrections

Articles carry their publication date, and future-dated articles are not visible until their date arrives. When facts change - a vendor reprices, a feature ships, a regulation moves - we update the article and its modified date rather than leaving stale claims standing.

When we find an error, we correct it. Substantive corrections that change an article's conclusion are noted in the text. If you spot something wrong, tell us at support@tregovia.com - a specific pointer to the sentence in question is the fastest path to a fix.

Why This Page Exists

Because "trust us" is not an argument. The standards above are checkable against the articles themselves: the disclaimers are visible in every comparison, the anonymized attributions are visible in every story, and the absence of invented percentages is visible everywhere. If you find an article that fails its own policy, that's a correction we want to make - and the fact that you can check is the point of writing the policy down at all.

Frequently Asked Questions

Who writes Tregovia's content?

Content is produced by the Tregovia team and published under organizational authorship. Regardless of who drafts a piece, every factual claim goes through the same verification standards described in this policy before it is published.

How are Tregovia feature claims verified?

Against the product itself. Before an article states that Tregovia supports a workflow, the claim is checked against the actual implementation - not against marketing copy, older articles, or assumptions from a feature's name. If a capability is partial or requires configuration, the article says so or the claim is removed.

Where does competitor pricing in comparison articles come from?

From live research at the time of writing, and every competitor price carries a disclaimer to verify current pricing at the vendor's own site - because vendor pricing changes without notice. We do not copy competitor prices from other blogs or from our own older articles.

Are the testimonials and user stories real?

Yes. We publish only real quotes from real users, shared with permission. When someone asks not to be named or pictured, we attribute by role only and say the name is withheld - we never substitute invented names or stock photos. Where results were not formally measured, our user stories say so explicitly instead of publishing invented percentages.

How do corrections work?

When we find an error - ourselves or via a reader - we correct the article and update its modified date. Substantive corrections that change an article's conclusion are noted in the text. You can report an error to support@tregovia.com.

Do comparison articles favor Tregovia?

Comparison articles are written to be genuinely useful even if you never use Tregovia: they include sections on when a competitor is the better fit, and every section describing Tregovia is explicitly labeled as our own positioning rather than neutral analysis. Where Tregovia doesn't cover a need - such as marketplace client discovery or US insurance billing - the article says so.