Structural steel detailing, software, and resources—built together.

David Carne is the owner of Quantum Steel Design and has 32 years of steel-detailing experience. His work provides the practical context for a business that brings steel detailing, workflow software, and public learning resources together.

For a detailing conversation, start with the project scope, the current drawing issue, the required deliverables, and the people responsible for review. For a software conversation, describe the repetitive task and the information that must pass between tools. Those details make an initial discussion more useful than a software name or an estimated tonnage alone.

Use the published contact details to reach Quantum Steel Design. The services page explains typical deliverables; the Proof and Automation Lab separates inspectable tools and illustrative studies from completed client-result claims.

Quantum Steel Design publishes the site's original explanations, practical examples, and tool documentation. AI-assisted tools are used in drafting and software development. The steel shape reference pages are generated from the attributed AISC Shapes Database v16.0; their repeated layout lets readers compare the same fields across different sections.

An article should help a reader make a specific distinction, inspect an input, or follow a defined workflow. Worked examples are labeled as examples. Hypothetical portfolio studies remain labeled as fictional rather than presented as client projects. Source links identify the standards organization, software publisher, or dataset behind a technical reference so readers can check the applicable edition and original context.

The company byline identifies the publisher. It does not identify an independent technical reviewer or establish project-specific engineering approval. Website checks can verify calculations against test cases, working links, generated data, and browser behavior; they cannot approve a connection, construction method, or fabrication release.

To request a correction, send the affected page address, the statement or tool behavior in question, the source or edition you believe controls, and a non-confidential example if one is needed. Do not send private project drawings or customer information with an initial report. Substantive changes should update the relevant explanation and its review or modification date; a software release date alone is not a fresh technical review of every article.

Read the Trust Center for automation boundaries and the Privacy page for the distinction between local project data, website delivery, contact submissions, and optional Analytics.