Who is responsible for the site
BuildNumbers is independently developed and maintained by Hosyss. The public source repository and change history are available on GitHub so readers can compare published claims with the implementation and release record. BuildNumbers does not present itself as a substitute for an engineer, architect, building official, manufacturer, or material supplier.
What we publish
The site focuses on material quantity estimation: measured geometry, unit conversion, visible project allowances, product coverage or yield, and whole-package purchasing quantities. It does not choose structural dimensions, reinforcement, code requirements, product suitability, or site-specific safety decisions for the user.
Source hierarchy
BuildNumbers prefers primary or first-party technical sources whenever a published fact depends on an external reference. Unit definitions and conversions are checked against NIST resources. Product-specific yield, coverage, package volume, or similar values are tied to the relevant manufacturer data when those values are used as examples or defaults. Standards bodies, public technical agencies, and manufacturer technical documentation are preferred over unsourced summaries.
A source is used only for the claim it actually supports. A manufacturer yield does not become a universal material constant, and a unit conversion reference does not establish project design requirements. When products or regions vary, the user-controlled value remains visible instead of being presented as a universal rule.
Facts, defaults and assumptions stay separate
Calculator geometry and unit conversions are deterministic. Project allowances, waste percentages, material density, product coverage, package size, bag yield, and similar purchasing inputs can vary. Where a default is useful, BuildNumbers labels it as an adjustable planning value or a product-backed example rather than hiding it in the formula.
How calculator guidance is reviewed
- Define the supported geometry and exclusions before implementation.
- Check conversions and referenced values against the cited source.
- Keep the calculation engine separate from display formatting.
- Verify worked examples against independent hand-calculated vectors.
- Test metric and imperial equivalence, invalid inputs, and package-rounding boundaries.
- Run rendered-page checks for metadata, structured data, links, sitemap, and robots output.
- Record formula version, engine version, and review date on calculator pages.
Guide content is written to support a decision
A BuildNumbers guide should answer a concrete estimating question, show the measurement or formula sequence, explain which inputs change the result, include an example or reference table where it adds value, and state what must still be verified before purchase. The goal is not to create pages merely to target search phrases or increase page count.
Corrections policy
Reports are treated as evidence to investigate, not as permission to change a result without verification. A confirmed calculation defect is reproduced with a regression test before the engine is changed. The affected quality checks are rerun before release, and material changes are recorded in the public repository history.
If a reference changes, a product value becomes outdated, a worked example is wrong, or wording overstates what a calculator can decide, the published page should be corrected and its review date updated.
Advertising does not set the answer
Advertising status does not change formulas, calculator outputs, source selection, or the decision to correct an error. If advertising is enabled, it remains separate from the calculation result and does not turn a product-specific example into a recommendation. BuildNumbers does not sell a better calculation result to advertisers or suppliers.
How to challenge a result or source
Use the calculator issue form for a calculation, conversion, documentation, or usability concern. Include the calculator, the values you entered, the result you expected, and a source when you are disputing a referenced value. For general questions, use the contact page.