A structural analysis report loses marks in predictable places — not because the calculations are wrong, but because the report doesn’t communicate them clearly. Here is the exact structure graders expect, and the mistakes that quietly cost the most marks.
Why the Structure Matters as Much as the Calculations
Two students can solve the exact same beam problem correctly and get very different grades, because a structural analysis report is graded on more than “is the final number right.” Markers are checking whether you followed a valid method, stated your assumptions, and presented results someone else could verify without redoing your work.
Treat the report structure below as non-negotiable scaffolding. Your specific analysis — a truss, a continuous beam, a portal frame — changes the content inside each section, not the sections themselves.
The Standard Report Structure
Section 1
Title Page & Abstract
The abstract is written last but read first — it should summarize the structure analyzed, the method used, and the key result in 100–150 words. A marker should be able to read only your abstract and know exactly what the report contains.
Include: structure type, span/loading, analysis method (e.g. moment distribution, stiffness method, software-assisted), and the headline result (max moment, max deflection, or governing member).
Section 2
Introduction & Objectives
State what structure is being analyzed and why. Then list explicit objectives — “determine the maximum bending moment,” “verify the structure against serviceability deflection limits” — as a short numbered list, not buried in prose.
This section also states your scope: what loading conditions you did and didn’t consider, and any simplifications you’re making up front.
Section 3
Methodology
Describe the analysis method itself — the theory, the assumptions, and the boundary conditions — before you show a single calculation. State material properties, support conditions, and load cases explicitly and in one place.
If you used software (STAAD.Pro, ETABS, a spreadsheet model), state the software, version, and what you verified manually to confirm the model was set up correctly. Markers specifically look for this manual verification step.
Section 4
Calculations & Results
This is the longest section, and where formatting discipline matters most. Every calculation should follow the same visible pattern: state the formula, substitute values, show the working, state the result with correct units.
Free-body diagrams, bending moment diagrams, and shear force diagrams belong here, each labeled and referenced by figure number in the surrounding text — never dropped in unexplained.
Section 5
Discussion & Conclusion
The discussion interprets the results — is the structure adequate, where does it govern, does the result make physical sense. This is where students lose easy marks by simply restating numbers instead of explaining what they mean.
The conclusion is short: does the structure pass or fail your stated objectives, and what would you check next (a different load case, an alternative member size) if this were a real design.
Figure & Table Formatting Conventions
Consistent labeling is one of the fastest wins available — it costs almost no extra time and markers notice immediately.
- Number figures and tables sequentially and separately: “Figure 1,” “Figure 2” / “Table 1,” “Table 2” — never reuse a number.
- Every figure needs a caption below it; every table needs a caption above it. State what it shows, not just a generic label.
- Reference every figure and table by number in your text — “as shown in Figure 3” — before or right after it appears.
- Keep units consistent throughout (kN, kN·m, mm) and state them on every value, not just the first one in a section.
Quick check before you submit: read your calculations section as if you know nothing about the problem. If a step doesn’t make sense without you explaining it out loud, it needs another line of working or a short note in the text.
Mistakes That Cost the Most Marks
|
1
|
Skipping stated assumptionsIf a marker can’t tell what you assumed (pinned vs. fixed support, self-weight included or not), they can’t verify your method — even if your arithmetic is perfect. |
|
2
|
Unlabeled diagramsA bending moment diagram without axis labels, units, or a figure number is unreadable to anyone but you — and unreadable work gets marked down even when it’s correct. |
|
3
|
No sanity check on resultsA deflection result that’s larger than the span itself is a red flag markers catch instantly. Always ask “does this number make physical sense” before writing it up as final. |
|
4
|
Writing the report after finishing all the calculationsWriting methodology and assumptions as you go — not after — keeps the report accurate to what you actually did, rather than a reconstructed version written under deadline pressure. |
Frequently Asked Questions
How long should a structural analysis report be?
Length depends entirely on the structure’s complexity, not a fixed page count. A single-span beam analysis might run 8–12 pages; a multi-story frame could run well beyond that. Prioritize completeness and clarity over hitting a target length.
Should I show every calculation step or just key results?
Show every step for the primary calculation path. For repetitive calculations (the same formula applied to multiple load cases), show one in full detail and present the rest in a summary table — that keeps the report readable without hiding your method.
Is it okay to use software results without manual calculations?
Most courses expect at least one manual hand-calculation to validate a software model, even if the bulk of the analysis is software-generated. Check your specific assignment brief, but including a validation check is rarely marked down and is often explicitly required.
Applying This to a Final Year Project?
The same structure and formatting discipline scales up directly into final year report writing — just with more chapters around it.