How We Review Software
Transparency matters. This page explains our evidence standard, current limitations, and how we handle corrections while older records undergo source review.
Quick Answer
PilotStack evaluates software using practical buyer criteria and vendor documentation. Some older numeric scores and review-count figures are still undergoing a source audit; they should not be treated as verified unless the page provides a checkable source and calculation. We omit unsupported claims as they are identified. Paid placements, where offered, are labelled separately and do not determine editorial ratings or rankings.
TL;DR
- Buyer-relevant criteria guide reviews and comparisons
- Numeric scores and review counts require a documented source and reproducible calculation
- A displayed update date does not mean every claim was rechecked
- Unsupported claims are corrected, qualified, or omitted
- Paid placements, where offered, do not influence editorial ratings or rankings
Key Takeaways
- Commercial placements are distinguished from editorial recommendations
- Consistent data is useful, but consistency alone does not prove a claim is sourced
- Scores are not presented as independent user ratings unless their provenance is documented
- Certification and company facts with no source should be omitted or labelled unverified
- Readers can report errors through the contact page
- Vendors cannot pay to change editorial scores or rankings
Readers reasonably want to know how tools are selected, how ratings are calculated, and how commercial relationships are handled. This page documents the process so readers can understand the context behind each score.
Our Five-Stage Methodology
1.Selection & Scoping
We select software topics based on practical buyer needs. Review pages discuss product fit, pricing considerations, feature availability, integrations, administration, and limitations. Some older records contain numeric scores or review counts whose source trail is still being audited; those figures should not be treated as independently verified until their provenance is documented. Commercial placements, where offered, are separate from editorial evaluation; payment does not determine editorial ratings or rankings.
2.Evidence & Sourcing
We prefer primary vendor documentation for product capabilities and pricing, and independent sources for third-party ratings or review counts. A stored value is not proof of sourcing by itself: the source URL, date checked, and relevant context must be recorded before a numeric claim is described as verified. Where sources disagree, we explain the uncertainty or omit the claim.
3.Scoring & Ratings
Numeric ratings are being audited for source provenance, consistent dimensions, and reproducible calculations. A score should be displayed as verified only when the evidence and calculation can be checked. Until that audit is complete, use the written criteria and vendor-confirmed facts rather than assuming that a stored number represents independent user sentiment or observed product outcomes.
4.Consistency & Limits
Content may be reused across reviews, comparisons, and recommendation pages, so corrections must be checked across every place a claim appears. A figure is not verified merely because it is consistent across pages. Certification statuses, ratings, review counts, and other unsupported facts should be omitted or explicitly labelled unverified until evidence is available.
5.Updates & Revisions
Software changes constantly. We update pages when pricing, features, or product positioning materially change, and correct claims when readers or our own audits identify problems. A displayed date alone does not prove that every claim on a page was rechecked on that date.
Scoring Rubric
The following dimensions are useful prompts for evaluating software. They are not a claim that every product has a verified numeric score; scores remain unpublished as verified until source evidence and calculation can be checked:
| Dimension | What We Measure | Evidence Status |
|---|---|---|
| Features | Confirm the capability in current vendor documentation and the plan being evaluated | Evidence first |
| Usability | Assess workflow fit with a representative task and clear acceptance criteria | Evidence first |
| Pricing | Check current regional pricing, billing terms, limits, and add-on costs | Evidence first |
| Support | Verify support channels, response commitments, and plan eligibility | Evidence first |
| Security | Check published controls, certifications, and scope directly with the vendor | Evidence first |
| Integrations | Verify required integrations and their plan or configuration limits | Evidence first |
| Performance | Use dated, reproducible evidence; do not infer performance from marketing copy | Evidence first |
| Documentation | Check current documentation coverage for the workflows you need | Evidence first |
| Scalability | Validate limits, administration, and cost at expected usage levels | Evidence first |
Fact-Checking & Corrections
We prioritize vendor documentation for capabilities and pricing, and independent source pages for external ratings and review counts. A source must be recorded with enough context to check the claim. If the source is missing, stale, or contradictory, we qualify or omit the claim rather than imply it is confirmed. When a correction is made, we update the page's review date where relevant. Readers can report errors via our contact form.
Editorial Standards & Byline
PilotStack publishes editorial standards for buyer-relevant criteria, source details, and corrections. Author pages identify the bylines used on the site; a byline alone does not establish that a product was tested directly or that the author has specialist credentials. Editorial roles are listed on our authors pages. Our published rules set expectations for buyer-relevant criteria, source details, and corrections. Older score and review-count data is under audit; a value repeated across pages is not independently verified merely because it is consistent.
Editorial Independence
PilotStack keeps editorial decisions separate from commercial relationships. Affiliate relationships and other commercial arrangements are disclosed where applicable. Paid promotional material, if present, is kept distinct from editorial reviews and comparisons. Our methodology describes the recorded sources and criteria used for editorial pages.
PilotStack may earn referral fees when readers click affiliate links and make purchases. These fees do not influence our reviews, rankings, or editorial content. Our affiliate relationships are disclosed in individual reviews and on our about page.
If you have questions about our methodology or believe an error has been made in a review, please contact us. We review all correction requests and publish clarifications when warranted.
Methodology last updated: October 22, 2026. This date records this page revision and does not mean every product claim across the site was rechecked on that date.