Define what are you responsable of. Make a list. I am not talking about "taste or style".
Normally you are NOT responsable of:
1) Any kind of orthography or redaction issues.
Make that very clear.
The client must provide you with a written authorized file with the text. You can charge an aditional fee if he modifies this text after.
2) Resolution of images provided by the client.
We are talking about images of an event, some machine, etc, that can not be taken again. Tell them to look for the best quality ones they can find. And if the resolution or the quality is too small inform them so they know what to expect.
3) Data on tables or charts and diagrams. They also need to provide this in a standard program or format. For example, a table must be provided as an excell file, not a power point where all cells are little images.
If you need to replicate some of this elements they need to review them and authorize them.
For what you are really responsable. Separate a project into chunks.
Images. Confirm the resolution, quality, and also copyrights.
Ilustrations, Confirm the content reflects the idea, have feedback on this separated elements, becouse you probably are not an expert on what a situation of the project is. They are, so a lot of feedback on content. It does not matter if you do them or not.
The same with Photography. Hire a profesional photographer if needed.
Texts. If they provide you with the texts, now you are responsable of using them all.
You should not crop a text becou
Use master pages, use styles. Do not use "artistic texts" (A one time modified text) but styles whenever posible.
Once one "designer" that came to me looking if I could hire her, showed me a dummy with totally inconsistent margins on a 8 page brochure... Some big some thin... Not good at all.
You need to know the color, and the print process.
Define your colors as spot ones or cmyk ones correctly. This is out of the scope of this answer.
Details Like page numbering, and some little icon here and there, again, try to use an automated system when posible, so you do not need to look for that everytime, but always take a look at that.
Have someone to look for it
Before a major revision.
Normally there is no "final" file, untill the file is actually authorized as such, and this same file is used in the print process.
Take a look on this topic about naming conventions for revision control:
What is your file naming convention you use for version control?
Have a written system for revisions
If the client provided you with some feedback write it down, or ask him to send it by mail, and tag thoose mails.
All final revisions should be aprooved as such
There is no "oh, yes, make thoose changes and send them as you please".