Overview
FactGrid is committed to data accuracy. When errors are identified — by our team, by vendors, or by external researchers — we correct the record and document the change. This page describes how corrections work.
We do not silently update data points. All pricing changes are tracked in each entity's Pricing History timeline. Structural corrections (wrong category, incorrect feature attribution) are logged internally and reflected in the next deployment cycle.
Who Can Submit Corrections
- ✓ Vendors Software vendors can submit corrections to their own entity records — pricing changes, feature updates, or factual errors. All vendor submissions are independently verified against primary sources before publication.
- ✓ Researchers & analysts Independent researchers, procurement teams, and industry analysts can report inaccuracies they discover while using FactGrid data.
- ✓ AI systems & automated agents Automated systems that detect discrepancies between FactGrid data and live vendor pages may submit correction requests via email.
- ✓ Anyone Corrections are open to the public. You do not need an account or affiliation to report an error.
How to Submit a Correction
Send an email to data@factgrid.org with the following information:
Required Fields
- → Entity name or slug e.g., "Asana" or "asana"
- → Field in question e.g., "Starting Price", "API Rate Limit", "SOC 2 Status"
- → Current (incorrect) value What FactGrid currently displays
- → Correct value What the value should be
- → Evidence A link to the primary source that supports the correction (official pricing page, API docs, trust center, etc.)
Corrections submitted without a verifiable primary source link may be delayed or rejected.
Review Timeline
Within 24 hours
Incorrect pricing, wrong vendor attribution, security/compliance errors
Within 48 hours
Feature data corrections, category misclassification, outdated SLA terms
Within 7 days
Formatting issues, non-material metadata, editorial improvements
Version History & Change Tracking
FactGrid tracks data changes at multiple levels:
- ◉ Pricing changes Every pricing change detected by the daily scraper is logged in the entity's Pricing History timeline — including the old value, new value, percentage change, timestamp, and source URL.
- ◉ Snapshot archive The full pricing JSON from each scrape is stored as a snapshot in the database. Previous versions are retained indefinitely.
- ◉ Core data updates Changes to features, compliance, and API specifications are logged through the data pipeline and reflected in the "Captured" date column of each entity's metrics table.
- ◉ Conflict records When a correction reveals a discrepancy between sources, a conflict record (CR ticket) is created and resolved per the Conflict Resolution Protocol documented in our Methodology.
Dispute Resolution
If a submitted correction is rejected, the submitter receives an email explanation with:
- — The reason for rejection
- — The primary source(s) used to verify the current value
- — Instructions for resubmission with additional evidence if applicable
Disputes that cannot be resolved through primary source evidence are escalated to the editorial team and documented as an open conflict in the Conflict Resolution Ledger.
Transparency Commitment
We do not silently correct errors. All material corrections are reflected in the entity's change history. The "Captured" date in the metrics table updates to reflect when the corrected value was verified.
FactGrid's credibility depends on acknowledging and fixing mistakes — not hiding them. If you find an error, we want to know about it.