A load takedown is only useful if you can hand it over, so exporting it well matters as much as computing it. StructLoads exports a takedown as a PDF report, an Excel schedule or a CSV file, each suited to a different next step. A good report carries the plan, the per-support load schedule and the governing reactions, with a clear preliminary-analysis disclaimer. This page covers which format to use and what the report should contain.
Three formats, three jobs
The right format depends on what the recipient does next.
| Format | Best for | What it preserves |
|---|---|---|
| Hand-over, client record | Layout, plan, tables, read-only | |
| Excel (xlsx) | Extending or re-checking | Editable schedule with the numbers |
| CSV | Importing into another tool | Raw rows, no formatting |
A PDF is the document of record because it is read-only and preserves the plan and tables exactly; for records that must stay readable for years there is even a constrained archival profile, PDF/A, which the Library of Congress describes as the ISO 19005 standard for long-term preservation of page-oriented documents. An Excel file lets the next engineer extend the schedule. A CSV is the plain-text option for importing the data elsewhere.
What a good report contains
Whatever the format, the report should let a reviewer follow and check every number.
- The floor plan with the supports marked.
- A per-support load schedule: tributary area, dead, live and roof loads.
- The cumulative service load and the governing factored reaction per support.
- The load combinations used and the units.
- A statement that it is a preliminary analysis for review by a qualified engineer.
That is the column load schedule, described in column load schedule explained, wrapped with the plan and the disclaimer.
Exporting from StructLoads
In the studio, the export menu offers PDF, Excel and CSV. The PDF includes an annotated plan drawing with the tributary zones and the reaction at each support, followed by the per-level tables, so it reads as a self-contained report. The Excel and CSV exports give one row per support with the load cases separated, ready to extend or import. The fast, checked workflow that produces these is in how to do a load takedown fast and check it.
Keep the load cases separate in the export
A good export keeps dead, live and roof in separate columns rather than pre-combined. That lets a reviewer re-apply the load factors, confirm the governing combination, and reuse the service loads for serviceability. A report that shows only a single combined number is hard to check and easy to mistrust, which defeats the point of exporting it.
Why the export matters for trust
The export is where the takedown meets other people: the foundation designer, the checker, the client. A clean, readable report with the plan, the schedule and the disclaimer builds confidence and speeds the hand-over, while a screenshot pasted into a document does not. This is part of why a dedicated tool beats ad-hoc methods, as set out in best load takedown software.
Key takeaways: exporting a takedown
Export PDF for a readable record, Excel for an extendable schedule, CSV for importing. Include the plan, the per-support schedule with separated load cases, the governing reactions, the combinations and a preliminary-analysis disclaimer. StructLoads exports all three directly. The export informs design but is not a final, stamped document, which a qualified engineer produces.
Quick answers
How do you export a load takedown report?
In StructLoads, open the export menu and choose PDF, Excel or CSV. PDF gives a readable report with the annotated plan and the load tables; Excel gives a schedule you can extend; CSV gives the raw rows for importing elsewhere. The export includes the per-support loads and the governing factored reactions, plus the disclaimer.
What format should a load takedown report be in?
Use PDF for a hand-over or client document, because it preserves the layout, the plan and the tables in a read-only file. Use Excel when the recipient needs to extend or re-check the numbers. Use CSV when another tool will import the data. Many workflows export a PDF for the record and an Excel or CSV for downstream use.
What should a load takedown report contain?
A good report contains the floor plan with supports, a per-support load schedule listing tributary area and the dead, live and roof loads, the cumulative service load and the governing factored reaction at each support, the load combinations used, the units, and a clear statement that it is a preliminary analysis to be reviewed by a qualified engineer.
When is an exported report not enough on its own?
It is not enough as a final design document. A takedown export is a preliminary gravity record; it does not include member capacity checks, lateral analysis, connection design or an engineer’s stamp. It informs and speeds up the design, but the responsible engineer must review it and produce the formal, code-compliant design documents.