I agree, having the summary and end or report would give our reports a much better first impression.

I'd recommend having 2 fields. Overview and Summary. Overview at front with whatever you want in it, Summary at the end, also with whatever you want in it. (or call it Summary and Appendix) Could be built with placeholders like the contract and boilerplate already have. Though in this case, placeholders would need to be tied to the report observations as well. In this instance, it would merge the current boilerplate and summary functions. It might look like:

Overview:

A home inspection is visual and not destructive

Words, words, words

The following observations provide a overview of all the observations noted during inspection. This helpful overview is not a substitution for reading the entire inspection report. The entire report must be read to get a complete understanding of this inspection report as the Summary Page does not include photographs or photo captions.

(Major Concern Placeholder)

(Repair Placeholder)

In my case, I'd personally make a "Chapter Summary" modifier for each chapter so I can consolidate multiple observations into 1 summary overview comment.

Personally, I like the summary at the start. But Home Inspector Pro, the software I was using before ScribeWare, did have an option to allow the summary to show at the start or the end of the report. I think it said something about the summary being required to be at the end in Texas (though I might be mis-remembering that.)

Not sure this matters…. Since everything is a click away…