Last updated: 1 October 2026
What every tool exposes
A calculator should not hide the path from input to result. CivilKits keeps the load case or geometry, unit basis, formula, displayed result, and limitations together on the focused page. The home toolbox is for discovery; the focused page is where the assumptions should be read before a result is reused.
How the first-pass checks are verified
- Default examples are expressed as explicit regression calculations in the site verifier.
- Source pages are checked for required files, unique titles, valid local links, and dedicated calculator paths.
- The deploy build is checked for the worker entry point, static assets, hosting metadata, and directory fallbacks.
- High-consequence decisions still require an applicable code, project information, and qualified engineering review.
Source and update discipline
Where a relationship depends on a standard, official guidance, or a recognized engineering reference, the focused page should identify that basis. A simplified calculator is labelled as a screen rather than presented as a universal design rule. Corrections should include the tool name, inputs, expected result or source, and enough context to reproduce the issue.
Input provenance and calculation version
The calculation transparency panel distinguishes editable user inputs, CivilKits reset examples, calculated outputs and declared built-in model choices. A code factor is not automatically a code-defined project value merely because it is prefilled. Confirm the jurisdiction, standard edition, amendment state, National Annex and design situation. Clause and equation references identify existing implementation/reference material; they do not mean CivilKits has independently certified the complete standard or design.
For a project record, note the source and revision of each input: drawings or survey for geometry, reinforcement schedules, material test certificates, an analysis model and combination for actions, a geotechnical report for soil parameters, and the adopted rainfall/design basis and coefficient source for hydraulic work. Record who selected and checked the values, when they were checked, and the displayed implementation identifier. Calculator inputs remain in the browser; CivilKits is not a project-record storage system.
Reference content can be older than the applicable project standard. Where an exact clause or edition cannot be traced, treat it as requiring manual verification; do not substitute an assumed clause number. Check the licensed governing standard and complete all omitted checks independently.
Editorial and advertising boundary
CivilKits includes Google AdSense site-connection metadata and the configured advertising script on substantive calculator/reference pages and the interactive homepage. Navigation-only directories and site-information pages do not load that advertising script. Empty or under-construction content is not eligible for ads. The configured publisher identity matches the root ads.txt declaration. Script installation does not establish account approval, successful crawling or actual ad serving; Auto ads and site-review status are controlled in the publisher's Google account.
Google’s current guidance asks publishers to provide original, useful content and clear navigation before applying for AdSense. For users in the EEA, UK, or Switzerland, Google also requires a certified consent-management platform integrated with the IAB Transparency and Consent Framework when serving personalised ads. These are launch checks, not a claim of approval or legal compliance.
What this page does not promise
CivilKits implements bounded calculation models, not a complete design-code engine, professional appointment or certification service. It is not a substitute for complete project analysis and independent review. See the Terms / Engineering Disclaimer and Privacy page. A disclaimer does not guarantee freedom from liability.