AgileFever editorial standards: how we write and check our content

How We Write and Check Our Content: AgileFever’s Editorial Standards

Table of Contents

Written by the AgileFever editorial team. Last reviewed October 2026.

We sell training, and we also publish a lot of articles about it. That is a conflict of interest, and you should know how we handle it. This page explains how our posts are made, what we check before publishing, and what you can do when you think we got something wrong.

Short answer. Every post is written for a reader who is deciding something. Program facts such as price, hours and modules come from the live program page or our course catalog, not from memory. We say when we are reviewing our own product, label examples that are illustrative, and date our reviews.

What we check before a post goes live

Item How we check it What you will see
Prices Read from the course catalog on the day of writing US prices, and a note that additional discounts are available
Hours, modules, projects Compared with the live program page The same numbers as the page, or a note when the page disagrees with itself
Prerequisites Taken from the program page, not guessed A plain statement of what you need before you start
Third-party facts Taken from the provider’s own material where reachable; flagged when not “Confirm on the official site” when we could not verify
Examples and numbers Marked illustrative when they are not real data The word “example” or “illustrative”
Our own product Disclosed at the top of the post A line saying we run the program

What we avoid in new and updated posts

  • Job, salary or placement guarantees. We explain why in Why AgileFever doesn’t guarantee jobs.
  • Testimonials or case studies we cannot attach to a real person or company.
  • Statistics we cannot source. If a number has no source, it is left out.
  • Claims that a course will save you a set amount of time.

How a post is made

Step What happens
1. Pick the question We start from questions readers ask, such as which program fits a role, what it costs and what it covers
2. Gather facts We pull prices, hours, modules and prerequisites from the program page and catalog
3. Write The post answers the question first, then shows the detail, with tables where a table is clearer
4. Check Each number is compared with its source before publishing
5. Date it The post carries a review date
6. Re-check We look at search data about four weeks later and update posts that are out of date or not helping readers

Additional discounts are available. Contact us to know more.

How we handle our own programs

When a post compares our program with another option, we say what the other option does well, and who should choose it. Several of our posts include a section on who should take something else, because a reader who joins the wrong program is a worse outcome for everyone than a reader who leaves for a better fit.

Corrections

If you find an error, a price that has changed or a claim that does not match the program page, tell us through the contact page. We will check it against the source and update the post, with a new review date.

What this page is not

It is not a guarantee that every post is free of mistakes. Programs change, and the page and the catalog are the final word. When a post and a program page disagree, trust the program page and let us know.

AgileFever

Contact Us

    By checking the box, you consent to receive registrations, class reminders, updates, support text messages from AgileFever at the provided number. Message and data rates may apply. Message frequency varies (typically 1–2 msgs/week). To end messaging from us, you may always reply with STOP. You may also reply with HELP for more information. Check Privacy Policy and Terms & Conditions.