Insights
The document that nearly lost the project it was built to support
Published February 2026
The project was serious, well-conceived, and genuinely needed. A proposed marine infrastructure and oceanographic research facility in the Gulf region, developed by a sovereign authority with a clear strategic rationale and the institutional backing to pursue it. The funding application was directed at a multilateral development institution. The technical case was sound. The market analysis was credible. The environmental rationale was well-established. There was every reason to expect the application to proceed.
The problem was the document.
The techno-economic feasibility study had been produced by the project's technical collaborator, a firm based in France with genuine competence in the underlying engineering, marine technology, and oceanographic systems, but limited familiarity with the specific documentary conventions expected by Gulf-region sovereign authorities and the multilateral funding institutions they engage with. The document they produced was technically rigorous. It was also, in several important respects, written for the wrong reader in the wrong context.
The first difficulty was structural. The study opened with a lengthy methodology section that established the technical credentials of the producing firm before it addressed the project itself. This is a convention in certain technical consulting traditions, it signals competence before making claims. In the context of a funding application to a multilateral institution reviewing hundreds of submissions, it signals something different: that the document does not understand its own purpose. An evaluation committee reading a feasibility study is not assessing the consultant. They are assessing the project. A document that spends its opening pages establishing the consultant's credentials before addressing the project's viability has misunderstood its primary obligation.
The second difficulty was contextual. The market analysis section drew on comparator projects and market data from European maritime contexts, the environment in which the technical collaborator had most of their operational experience. The comparators were legitimate. The data was accurate. But a market analysis for a Gulf-region marine project that grounds its projections in European operational contexts requires, at minimum, an explicit and carefully argued bridge between those contexts and the project's actual environment. That bridge was absent. A reviewer unfamiliar with the collaborator's background would read the section and conclude that the document did not fully understand where the project was located, or who its primary beneficiaries were.
The third difficulty was the most consequential. The techno-economic projections, the financial modelling that underpinned the case for the project's viability and the funding ask, were presented in a format and at a level of granularity that was inconsistent with the expectations of the receiving institution. Not wrong. Not fabricated. Presented in a way that made them difficult to evaluate against the institution's own assessment framework. A reviewer working to a specific template and timeline, finding that the document's financial projections do not map cleanly onto the categories their framework requires, will not take the time to reconstruct the mapping themselves. They will note the deficiency and move on.
The document reached this practice at a point where the sovereign authority had received informal signals from the multilateral institution that the application was unlikely to proceed in its current form. The feedback was not detailed, multilateral institutions rarely provide granular rejection rationale, but the signals were clear enough. The technical case was not the issue. The document was.
The reconstruction work was substantial. It was not, however, a matter of changing the underlying analysis. The analysis was sound. It was a matter of rewriting the document so that the analysis it contained could be read and evaluated by the audience it was addressed to.
The methodology section was moved to an appendix. The market analysis was restructured around Gulf-region comparators, with the European data retained as secondary reference and the bridge between the two contexts made explicit and argued. The financial projections were reformatted to map directly onto the evaluation framework of the receiving institution, a framework that is publicly documented and that the original document had not consulted.
The executive summary, which in the original ran to eleven pages, was reduced to four. The first paragraph of the reconstructed summary stated the project's purpose, its funding ask, and its primary viability finding in three sentences. A reviewer who read nothing else would know, from those three sentences, what they were being asked to fund and why it was viable.
The reconstructed application was resubmitted. It proceeded to the next stage of evaluation.
What that engagement illustrated, in terms that any project developer working across institutional contexts will recognise, is a specific and recurring vulnerability. Technical competence and documentary competence are not the same skill. A firm that is genuinely expert in the engineering of marine infrastructure and oceanographic systems is not automatically expert in the production of documents that communicate that engineering to institutional funders in a different region with different conventions and different evaluation frameworks.
This gap is not a criticism of the technical collaborator. It is a structural feature of complex cross-border projects. The document that a European engineering firm produces from its own professional tradition is not the same document that a Gulf sovereign authority needs to present to a multilateral funder. Both documents may contain identical underlying analysis. Only one of them will be read in the way it needs to be read.
The cost of that gap, in this case, was nearly the project itself. The reconstruction was possible because the analysis was sound. It would not have been possible if the analysis had been weak. But the analysis was never the risk. The document was.