Business Cases for Major Public Infrastructure Projects in Canada
Notice bibliographique
Résumé
When governments announce that they are going to spend vast sums of taxpayers’ money on a new public infrastructure project, you can be certain they will praise all the terrific new benefits that the project will bring to citizens, making everyone’s life easier, safer, greener and better. But this does not tell us whether we are better off as a society, after accounting for the cost of these projects borne by taxpayers today and well into the future. In reality, there is a meaningful risk that a project undertaken without a proper business case could end up making citizens’ lives worse. That new commuter train might look sleek and shiny and seem convenient for some, but a close business case analysis of recent transit projects in Canada’s three largest cities suggests that in as many as four cases out of 21 projects, the burden of paying for the projects does not justify the public investment. In a review of thirteen recent public transit projects in the Greater Toronto and Hamilton Area (GTHA), at least three projects had benefits that fell short of the costs. Yet, all three projects went ahead (or have been funded). Only one project showed large net benefits for citizens once all considerations were accounted for. Three projects showed small net benefits – of a size that can be easily offset by a modest cost over-run. The six remaining projects did not have any publicly available business cases. In the Greater Montreal area, a review of three recent major transit projects turned up no evidence of a publicly available business case for any of them. As a result, Montrealers are in the dark as to how much benefit or value destruction the three projects are responsible for. Things are far more encouraging in Vancouver, however, where three out of the five major transit projects undertaken or funded in recent years were backed by business cases showing a net benefit. Only one project did not show a net benefit and one project did not have a business case. Of course, business cases only make projections about net benefits. Rarely, if ever, do governments undertake an ex post review to determine whether their estimates were correct and if the project has delivered — or destroyed — the value expected. Given that these projects can run into the billions of dollars, tie up immense amounts of government resources, and can cause any number of disruptions to business and families, it is remarkable how little cost-benefit scrutiny is brought to bear on them. Without these ex post business cases, there can be no lessons learned from past projects. There can be no assurance that we can make better investment decisions going forward.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,003 | 0,046 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,001 | 0,003 |
| Études des sciences et des technologies | 0,001 | 0,000 |
| Communication savante | 0,002 | 0,003 |
| Science ouverte | 0,004 | 0,001 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,001 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».