Our Editorial Policy explains how ConcreteCreek.com researches, writes, reviews, updates and corrects concrete calculators, conversion tools, construction guides, cost pages and educational content. Our goal is to make technical information useful, transparent and easy to verify.
Concrete construction combines arithmetic, material science, local standards and real-world workmanship. We aim to explain those topics without pretending that a web page can replace project drawings, supplier data, qualified testing or professional engineering where those are required.
We check formulas, units, factual claims and worked examples before publishing or materially updating a page.
Where practical, we prefer standards bodies, government agencies, manufacturers and original technical documentation.
Calculators and guides should state the assumptions, units, limitations and conditions that materially affect the result.
Commercial relationships should not determine conclusions, formulas, safety guidance or source selection.
When we find a meaningful error, we aim to correct it promptly and update the affected explanation or calculation.
Pages can be revisited when standards, product information, pricing, local rules or best-practice guidance changes.
Our editorial workflow is designed to move from topic definition to research, drafting, verification, publication and later review. The exact process can vary by page type, but the same core principles apply.
These principles apply across calculators, conversions, guides, city pages, cost content and policy pages.
Technical claims should rely on credible references, especially where standards, safety, materials or regulation are involved.
Formulas should be explainable, units should be explicit and defaults should not silently change the meaning of a result.
High-consequence topics should distinguish educational guidance from professional engineering, legal or safety decisions.
Search optimisation should help users find useful content, not justify repetition, keyword stuffing or misleading claims.
Time-sensitive material such as local standards, costs and product information should be reviewed when accuracy may have changed.
We aim to separate editorial judgment from advertising, affiliate relationships and commercial incentives.
ConcreteCreek.com publishes concrete calculators, quantity estimators, conversion tools, cost explainers, construction guides and educational reference pages. Because these topics combine mathematics with changing products, standards, supplier practices and local requirements, our editorial process focuses on two things at the same time: making information easy to use and making the assumptions behind it visible.
We do not treat every page as the same kind of content. A millimetres-to-metres conversion is based on a fixed unit relationship. A concrete-cost guide can change with location and time. A reinforcement guide may depend on current standards. A calculator can produce exact arithmetic from inputs while still being only an estimate of a real construction project. Our review process is intended to reflect those differences.
Our goal is not to publish the longest possible answer. We prefer a shorter, accurate explanation over a longer page filled with unsupported assumptions. Where a topic benefits from detailed treatment, we add examples, tables, troubleshooting, FAQs and related context—but those additions should remain relevant to the user's question.
We check numerical relationships, units, example arithmetic and formula logic before publication. When a page includes multiple unit systems, we try to keep conversions consistent rather than mixing rounded and exact values without explanation.
For technical concrete topics, we generally prefer information from standards organisations, government agencies, professional institutes, established trade associations, manufacturers and original product documentation. Examples can include ACI, ASTM, NIST, Safe Work Australia, state workplace-safety agencies, local councils and product manufacturers.
Secondary articles can still be useful for context, but they should not replace a more authoritative source when the primary material is available and understandable.
A source can be reputable yet still be irrelevant to a particular statement. We aim to use sources that directly support the claim being made. For example, a general concrete handbook is not automatically the right source for a current council footpath thickness requirement. A council's own current standard drawing is more appropriate for that claim.
Some information is highly stable. One metre equals 1,000 millimetres. One cubic yard equals 27 cubic feet. Other information changes. Building rules, workplace guidance, standards editions, product specifications, supplier yields and material prices can all be revised.
Pages containing changing information should be reviewed against current sources when they are updated. We avoid presenting time-sensitive claims as timeless facts.
A conversion calculator can be mathematically exact if the source measurement is exact. A construction estimator is different. Concrete volume, bag count, material cost, delivery cost, waste and reinforcement quantities are affected by real-world variables.
Our calculators should clearly identify whether the result is a mathematical conversion, a geometry calculation or a planning estimate. They should also make significant assumptions visible rather than hiding them in code.
Where possible, we avoid pre-filling numeric fields with values that could accidentally become part of the user's entry. A faded placeholder can show the expected format without inserting a real value. We also avoid silently selecting calculation-changing defaults where a user choice is required.
If a density, product size, bag yield, waste percentage or price materially changes the answer, the calculator should either request the value or clearly identify the default assumption.
Concrete calculators are useful for planning, budgeting and checking arithmetic. They do not perform structural engineering unless explicitly designed and validated for that purpose. A volume calculator cannot determine reinforcement. A slope calculator cannot certify accessibility compliance. A concrete weight estimate cannot replace an engineered lifting plan.
Where the consequences of error are high, we state the limitation and direct readers to project drawings, qualified professionals, suppliers, laboratories or authorities as appropriate.
For common calculators, readers should be able to understand the core mathematical relationship. A slab-volume page may explain length × width × thickness. A cylindrical post-hole page may explain πr²h. A unit converter should show the conversion factor.
Showing the formula makes the calculator easier to audit and helps users catch incorrect inputs. We do not believe a result should appear as unexplained “magic.”
Examples are intended to teach, not merely decorate the page. A reader should be able to repeat the arithmetic using the stated inputs and get the same result within the stated rounding. If an example includes waste or a product yield, that assumption should be visible.
A calculator can display many decimal places, but that does not make a rough site measurement more accurate. When inputs are approximate, results should be interpreted accordingly. We may retain additional decimals internally for calculation while displaying a more practical rounded result.
Concrete density, strength development, bag yield, coverage, curing time, pricing and decorative appearance can vary. Where variability is meaningful, we try to explain what drives it instead of presenting one number as universal.
This is especially important for supplier-dependent information. A generic bag-yield assumption should never override the yield printed on the exact product being used.
Location-specific content should not simply replace one city name with another. If a page discusses a current permit, council standard, driveway rule, local path thickness or state workplace requirement, we prefer to support it with the relevant authority's own current material.
Where no reliable local source is available, the page should avoid inventing a rule. General guidance can still be useful, but it should be described as general.
Concrete prices can vary with location, project size, concrete strength, additives, short-load fees, access, pumping, labour, reinforcement, excavation and season. Cost pages should not present a single number as a guaranteed quote.
When we provide example ranges, they are planning references. Readers should obtain current supplier and contractor quotes for project decisions.
Concrete standards are technical documents with scope, definitions and measurement procedures. We avoid taking a number from a standard and applying it outside its intended context. When a standard edition matters, we aim to identify the edition or current listing rather than referring vaguely to “the ASTM standard” or “ACI says.”
Standards organisations publish copyrighted technical documents. We may summarise a requirement or explain what a standard covers, but we do not reproduce entire standards, tables or long copyrighted passages. Readers who need the full requirements should consult the official publication.
Concrete work can involve silica dust, cement burns, heavy loads, powered equipment, pressure washing, chemicals, reinforcing steel and working around vehicles. Safety guidance should not encourage shortcuts or imply that personal protective equipment alone makes a hazardous process safe.
Where current workplace rules or product safety instructions apply, we prefer official safety sources and manufacturer safety data.
Old coatings can contain lead. Grinding concrete can generate respirable crystalline silica. Paint strippers can contain hazardous solvents. We aim to identify these possibilities where relevant and recommend checking current safety guidance before beginning work.
ConcreteCreek.com is an educational website. Regulations, permits, workplace duties and engineering approvals can depend on jurisdiction and project details. General content is not legal advice, engineering certification or a permit determination.
We link to related ConcreteCreek pages when the next step is genuinely useful. A sidewalk-thickness guide may link to a concrete-volume calculator because quantity depends on thickness. A wire-mesh guide may link to reinforcement calculators. We avoid adding unrelated links solely to increase internal-link counts.
Where practical, external references point readers toward the source behind the claim. We prefer direct pages from standards bodies, government agencies, councils and technical organisations rather than generic homepages when a specific source is available.
We use descriptive titles, headings, FAQs and related terminology so readers can find the content they need. We do not intentionally change a technical conclusion simply because a different answer may attract more search traffic.
Keywords should fit naturally. Repeating the same phrase excessively makes the page harder to read and does not improve the underlying information.
Our pages are written to explain the topic in our own structure and language. Sources are used to support facts, not to copy their prose. Tables, examples and figures are created to make the specific ConcreteCreek page easier to understand.
Illustrations are used when they help explain geometry, layer relationships, installation mistakes, unit conversion or process flow. Figures should fit within their visual container on desktop and mobile and should not place important labels outside the visible area.
Technical tables can be wider than a phone screen. We use responsive wrappers so readers can scroll horizontally rather than forcing columns to become unreadably narrow. Descriptive columns are normally left aligned while numeric columns remain easy to compare.
When a page is intended as a guide, we do not add a calculator simply because the site contains calculators elsewhere. A guide about paint removal, concrete strength, decorative concrete or wire mesh can remain purely educational. Related calculators can be linked separately when useful.
Editorial, privacy, advertising, corrections and methodology pages should focus on transparency. They do not need decorative calculation widgets that distract from the policy itself.
Modern editorial workflows may use software tools, including AI-assisted drafting, rewriting, outlining, coding or quality checks. When such tools are used, they do not replace responsibility for the published result. The content still needs human-directed review for accuracy, relevance, structure and site standards.
AI-generated factual claims should not be treated as sources. Technical claims should be checked against reliable references. Calculator code and arithmetic should also be tested rather than trusted simply because software produced them.
When a calculator is created or materially changed, we aim to check its formulas with known test cases, verify unit conversions and confirm common input behaviours such as reset, hidden results and mobile entry. Code syntax checks can help catch errors, but they do not replace formula validation.
A harmless display default is different from a hidden calculation default. We consider whether a preselected value could cause a user to receive a plausible-looking but unintended answer. When a choice materially changes the result, asking the user to select it may be more transparent.
ConcreteCreek.com serves readers who may use metric, U.S. customary or mixed units. We try to label units explicitly and avoid ambiguous terms such as “ton” without indicating whether we mean a U.S. short ton or metric tonne when the distinction matters.
Where the site addresses Australian users, we generally use spellings such as metres, litres and tonnes and refer to relevant Australian authorities when the topic is location-specific. Some calculators also include U.S. customary units because construction information often crosses markets.
When a rule or standard may change, using a specific edition or publication date is clearer than saying “currently” without context. If a page is revised after a new standard appears, we aim to update both the claim and the reference.
If a result depends heavily on density, waste allowance, product yield, structural design, site measurement or local code, that limitation belongs near the relevant content—not only in a footer.
A disclaimer cannot turn inaccurate content into acceptable content. We still aim to research and verify what we publish. Disclaimers explain the boundary between general educational information and project-specific professional decisions.
If ConcreteCreek.com receives compensation through advertising, sponsorships, affiliate links or commercial partnerships, that relationship should be disclosed where relevant. Commercial arrangements should not secretly determine the technical conclusion of a page.
If sponsored content is ever published, readers should be able to distinguish it from independent editorial material. Sponsorship does not grant the sponsor permission to rewrite technical conclusions or remove necessary safety context.
A manufacturer or product may be referenced because its technical documentation provides a useful example, yield or procedure. Mentioning the product does not automatically mean ConcreteCreek.com endorses it for every project.
A company should not be able to pay to make an unsafe material appear safer, a lower-performing product appear technically superior or a standard requirement disappear from the page. Editorial integrity requires separating commercial payment from technical conclusions.
Reader feedback can reveal unclear formulas, missing scenarios, broken links, regional differences or interface problems. We may update a page when feedback identifies a real improvement. A user suggestion is evaluated rather than automatically accepted.
If you believe a ConcreteCreek page contains an incorrect formula, outdated standard, broken link, misleading statement or calculation bug, we encourage you to report it. The most helpful reports include the page URL, the disputed statement or calculation, and a source or example showing the problem.
If a calculator uses the wrong conversion factor, correcting only the explanatory paragraph is not enough. The code, examples, tables, PDF output and schema may all need review. We aim to correct the affected system rather than only the most visible sentence.
Spelling, punctuation, formatting and wording changes may be made without a formal correction note. A material correction changes the meaning of a technical claim, formula, legal/safety statement or result. Material corrections deserve greater care and may justify an update note depending on significance.
Technical organisations can move pages, revise URLs or replace standards. During page updates, we may check whether important source links still work and whether the cited material remains current.
Sometimes an older standard or rule remains useful for explaining a historical project. In that case, the content should make the older status clear rather than presenting it as the current requirement.
Any cost example is educational. Actual supplier prices, contractor labour, delivery fees, pumping, access, reinforcement, excavation, disposal and tax can differ substantially. Readers should request current local quotes before making purchasing decisions.
If reliable current local pricing is unavailable, we would rather provide a transparent estimating framework than fabricate a city-specific number. Regional differences can be discussed qualitatively when the evidence supports them.
Concrete content can intersect with legal permits, occupational health, insurance, contracts and property decisions. We keep the focus on concrete information and identify when readers should seek the appropriate licensed professional or authority.
Foundation depth, reinforcement, suspended slabs, retaining walls, lifting, load capacity and structural alterations are high-consequence topics. General guides can explain concepts, but project-specific design should come from qualified professionals and approved documents.
Durability, permeability, air content, curing, jointing, thickness, reinforcement, support and exposure can matter as much as compressive strength. Editorial content should avoid oversimplifying concrete quality into one PSI or MPa number.
Common practices vary between countries, states, councils, suppliers and project types. A familiar residential rule of thumb may not apply to public infrastructure, structural concrete or a different climate. We try to identify the context around rules of thumb.
| Page Type | Main Review Focus | Typical Source Priority | Main Limitation To State |
|---|---|---|---|
| Unit Converter | Exact factor, direction, units, rounding | NIST / SI references | Does not improve measurement accuracy |
| Concrete Volume Calculator | Geometry, units, waste logic | Mathematics + product/supplier context | Site dimensions and overbreak vary |
| Bag Calculator | Manufacturer yield and whole-bag rounding | Product technical data | Yields vary by product and conditions |
| Cost Guide | Currentness, location, included scope | Current supplier/contractor/public data | Not a quote |
| Construction Guide | Process, safety, standards, limitations | ACI, ASTM, government, manufacturer | Not project-specific instruction |
| Local Standard Page | Current authority requirement | Council / agency primary source | Rules can change by location |
| Policy Page | Transparency and consistency with site practice | ConcreteCreek internal policy | Policy may evolve |
There is no perfect hierarchy for every topic, but our preference generally follows the nature of the claim. A current law should come from the responsible government source. A concrete test method should come from the standards organisation. A bag yield should come from the product manufacturer. A local footpath requirement should come from the council.
| Source Type | Common Use | Strength | Editorial Caution |
|---|---|---|---|
| Government / regulator | Rules, safety, public infrastructure | Authoritative for jurisdiction | Check date and scope |
| Standards organisation | Test methods, specifications | Technical authority | Full standards may be copyrighted/paywalled |
| Professional institute | Design and construction guidance | Industry expertise | Guide vs mandatory code must be distinguished |
| Manufacturer | Yield, coverage, installation, product data | Best source for its product | Not automatically neutral across products |
| Trade association | Industry practice and education | Specialised knowledge | Confirm claim matches scope |
| Secondary publication | Context and explanation | Can be accessible and useful | Verify technical claims where possible |
Editorial independence means the answer should follow the evidence and the page's purpose. If a sponsor prefers a claim that conflicts with a reliable technical source, the reliable source should win. If an affiliate product is not suitable for the stated use, commercial value should not change that conclusion.
Advertising can support a website financially, but it should remain distinct from technical content. Ads do not determine calculator formulas, source selection, safety notes or editorial rankings. For additional detail, readers can also review the site's Advertising Disclosure where available.
If affiliate links are used, ConcreteCreek.com may earn compensation from qualifying purchases. The existence of an affiliate link should not change the underlying explanation. Where we compare products, the criteria should be relevant to the use case rather than designed solely to maximise commission.
When we discuss a product category, we aim to identify the criteria that matter—such as yield, compatibility, exposure, safety instructions or technical properties. We do not represent marketing claims as independent testing unless we actually have independent test evidence.
We want readers to be able to trust that identified mistakes are addressed. When a material error is confirmed, we aim to correct the page promptly. Depending on the issue, this may include revising text, calculator logic, examples, tables, figures, links or downloadable outputs.
Minor spelling or formatting changes may be made silently. Meaningful technical corrections may be accompanied by an updated date or correction note when that improves transparency.
When contacting ConcreteCreek.com about a possible error, please include the page title or URL, the sentence or result you believe is incorrect, why you believe it is wrong, and any reliable source or worked example that supports the correction. Detailed reports are easier to verify and act on.
Not every page needs constant revision. Stable unit conversions can remain correct for years. Time-sensitive content deserves more frequent review. We may update pages when standards are revised, links break, authorities publish new requirements, manufacturers change product data, or reader feedback reveals a meaningful issue.
A page's update date should reflect a meaningful editorial review or material revision rather than a trivial automated timestamp change. Cosmetic site-wide changes do not necessarily mean every factual statement was re-researched on that date.
ConcreteCreek.com may use AI-assisted tools to support drafting, editing, structure, coding, data checking or content operations. AI output is not treated as an authoritative source. Technical facts, current standards, legal/safety claims and formulas should be checked independently before publication.
Where AI assists calculator code, the code should still be tested with known inputs. Where AI assists prose, the content should still be reviewed for relevance, unsupported claims, contradictions and misleading certainty.
We aim to publish original explanations rather than copy the structure or wording of another website. Technical facts can be shared across many sources, but the way they are explained, organised and illustrated should be original to ConcreteCreek.com.
Figures should be original, licensed or otherwise used appropriately. Diagrams created for ConcreteCreek are intended to explain concepts such as reinforcement position, conversion relationships, slab layers or process steps. They should not falsely imply engineering approval.
Feedback submitted about content should be handled consistently with the site's Privacy Policy. We do not need sensitive personal information to investigate a technical correction. A page URL and description of the issue are usually enough.
Writers or reviewers should avoid undisclosed conflicts that could materially influence a technical recommendation. If a commercial relationship is relevant to the content, disclosure helps readers evaluate the context.
If ConcreteCreek.com accepts guest contributions, the content should meet the same editorial standards as internally produced material. Publication is not guaranteed simply because a contributor is an industry professional or represents a company.
Some high-consequence topics may benefit from review by qualified engineers, concrete technologists, safety professionals, contractors or other specialists. If expert review is specifically claimed on a page, that claim should identify the nature of the review rather than imply a review that did not occur.
This policy may evolve as the site grows, publishing tools change or editorial workflows improve. Material changes may be reflected in the page's updated date. The central principles—accuracy, transparency, useful sourcing, clear limitations and corrections—are intended to remain stable.
Readers may also want to review the Methodology, Privacy Policy, Advertising Disclosure, About Us and Contact Us pages where available. Together, these pages explain how ConcreteCreek.com operates, handles information and distinguishes editorial content from commercial activity.
A useful page should pass more than a spelling check.
Do formulas, units, claims and examples match the best available evidence?
Can a reader understand the assumption, limitation and next step?
Could the rule, standard, product data or price have changed?
Does the page help a real decision without overstating what a website can determine?
Answers about sourcing, updates, corrections, AI assistance and editorial independence.
We aim to verify formulas, units and factual claims against reliable sources and test calculator logic with known examples before publication or major revision.
We generally prefer primary and authoritative sources such as government agencies, standards organisations, professional institutes, councils and manufacturer technical data.
Pure unit conversions can be mathematically exact, but construction estimators depend on measurements, assumptions, waste, product yield and site conditions and should be treated as planning estimates.
It should not. Commercial relationships are intended to remain separate from formulas, technical conclusions, source selection and safety guidance.
AI-assisted tools may support drafting, editing, coding or quality checks, but AI output is not treated as a source and should be reviewed and verified before publication.
We aim to compare calculator outputs with known test cases, verify unit conversions and review code behaviour such as reset, inputs and result formatting.
Update frequency depends on the topic. Stable unit conversions may need little change, while local standards, safety guidance, prices and product data deserve more frequent review.
When a material error is confirmed, we aim to correct the affected text, calculation, table, figure or downloadable output as appropriate.
No. Minor spelling or formatting changes may be silent. Significant technical corrections may receive an updated date or correction note when useful.
Our editorial policy is that commercial relationships should not override reliable evidence, required safety context or accurate technical conclusions.
Yes. Manufacturers are often the best source for their own product yield, coverage, installation and technical data, though their claims are not automatically neutral comparisons across competing products.
Those links help readers verify standards, safety guidance and technical claims using authoritative primary sources.
Yes. Reports are most useful when they include the page URL, the disputed statement or result and a reliable source or calculation showing the issue.
Search optimisation helps readers find pages, but it should not determine formulas, standards, safety advice or technical conclusions.
No. This is a policy page only and intentionally contains no calculator, input fields or results section.
Editorial standards work together with methodology, advertising, privacy and correction practices.
Explains how calculations, formulas, assumptions and data sources are selected and presented.
Read MethodologyExplains how advertising or commercial relationships are separated from editorial decisions.
Read Advertising DisclosureExplains how information associated with site use and communications is handled.
Read Privacy PolicyLearn more about the purpose of the site and the kinds of concrete tools and guides we publish.
Read About Us