We frequently run into this requirement, client wants to see the "field datasheet" submitted with the project deliverable, usually as an appendix of the report. Some client's accept a feat. class/table dump into a single excel table, some don't. In reality, a compiled single table that's produced by dumping the feat. classes and tables in the service is MUCH more useful, but none-the-less some people still like to see the raw "field datasheet".
What's even more problematic is that clients often want the newly collected data to be recorded on their existing field datasheet PDF/Word template...ugh.
I usually end up designing a template datasheet "form" in Excel. Alternatively, you can use a pre-existing template word doc that's just as easy to fill. Then, dump all feat. class/table data to a single Excel workbook separated into various worksheets, perhaps one for each related table. Then with a VGA macro, I open the blank template Excel/Word file, SAVE-AS and populate it by looping over the Excel worksheet(s), then export to PDF. The end product looks exactly like, or close to the client's field datasheet, minus the wet paper tears, field mud and illegible scribbles.
But...a 'PRINT' button would sure be nice...hint hint ESRI....
To the OP, this probably isnt' what you were looking for, but is just how we've done it in the past. Once you setup the macro once, it's not that difficult to edit it for other projects. You'll find a lot of similarities, main data table, ancillary related tables (repeats), ect...
BTW, I'm sure you could do this with Python also, but then you'll likely run into having to hunt for modules that can consume MS files.