I agree with Mr. Gill's comments.
I've never seen corruption in a P3 contract, which is not to say that it doesn't exist or will never exist. The risks are always there in the process. But one of the things that you can ensure, or look to ensure, is clarity in terms of the contract, and sunshine. Sunshine is a good disinfectant. This is something of a controversial issue when it comes to contracting.
I've seen a bad P3 contract. I'll point out a couple of things, and I'll have to leave parties nameless. The contract allowed the private partner to specify the terms of performance, the metrics by which performance will be measured, and to implement the systems that ran the metrics, that produced the performance measure, and the bonuses associated with the contract. That was a really bad idea. There is something else about it too. I sat in a room with a couple of project proponents and read through the contract. I wasn't allowed to leave the room with the contract; I wasn't allowed to take photocopies of any pages. I had a piece of paper and a pencil that I could make notes on, and that was absolutely it. The contract was not in the public domain.
If the parties knew early on the contract was going to be in the public domain sometime after it was let, after they'd been through the bidding process, probably there would have been more discussion about the terms of the contract early on and sunlight would have prevented at least that kind of problem. I won't call that corruption, but certainly it was a bad contract.