To pick up on Craig's point on shovel-worthy versus shovel-ready, one of the things I would caution you guys about in general as a committee would be that when we got infrastructure bundled up with fiscal stimulus, I think that was generally a mistake.
There are two types of infrastructure projects that can take place. There are things that can happen in the 2016 construction season. Those are things like routine maintenance projects. But there are also things that need to be done over the longer term, say, in 2017 or 2018, over the mandate of the government. We can call those shovel-worthy.
The point I would make is that because a project is ready does not make it a top-of-the-list priority. I think we should be looking at building growth, and I think we should be setting expectations such that people are not thinking.... For example, when I look back at the economic action plan, I see that the initial allocation in budget 2009 was that half the spending would be in year one and half in year two. That's in the expectation that in the first construction season there's going to be a lot of activity. I'm just looking at the cost-shared projects, the projects that include municipal, territorial, and federal governments, and in fact, 17% of the stimulus spending came out in year one, 69% in year two, and then it was 14%, because we extended it into year three.
My point would be that we learned something from that episode. I'm not saying that the stimulus program that happened was not done well, but it was not done as quickly as people had expected. Expectations were such that it was going to be boom-boom. I think that as long as expectations are set with the public that some projects need to be done quickly—and they can be, and those will support the economy—most of the focus should be on supporting economic growth. I think that's the safe way to play it.