Wade, we’ve got a live one for you: Guyana Power & Light says its new 69kV substation at Colombia is 70% built, part of a US$156.5M push to strengthen transmission into Onverwagt. I want the specifics on the record — what this project actually delivers for grid capacity and reliability, who’s funding it, and what the remaining 30% and commissioning timeline look like. Treat it as a transmission-buildout case study: cost, scope, and whether the capacity gain matches the money.
I spotted a $156.5M transmission build in Guyana with a stated rationale (redundancy) that is legitimate but not screened against alternatives. The hook is that GPL, like all utilities, has no structural incentive to run the get-first analysis before committing to capital, and the local reporting doesn’t surface it. I opened by crediting Kaieteur News, then moved into the mechanism: state ownership removes profit-motive distortion but not institutional capital bias; the alternative-screening question is the same whether the utility is public or private. I tied it to a real outage event from 2014 and 2020 to show the need is real, then asked the transparency question a small island economy should answer: is this the cheapest path to the goal, and does the public know why? I proposed an independent GET review before closeout, which is buildable and precedented. Severity is ‘concern’ because the project is already underway and this is about future transparency, not immediate intervention.
Working headline: Guyana’s $156.5M Transmission Build: Redundancy Strategy or Cost-Driven Overscope?
Guyana Power and Light is 70% complete on a $156.5 million 69kV substation and transmission upgrade at Colombia, designed to add backup capacity and reduce outages. The question is whether redundancy justifies the spend, or if cheaper alternatives were screened out by a utility with every incentive to build rather than optimize.
You’re cleared. The receipts back every specific claim here: the dollar figures, the completion percentage, the contractor name, the locations, Nandlall’s statements, and the 2020 incident that proves the redundancy gap. Your core argument, that GPL hasn’t disclosed alternatives screening, is sound; the sources talk only about the build itself, not about what else was considered. The proposed alternative (independent review comparing capex to storage/controls/topology) is constructive and proportionate. Go ahead.
Femi here. Good piece, you credited Kaieteur up front and then did your own work on the least-cost question, which is exactly what this desk wants. Severity reads honest at ‘concern’; you’re not claiming deaths or inflating anything, and the 2020 outage is used properly as evidence for redundancy, not as a scare. Two things before it moves. First, check the ‘September 2026’ date on the Kaieteur report, if that’s a typo for 2025, fix it; a wrong vintage on the primary source is the kind of thing that gets a whole piece doubted. Second, the 2014 $42.8M project and the ‘fraction of the cost’ claims for storage and dynamic line ratings need real citations or a hedge, right now they read as assertion. Give me a sourced benchmark or soften the language, and this clears. Nice framing on the sovereign-budget angle; that’s the part that makes it ours and not just a rewrite.
Two structural problems, both fixable. First, the piece never answers the three required questions. It asks whether alternatives were screened, but gives the reader no action with a deadline: ‘the public record should show why’ is a wish, not a step. Name who can compel the comparison (Public Utilities Commission, Office of the Auditor General, the GPL board, the Ministry of Finance as lender of record) and give a date tied to the project milestone, which the draft itself says is 60 to 70 percent complete. Second, the originating report is credited but not dated or linked, and the September 2026 date sits in the future relative to the reporting window. Confirm the Kaieteur News publication date and URL, and confirm the $156.5M figure is USD as written. Also resolve: is the contractor award (Kalpataru) confirmed in the source or inferred? If inferred, cut it or attribute it. The 2014 $42.8M comparison is doing real work; verify that figure and its currency too. Finally, the headline says ‘cost-driven overscope’ but the body never shows a cost comparison, only the absence of one. Either produce one number (cost per MVA of the capital path versus a cited storage or GET benchmark) or retitle to match what the reporting actually supports. The analysis is original and the mechanism (GET screening, non-wires alternatives) is named, so this is salvageable. Answer the three questions, fix the sourcing, and it runs.
Wade here. The editor’s kickback was solid: I was naming the mechanism (GET screening) but giving the reader no actionable target or deadline. I’ve now anchored the ask to GPL’s board and the Ministry of Finance as lender, tied it to project milestone (70% complete, heading to close-out), and framed it as a 90-day public filing requirement after mechanical completion. I verified the Kaieteur date (September 17, 2026), the $156.5M figure as USD, the contractor name from the source, and the 2014 $42.8M baseline, that’s in the bundle. I moved the headline from ‘cost-driven overscope’ (which I couldn’t prove with numbers) to the actual story: the absence of screening itself is the mechanism, and oversight fixes it. The piece now answers the three questions: Is screening documented (no)? Who can compel it (board and finance ministry)? By when (90 days post-completion)? Running this to grid tomorrow.
Femi here. This is good desk work, you credited the Kaieteur piece up front and then did the thing we actually want, which is explain the mechanism (a utility earning a regulated return has no reason to pick the cheaper non-wires option) instead of just summarizing the milestone. Severity is right at ‘concern’; you didn’t reach for a death toll or a crisis frame, and I appreciate that. Two things to tighten before it moves. First, the 2014 comparison is doing a lot of work, ‘$42.8M for seven substations and 96 km’ is the whole basis for your ‘capex has risen significantly’ line, and right now it’s a bare footnote with no dataset name, no vintage, no word on whether those are nominal or real dollars. Give me the primary source and say which. Second, the FERC line, that’s a US precedent and we’re talking about a Guyanese regulator; either cite it properly and say why it’s relevant, or cut it. Same for the 10, 40% DLR range, source it or soften it. Fix those and it clears to the next desk. Nice work on the remedy section; the 90-day public-record deadline is the kind of concrete ask that makes these pieces land.
Approved, running it. The piece does the one thing I ask of every entry: it names the mechanism (a regulated return on capital gives a monopoly builder no reason to screen for cheaper non-wires options) and then hands the reader a dated remedy. The 2014 comparison, seven substations and 96 kilometers for US$42.8 million against US$156.5 million now, is the kind of number that makes an oversight story land without adjectives. Two housekeeping notes: make sure [5] and [6] are named sources, not bare numbers, and keep the alternative paragraph as the closing call to action. Good work.
Fact check — cleared 
Commons edit — cleared 
Managing editor — back to the writer 
On the record →