How We Write Guides and Comparisons

Calendox publishes this blog and is one of the two products in every comparison. Facts about other products link to their public source, a comparison is flagged for a re-check once its facts are 30 days old, and you can report an error to support@calendox.com.

Who publishes this blog?

Calendox publishes every post on this blog, under the name Calendox rather than a named author. Calendox is a calendar sync service for Google and Microsoft calendars, with Personal, Business and Enterprise accounts.

That matters most on our comparison pages. Each one compares Calendox with one other product, so the publisher is always one of the two products compared. Every comparison says so at the top and links to this page.

Where do the facts come from?

Facts come from public sources:

• Other products: the vendor's own website, pricing page, documentation and code repository, and its app store and marketplace listings. A few details, such as when a product's website address was registered, come from public records.
• Microsoft and Google: their own documentation, support articles and official blogs, such as Microsoft Learn, Microsoft Support, the Microsoft Tech Community blogs and Google Calendar Help.
• Calendox: our documentation, pricing page and other public pages, such as our provider pages.

Every statement about another company's product links to its source, in the text or under Sources. Statements about Calendox match our own pages, and link to them where it helps.

Where a statement is another company's own claim or position, the text attributes it, for example "Microsoft says". When a statement comes from a forum answer rather than official documentation, the post says who wrote it, such as a Microsoft Community moderator on Microsoft Q&A.

If a fact can't be confirmed from a public source, it's left out.

How are guides researched?

Every statement in a guide is checked against its source before the guide is published. Each guide answers one practical question, such as how to keep calendars in sync between two Microsoft 365 tenants. The checks come in three steps:

1. Microsoft and Google facts are checked. Each statement about their products is checked against their own published pages, such as documentation, support articles and official blogs, or an attributed answer on Microsoft Q&A. Those pages are linked in the text or under Sources.
2. Calendox facts are checked. Each statement about Calendox is checked against our documentation and pricing page.
3. Anything unconfirmed is removed. A statement that couldn't be confirmed, or that went further than its source, is dropped or reworded.

Guides describe built-in Microsoft and Google options as those companies document them, before explaining where Calendox fits. Diagrams and screenshots use made-up example people and companies, never real customers, and every fact an image shows is also in the text.

Are other products tested hands-on?

No, unless a page says so. Details about other products come from public sources, mostly what their vendors publish, not from our own trials.

A vendor's website can change after a page is published. That's why each of those facts links to the page it came from, so you can check the current version.

How is a comparison page built?

Every comparison follows the same order: an at-a-glance table, pricing scenarios, where Calendox is stronger and who it suits, and, at the end, a numbered list of sources.

At a glance

The table has the same eight rows on every page:

• calendars supported;
• sync directions;
• update speed;
• unified calendar;
• booking pages;
• team administration;
• Microsoft 365 tenant-to-tenant sync;
• trial.

Three rules apply to every row:

• Every row is filled in for both products, including rows where the other product differs from Calendox.
• Each of the other product's cells cites its numbered source.
• If a vendor's website doesn't mention a feature, the cell says it isn't listed there, not that the product lacks it.

Pricing compared

Prices are compared scenario by scenario, like for like:

• Each scenario names its unit: per user, per calendar, per sync or per pair.
• Both products are priced for the same quantity of that unit. A price per sync is never set against a price per calendar.
• Calendox prices are worked out from the same price list as our pricing page, so they can't drift from it. They're in US dollars, and taxes may apply by country.
• The other product's prices use the amount, currency and billing period the vendor lists, on its website or store listing, with a source. A price per unit is multiplied out to the scenario's quantity.

Where Calendox is stronger and who it suits

After the pricing, a comparison lists where Calendox is stronger and who Calendox suits. Each strength links to the Calendox page that shows it.

Because Calendox publishes these pages, they don't include a section making the case for the other product. The complete table and its sources are there so you can judge both products on the same facts.

Each comparison ends with its numbered Sources list, which the table and pricing cells cite.

How often are comparison facts re-checked?

A comparison is flagged for a re-check once its facts are 30 days old. The re-check then compares the page's facts, prices included, with their sources again.

• A new comparison is verified again before it's published if its facts are more than 14 days old by then.
• When a re-check changes what a page says, the page's Updated date changes.
• A re-check that finds nothing new leaves the date as it is.

How do you report an error?

Email support@calendox.com, or use our contact form. Please include:

• the page's address;
• what's wrong;
• a link to a public page that shows the correct information, if you have one.

We check each report against its source. If a page is wrong, we correct it, and its Updated date changes.

This applies to vendors too. If you work for a company we compare and a detail about your product is out of date, send us the public page that shows the current detail.