Australia
Structural drawing member schedule and screening
Upload a DXF, PDF or IFC drawing, get a member schedule of beams, columns, slabs and footings, and run a completeness pass and StructByAI's own screening heuristics as a first pass before an engineer's own review. No member is checked against a standard, and nothing is reported as a pass.
- 5 StructCheck drawing parses, 3 screening runs and 5 exports per month
The problem
Reviewing structural drawings starts with bookkeeping: list every beam, column, slab and footing, read off its section, grade and span, and look for gaps. On a PDF set or a CAD file that takes hours, and it is where simple slips hide: a member with no grade, a footing with no site class.
A tool that pulls the members into one schedule and points at the gaps can speed up that first pass. It cannot do the review, and StructCheck does not check any member against a standard.
How it works
- Open StructCheck and upload a drawing as DXF, PDF or IFC.
- Optionally choose a soil class, applied to every member that doesn't carry its own. It is used only to tell whether a strip footing has a usable class recorded; nothing sizes or screens a footing with it. You can also choose an exposure class, but nothing uses it yet.
- Select Read drawing. From a DXF, it reads text labels and blocks that give a member mark or a section, on any layer not named for another discipline; linework with no label is reported, never turned into a member. From an IFC, the structural elements. From a PDF, an AI vision model sorts the pages: schedule tables are read from the PDF's text, drawing sheets from an image of the page.
- Review the member schedule. Each row shows its type, material, grade, section, span and how it was read. If a PDF has more pages than your plan reads, or a page could not be read at all, a warning says the schedule is incomplete.
- Select Run Screening Checks. A completeness pass flags a row with no grade, a strip footing with no usable soil class, and a concrete beam with no reinforcement detail. StructByAI's own screening heuristics then look at two things: timber depth against span, and long steel spans. They are the product's own rules of thumb, with no recorded source in any standard: a screening note is information only, names no standard or clause, and is neither a pass nor a fail. Concrete members and footings get no size screening at all.
- Every member is reported not checked, with the reason: no rule in this build is sourced from a standard. Nothing on the screen is a pass.
- Export the schedule as CSV, XLSX or PDF, with the notes if you ran the screen.
The screening is fixed code. AI reads PDF pages only, so one PDF can return different members on different runs, even a whole page.
Worked example
Illustrative inputs, not a real project: suppose the parse returned these four members, and you chose soil class M.
- B1, a steel beam, 360UB57, grade 300, 6 m span
- C1, a column, 150x300, grade N32, material not identified
- F1, a concrete strip footing, 300x500, no grade
- F2, a concrete strip footing, 200x300, no grade
The screen returns no errors. It gives two missing-grade warnings, for F1 and F2, and no screening notes: B1's span is short, C1's material was not identified, and footings get no size screening. All four members are reported not checked. An automated test runs these members through StructCheck's own code and fails if this result changes.
Silence on a member is not a finding that it is adequate. Next you would read the schedule against the drawing, add the missing grades, and design-check every member yourself.
What it doesn't do
- It is not a design check or a code review. No member is checked against AS 3600, AS 4100, AS 1720, AS 2870 or the NCC, and nothing checks strength, stability, deflection, connections or loads. It speeds up your review but does not replace it, and the engineer who signs the design remains responsible.
- It can miss members entirely. Members are read automatically and can be misread or missed. A member never extracted never appears as a problem.
- A screening note is not a finding. The heuristics are product rules of thumb, not requirements of any standard. Silence on a member means no heuristic applied or fired, nothing more.
- It reads common notation only. It recognises Australian section designations from a catalogue no engineer has verified, and usual block and layer names. Only a section family the catalogue lists sizes for is compared with it; a size outside that list is marked unverified. A family it lists no sizes for, including welded beams and columns (WB, WC), angles, hollow sections and purlins, is never marked unverified: at most its dimensions or mass are bounds-checked.
- Its results are advisory. Verify every row against the drawing and every requirement against the published standard.
Codes and standards our tools refer to
We refer to Australian Standards by name, designation and clause number only, and show none of their text, values or requirements. Our NCC 2025 entries are summaries of ABCB material published under CC BY 4.0. Buy the full text of a standard from Standards Australia. How we use standards.
- NCC 2025
- AS 3600 — Concrete
- AS 4100 — Steel
- AS/NZS 1170 — Loads
- AS 1720 — Timber
- AS 2870 — Footings
- AS 3959 — Bushfire
- AS 4055 — Wind
Questions engineers ask
Does a clean result mean the design meets the standards?
No. No rule in this build is sourced from a standard, so every member is reported not checked, never passed. The completeness pass and the screening heuristics only point at gaps and unusual sizes. They do not check strength, stability, deflection or connections, and the tool can miss members entirely. The engineer who signs the design is responsible for it.
Which file formats can I upload?
DXF, PDF and IFC. The size limits are 50 MB for DXF, 100 MB for PDF and 200 MB for IFC. Only the first pages of a long PDF are read, up to your plan's page limit, and a warning tells you when pages were skipped.
What does the screen actually run?
A completeness pass that flags a member with no grade, a strip footing with no usable soil class and a concrete beam with no reinforcement detail. Then StructByAI's own screening heuristics look at timber depth against span and long steel spans; concrete members and footings get no size screening. The heuristics are the product's own rules of thumb with no recorded source in any standard: each note is information only, names no standard or clause, and is neither a pass nor a fail.
Does it read scanned PDFs?
Partly. Drawing sheets are read from an image of the page by an AI vision model, so they don't need a text layer. Schedule tables are read from the PDF's text, so a scanned schedule gives nothing. Each row says how it was read, and the results should be checked line by line against the drawing.
What if it finds no members?
The drawing probably uses notation, block names or layer names the parser does not recognise. The parse still counts toward your usage, but running the screening checks on an analysis with no members is refused and not charged.
Related tools
- BAL record and AS 3959 pointers
- Wind region and wind specification for housing — AS 4055
- NCC 2025 code assistant for engineers
- AI engineering documents and certificates
- Desktop site screening for Australian projects
- Construction material checklist from site conditions
- Tender response writer for engineering consultancies
- Structural drawing review for Indian projects
Try it on your next job. Every output is a starting point for a qualified engineer to check.
Try it freeStructBy AI outputs are automated or AI-assisted and must be reviewed by a qualified, registered engineer before anyone relies on them. They are not professional engineering, legal or regulatory advice, and they do not replace a site inspection or a formal assessment. Our NCC entries are summaries of ABCB material, not the text of the NCC. Australian Standards are referred to by name, designation and clause number only; their full text is sold by Standards Australia. Verify every value and clause against the current published edition before you use it in design or documentation.