Auminer,
In the UK, BS8888:2002 "Technical Product Documentation(TPD) - Specification For defining, specifying and graphically representing products" is now the definitive standard for all Technical Documentation. However, it's not perfect and appears to overlook the written 'technical report' style document entirely, concentrating on drawings:
This standard cross-references EN ISO 128 "Technical Drawings" (in dozens of sections) and also BS EN ISO 3098 "Technical Product documentation - Lettering"
3098-0 Part 0 - TPD Lettering general requirements
3098-2 Part 2 - TPD Latin alphabet numerals and marks
3098-3 Part 3 - TPD Greek Alphabet
3098-4 Part 4 - TPD Diacritical and other marks Latin
3098-3 Part 5 - TPD CAD Lettering of the Latin alphabet
3098-3 Part 6 - TPD Lettering - cyrillic alphabet
Part 5 refers to the font for drawings which is the basis for Autodesks and others 'ISO' font.
This font provides excellent clarity but can make large documents look like 'first steps in reading' kids books because the font is so unmistakable.
Times Roman fonts are not good for the clear reading of mission-critical text. (They were, when originally created by the UK Times Newspaper 100 years ago, but then the priority was to create the maximum size with minimum surface area = minimum ink use) I can understand a Uni liking Times because it provides an old look to modern documentation and minimised toner use in printers.
For clarity and ease of recognition, I suggest you as a company standardise on a typeface as the basis for a 'house style'. Consistency in the appearance of documentation across a project is as important as the typeface used. It may sound beaurocratic, but half a day spent with project mamagers agreeing the format of text, titles and page layout can transform a big project from a load of disparate parts into a really superb cohesive whole.
I hope you can use some of these ramblings!
Regards,
Bob aka MadManxCadMan