Project Pulse

See it first. Act earlier.

A transparent methodology for public-sector project intelligence

Project Pulse provides business intelligence from permitted public information. It keeps the evidence trail visible and does not treat an early signal as confirmation that procurement will occur.

Last reviewed 5 August 2026

Public-only source discovery

Sources are discovered through official websites, sitemaps, public document libraries and verified public-sector domains. Crawling respects access controls, robots rules, response limits and configured collection boundaries.

Extraction and classification

Documents are parsed before relevant fields are extracted. A useful record needs an identifiable organisation, credible source and evidence connected to a potential built-environment requirement. Vague aspiration alone is not enough.

Evidence, inference and confidence

Evidence is what the source states. Inference is the commercial interpretation of what that evidence may mean. Confidence can increase when dates, named sites, approvals and repeated independent references align, but automated analysis can still be wrong or superseded.

  • Evidence remains linked to its original source.
  • Inferences are presented as judgement, not fact.
  • Material opportunities should be checked against later documents and official notices.

Corrections and limitations

Projects can be delayed, cancelled, renamed or absorbed into wider programmes. Teams should report material corrections and avoid relying on a single stale document. Project Pulse does not claim to identify every project or guarantee a procurement outcome.

Editorial and intelligence note

Project Pulse provides business intelligence based on permitted public information. An early signal is not confirmation that a procurement will occur, and users should validate material opportunities against original sources and later updates.