For what it's worth there's also this 2016 document, Introduction to Reports and Theses. [0] It's clearly different, but the introductions in particular have a

For what it's worth there's also this 2016 document, Introduction to Reports and Theses. [0] It's clearly different, but the introductions in particular have a lot in common: From the IEEE version of A Guide to Technical Report Writing: > A good report is easy to recognise. Its title is precise and informative, its layout and format are well organised, and the binding is easy to handle and opens flat to reveal both text and diagrams. Reading a well written report is pleasurable: the style is accurate, fluent and concise, with headings to indicate the content of each section. The diagrams, which in this Guide will be taken to include non-verbal material such as tables and graphs, are well presented and clearly labelled. There are no absolute rules about the details of report production, because every report must be totally adapted to the needs of its reader. (The IET version is slightly different, for instance it does not mention document binding.) From Introduction to Reports and Theses: > A report is good when it is easy to recognize, title is precise and informative. The layout and format are well organized. The binding is trouble-free to handle and open. Reading a well written report is pleasurable, if, the style is accurate, fluent and concise, with headings to indicate the content of each section. There are no absolute rules about the details of report production, because every report must be totally adapted to the needs of its reader. [0] https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2775664 https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2775664 or https://dx.doi.org/10.2139/ssrn.2775664 https://dx.doi.org/10.2139/ssrn.2775664