Editorial Methodology & Technical Source Policy
Our objective is useful, original concrete guidance that clearly separates authoritative project requirements from educational explanation and planning rules.
1. Primary sources first
For technical concepts, we prefer primary sources from organizations responsible for the relevant code, specification, test method, or material guidance. The core source set includes the American Concrete Institute, ASTM International, and the American Cement Association. When a page concerns a product-specific system, manufacturer technical data and the approved project submittal are the appropriate authority for that product.
We avoid treating blogs, social-media posts, AI summaries, forum anecdotes, or search snippets as a substitute for a recognized standard. Secondary sources may help identify a question, but the technical explanation is checked against primary material before publication.
2. Requirements are not the same as recommendations
A recurring source of bad construction advice is blending several document types into a single word such as “standard.” An adopted building code may be legally enforceable. ACI 318 is a structural concrete code commonly referenced by building codes. ACI 301 can be incorporated as a project specification. ASTM documents often define material requirements or test methods. ACI guides and reports provide recommendations and background. A project drawing can impose requirements specific to one structure.
Pages therefore use language such as required by the project, typical planning range, common field practice, or manufacturer-specific deliberately. If a value changes with code edition, member condition, exposure, or design, the site does not present one number as universally mandatory.
3. We do not reproduce copyrighted standards
ConcreteStandards.com explains concepts in original language and links to the official publisher. It does not reproduce full ACI, ASTM, ICC, or proprietary tables/procedures. This is both a copyright limitation and a technical-quality choice: extracting one paragraph from a standard can omit definitions, exceptions, scope, and referenced requirements that change its meaning.
4. Calculators expose assumptions
A calculator is useful only when a user can see what it does. Volume tools use ordinary geometry and show units. Bag quantities state the nominal yields used and tell users to check the actual product label. The rebar tool estimates quantities only after a design spacing is supplied. The joint-spacing planner labels the 24–36-times-thickness relationship as a planning rule rather than a code mandate.
We intentionally do not publish a “structural slab thickness calculator,” “footing size calculator,” or similar tool that would imply engineering from a few inputs. Those designs depend on loads, soil, reinforcement, geometry, and code conditions that cannot be responsibly reduced to a generic browser formula.
5. Troubleshooting is evidence-based
Concrete distress can have multiple causes. Crack pattern, timing, movement, location, weather, mixture records, support conditions, curing, exposure, reinforcement, and loading all matter. Troubleshooting pages describe what evidence to collect and what mechanisms fit the evidence. They avoid claiming that a photograph alone proves one cause.
When distress affects structural capacity, safety, active settlement, corrosion, post-tensioning, significant water containment, or major repair cost, the page directs the reader to qualified professional evaluation.
6. Review and update process
Each technical article includes a reviewed/updated date. A material update is warranted when the underlying source changes, an error is discovered, a tool assumption changes, or wording could cause a planning value to be mistaken for a requirement. Site architecture is designed so one corrected data record updates the page rather than leaving hundreds of copied articles inconsistent.
Old thin URLs consolidated during the 2026 rebuild redirect to the closest substantive guide rather than remaining online as near-duplicate search inventory. This preserves useful inbound links while keeping the index focused on pages with a distinct purpose.
7. Advertising does not define the technical answer
The site may use Google AdSense on substantive editorial pages. Advertising is separate from the technical content and does not determine recommendations, product selection, or conclusions. We intentionally suppress ads on search results, errors, and trust/legal pages where advertising would add little user value.
8. Reader responsibility
Use the site to understand terminology, plan questions, estimate material, and recognize when more information is needed. For a real construction decision, verify the adopted code, project drawings/specifications, inspection requirements, approved mixture/submittals, local weather/exposure, and product instructions. When professional design is required, use it.