MC024-8.1 Report Content, Analysis Methodology, Conclusions, and Applicable Standards and Regulations

How to Write a Façade Calculation Report That Any Reviewer Can Trust and Reproduce

About This CPD

Join us for a technical CPD on writing a façade calculation report that survives review. This session opens with an uncomfortable truth: a flawless calculation can still be rejected — not because the number was wrong, but because nobody else could trace how it was reached.

Presented by Eugene Korch (IAST), this course is built around a single shift in thinking: a report isn't written for its author, it's written for the person who has to check it. Everything in a good report exists to carry your reasoning across that gap.

This course covers:

Who the report is really for — the one test every section has to pass: could a stranger follow this to your conclusion, on their own?
What a report must contain — the full spine of purpose, inputs, model and assumptions, method, result, and verdict, walked through a real report from title page to final figure
Leading with the answer — a results summary up front, with every condition that makes it true, and why every value needs a traceable source
The typical fragment — keeping a report complete without turning it into a book, and the one question that settles what belongs and what doesn’t
Presenting the analysis methodology — naming a method by what it does, making assumptions visible, and the reproducibility test that proves a methodology section works
Writing the conclusions — a verdict everyone reads, honesty about a thin margin, and how to state a non-compliant result and point toward the fix
Applicable standards and regulations — the two layers every report must keep apart — method and compliance — and how that split holds across Europe, the USA, and Australia

Using real report examples throughout, this CPD focuses on the one thing that decides whether good engineering gets accepted: can someone else check it?

What You'll Learn

Explain why a calculation report is written for the person who has to check it, not for the author, and apply that test to your own writing
Structure a calculation report as a complete, ordered story — purpose, inputs, model and assumptions, method, result, and verdict — with no step left for the reader to guess
Open a report with the identifying information a reviewer needs first, and lead with the headline result and the conditions attached to it, rather than making the reader hunt for the answer
Attach a traceable source to every material property, boundary condition, and dimension used in a calculation
Structure a repeating per-detail block so that one format serves every build-up in a report, however many there are
Present a result as a visible journey — from the model picture, through the driving parameter, to the final calculation table — rather than a number alone
Use the typical fragment as the unit of work in a report, so its length grows with the number of distinct build-ups, not the number of junctions on the façade
Judge the right amount of detail for a report using a single test: does this help someone retrace the reasoning?
Name an analysis method by what it does and justify why it fits the case, and make every assumption and simplification in a model visible
Apply the reproducibility test to a methodology section: could another competent engineer reach the same result from your report alone?
Write a conclusion that states a clear verdict tied to its criterion, in language any non-specialist reader can follow
Report a thin compliance margin honestly, and state a non-compliant result clearly, together with its consequence and a route to a fix
Distinguish a calculation method from a compliance code in a report, apply that two-layer structure across European, US, and Australian frameworks, and maintain a single, honest standards registry

Who Should Attend

Façade Engineers, Junior Façade Engineers, Architectural Technologists, Envelope Designers, Façade Specialist Contractors, Building Envelope Consultants, Project Managers, Design Managers, and Building Control / Approving Authority reviewers.

This session is designed for anyone who writes, reviews, or relies on a façade thermal or condensation calculation report — whatever software or method produced the numbers inside it.

Speakers

Eugene Korch

Programme Director, IAST

Eugene is a façade engineer and educator who leads educational initiatives through the Institute for Architectural Science and Technology (IAST) and Facade Intelligence, delivering training to construction professionals.

Course Schedule

Format: Online
CPD Points: 2 hours structured CPD / 2 Learning Units
Certificate: CPD certificate provided upon completion

MC024-8.1

Report Content, Analysis Methodology, Conclusions, and Applicable Standards and Regulations

How to Write a Façade Calculation Report That Any Reviewer Can Trust and Reproduce

Course Fee £120

Free for FI Pro Members

REGISTER AS INDIVIDUAL

REGISTER AS COMPANY

Pricing Options

Take advantage of exclusive savings with IAST Corporate Membership. If you are booking multiple places or using your IAST Corporate Member discount, please email corporate@iast.uk with the number of places required, your IAST Membership number (if applicable), and company details for invoicing. Alternatively, complete our group reservation form below. We aim to provide quotations within two working days after receiving the form.

Interested in becoming an IAST Corporate Member? Access exclusive discounts and benefits—visit our Membership Page to apply today.

Enhance your expertise with a Façade Intelligence Professional (FI Pro) subscription. Subscribe now at facadeintelligence.com. If you are already an FI Pro member and would like to use your discount, simply email our team at info@iast.uk to claim your benefits.

MC024-8.1 Report Content, Analysis Methodology, Conclusions, and Applicable Standards and Regulations

About This CPD

Join us for a technical CPD on writing a façade calculation report that survives review. This session opens with an uncomfortable truth: a flawless calculation can still be rejected — not because the number was wrong, but because nobody else could trace how it was reached.

Presented by Eugene Korch (IAST), this course is built around a single shift in thinking: a report isn't written for its author, it's written for the person who has to check it. Everything in a good report exists to carry your reasoning across that gap.

This course covers:

Who the report is really for — the one test every section has to pass: could a stranger follow this to your conclusion, on their own?

What a report must contain — the full spine of purpose, inputs, model and assumptions, method, result, and verdict, walked through a real report from title page to final figure

Leading with the answer — a results summary up front, with every condition that makes it true, and why every value needs a traceable source

The typical fragment — keeping a report complete without turning it into a book, and the one question that settles what belongs and what doesn’t

Presenting the analysis methodology — naming a method by what it does, making assumptions visible, and the reproducibility test that proves a methodology section works

Writing the conclusions — a verdict everyone reads, honesty about a thin margin, and how to state a non-compliant result and point toward the fix

Applicable standards and regulations — the two layers every report must keep apart — method and compliance — and how that split holds across Europe, the USA, and Australia

Using real report examples throughout, this CPD focuses on the one thing that decides whether good engineering gets accepted: can someone else check it?

What You'll Learn

Explain why a calculation report is written for the person who has to check it, not for the author, and apply that test to your own writing

Structure a calculation report as a complete, ordered story — purpose, inputs, model and assumptions, method, result, and verdict — with no step left for the reader to guess

Open a report with the identifying information a reviewer needs first, and lead with the headline result and the conditions attached to it, rather than making the reader hunt for the answer

Attach a traceable source to every material property, boundary condition, and dimension used in a calculation

Structure a repeating per-detail block so that one format serves every build-up in a report, however many there are

Present a result as a visible journey — from the model picture, through the driving parameter, to the final calculation table — rather than a number alone

Use the typical fragment as the unit of work in a report, so its length grows with the number of distinct build-ups, not the number of junctions on the façade

Judge the right amount of detail for a report using a single test: does this help someone retrace the reasoning?

Name an analysis method by what it does and justify why it fits the case, and make every assumption and simplification in a model visible

Apply the reproducibility test to a methodology section: could another competent engineer reach the same result from your report alone?

Write a conclusion that states a clear verdict tied to its criterion, in language any non-specialist reader can follow

Report a thin compliance margin honestly, and state a non-compliant result clearly, together with its consequence and a route to a fix

Distinguish a calculation method from a compliance code in a report, apply that two-layer structure across European, US, and Australian frameworks, and maintain a single, honest standards registry