Menu
OpsForge Quality Standard · v1.0
Trust should be inspectable.
OpsForge publishes the checks, limits, compatibility definitions, and support commitments behind its spreadsheet systems. The standard is designed to make product quality easier to verify—not merely easier to claim.
Current release evidence
A catalog-wide record, not a badge.
Snapshot reviewed August 23, 2026. Automated checks confirm file structure, formula preservation, named worksheets, guide sheets, and visible error conditions. They do not prove that a buyer’s quantities, rates, scope, or commercial judgment are correct.
The release gate
Seven requirements before release.
Purpose before polish
Every release must solve a defined estimating or operating workflow. A styled blank tracker does not pass the standard.
Inputs stay visible
Editable assumptions are separated from calculated outputs so an operator can see what drives the result.
Calculation checks
The populated model is scanned for visible spreadsheet errors and representative outputs are reconciled before release.
Controls and guidance
Validation, exception signals, sample data, operating limits, and user guidance must make the intended workflow understandable.
Usable outputs
The workbook must produce a useful decision view, printable output, dashboard, or controlled handoff—not merely store data.
Compatibility is qualified
Excel is the full-fidelity edition. Google Sheets-ready and Apple Numbers-ready files are verified as import-ready derivatives, not claimed to be pixel-identical.
Every release is accountable
A version, QA record, change history, support path, and defect-correction policy identify what the buyer can rely on.
Compatibility record
Three editions, three precise claims.
EditionRelease classificationWhat the record means
Microsoft ExcelFull fidelityThe original workbook experience, including the intended formulas, validation, conditional formatting, protection, charts, and print layouts.
Google SheetsImport-ready .xlsxA separate derivative preserves the source formula count, includes a Google Sheets guide, and passes a visible-error scan. Review controls and layout after import.
Apple NumbersImport-ready .xlsxA separate derivative preserves the source formula count, includes a Numbers guide, and passes a visible-error scan. Review controls, charts, and layout after import.
Estimate control
Better estimates require a closed loop.
The first OpsForge Estimate Control Companion is complete and entering the product-package rollout. It adds a readiness gate, assumptions register, estimate-versus-actual closeout, release record, and operating guidance around the core estimating workbook.
Open critical inputs prevent a “ready” result.
Every material driver gets a source, owner, confidence level, and downside.
Cost, labor, revenue, profit, and margin variances become a specific next-estimate action.
The companion is not yet listed as an included deliverable on a product page unless it has been added to that product’s download package.
Version and update policy
Changes should leave a trail.
- Every product record identifies the current version and release month.
- Confirmed file defects are corrected in a maintenance release or replaced at no additional charge.
- Maintenance notes describe material formula, control, compatibility, or documentation changes.
- Major redesigns, new integrations, and newly commissioned features may be separate paid releases unless the product page states otherwise.
- Users should preserve a clean original and compare release notes before moving live business data into a replacement file.
Support commitment
A defined response when the file is the problem.
- OpsForge targets an initial human response within two business days.
- A confirmed OpsForge file defect is corrected or replaced at no additional charge.
- For a reproducible blocking defect, OpsForge targets a workaround or correction within five business days.
- Support covers downloads, workbook navigation, documented behavior, and compatibility troubleshooting.
- Support cannot validate an estimate or provide legal, tax, accounting, engineering, code, or safety advice.
Response and correction times are operating targets, not guaranteed service-level agreements.
What the standard does not certify
The operator still owns the estimate.
OpsForge does not certify field measurements, labor productivity, supplier pricing, taxes, permits, code compliance, licensing, engineering, safety, contract language, client expectations, or whether a price is competitive. Sample assumptions are illustrative and must be replaced with current business evidence.
Check the record before you buy.
Every product page now links to a product-specific QA record with its version, package counts, compatibility classification, and release checks.