Hi, Lee_M
thanks for interesting question.
TestComplete has two kind of results representation: ordinary log (which is more technical and mostly need to understand the cause of test failure) and summary (it contains high-level info about pass/failed scenarios).
If you need to show some high-level report for your boss, I'd recommend to use Summary representation (and it can be exported as JUnit and exported in some test reporting system, or just printed as PDF).
Also the next step can be to put the test set in some test orchestration system: Zephyr, AzureDevOps, or Jenkins (which is free to use).
It can give you merged report, scalability, different kind of representations and historical data.
Here some screenshots from Jenkins:
It stores also the "technical" logs, so, you can always can see them and it can options to clean the storage by scheduler.
Another thing which I like in Summary, that you can add all test cases / scenarios which you discussed with you boss or dev. And automate it one by one, and before non-automated-yet test cases just put Runner.Stop() - all the test cases which are not automated will be in Unexecuted group.
So, you boss can see in report the progress - how many tests already automated and what is in backlog. The technical details is usually not so important for management.
There is also another way to present trends with your tests in Jenkin's. We use an extension called 'Plots', that in our case, we use to graph page load times daily/weekly.
