We are very deliberate about setting deliverable dates in time after the required inputs by others are available, and when inevitably they are not, we have a spreadsheet sent to the customer every 2 weeks which shows what information we are missing and the delay that is causing to our progress. As we are liable for damages if we delay the project it is necessary for us to have the proof that we did not cause the project to be behind schedule. This often means having these difficult conversations only a month in to a year long project when vendor drawings we were promised are not delivered.
This is a great approach if you can stay that organised. It reminds me of one of my fundamental rules of business - the two benchmarks you're compared to are the previous entry in the Gantt chart and your counterpart in the client organisation. If you can stay ahead of both of those, you're golden!
Another EPC was moving so fast to try and meet a project milestone in order to get paid, they installed an instrument enclosure totally backwards (huge crane required to drop enclosure into place). They still got paid as the milestone didn't specify the enclosure had to be installed correctly.
One of annoying aspects about controls is that non-technical stakeholders see a mechanically complete object/machine/plant and wonder why it isn't working yet. Also, I always found that the controls guys were the first to get yelled at if something at site stopped working.