Every infrastructure launch produces a wave of press releases and a shortage of evidence. Ribbons photograph well; verifiable facts are harder to come by and worth far more to anyone deciding whether to commit capital. The disciplined task around the new terminal at Freetown International Airport is to separate what can be documented as of today from what is still assertion.
The starting point is narrow and firm: a new passenger terminal has opened at Freetown International Airport under a private-development and operating arrangement, with the stated aim of higher passenger-handling capability and improved business and tourism connectivity. The developer’s project record is one primary source; the airport and ports authorities and World Bank country data are others. For a Content desk building a source-led package, those anchors define the verifiable spine.
What Is Knowable on 3 March 2023
The confirmable facts are the opening, the delivery model, and the intent to raise capacity and connectivity. Everything an operator would want beyond that — exact capacity figures, capital cost, concession length, traffic forecasts — needs a primary document before it can be reported. Holding that line is the difference between journalism and stenography.
Takeaway: Report the opening as fact; treat the brochure numbers as claims until sourced.
What Needs a Primary Document
The specifics that decide investment cases — passenger throughput, tariff structures, the operator’s revenue share, cost of construction — are [TK] until the concession agreement or an official statement is obtained. A responsible package flags these gaps rather than filling them with estimates dressed as findings.
Each of these gaps has a source that would close it. Throughput is settled by the airport authority’s traffic records; tariffs and the revenue split live in the concession agreement; construction cost sits in the financing documents. A source-led package names the document that would resolve each open question, so that a reader knows not only what is unknown but where the answer is kept. That turns a list of gaps into a research plan rather than an excuse.
Takeaway: A missing number named honestly beats a confident guess.
Grading the Sources
Not every document carries the same weight, and a source-led package says so. A developer’s own project record is authoritative on what was built but interested in how it is framed; an airports or ports authority speaks for the public side; World Bank country data provides the independent macro backdrop against which any traffic or connectivity claim can be sense-checked. The method is to rank each source by proximity and independence, then to trust a claim in proportion to how many unaligned sources support it. A capacity figure that appears only in promotional material sits lower than one confirmed in an official filing. Grading the sources in the open lets a reader see not just what is claimed but how firmly it is held.
Takeaway: Weigh the source before you weigh the claim.
Building the Package: Chronology and Voices
The method is straightforward: assemble the chronology, secure the primary documents, add one operator interview, and test each claim against market data on traffic and tourism. From that spine a chronology, a data visualisation and a Ironu Voices podcast can be built without a single unverifiable assertion. The evidence carries the story.
Takeaway: A timeline built on documents outlives the day’s headline.
The Operator’s Read
For an operator, the value of this discipline is decision safety. Enter, finance or partner on what is documented — the gateway is real and its capacity is rising — and treat the unsourced specifics as open questions to resolve in due diligence. The commitment can be staged to the evidence: a small, reversible position on the verified core, scaled up only as the concession terms, traffic data and cost figures are confirmed. Build the file before you build the position.
Takeaway: The best position rests on what you can prove, not what was announced.
