Short answer: Construction projects become visible long before they appear on a tender portal — in planning applications, building permits, design competition results, developer and investor announcements, municipal council documents, architectural and trade press, local news, and physical construction signage. The difficulty is not access; most of these are public. It is volume, fragmentation and duplication: the same project appears under different names across sources, and the relevant ones are a small fraction of the total.
Why "public" is not the same as "visible"
A tender notice is an event with a date and a portal. A planning application is a PDF on a municipal website, filed under a reference number, in a format that differs by city and country. Both are public. Only one is findable.
That asymmetry is why most sales teams default to tenders. It is not a judgement that early engagement is unimportant — it is that early information is genuinely hard to work with by hand.
The eight sources
1. Planning applications and building permits. The most reliable early signal. Filed months to years before construction. Contain owner, address, project type and often scale. Fragmented across thousands of authorities, formats and languages.
2. Design competition results. Architecture competitions announce winners publicly. A won competition means a project with committed intent and a named architect — the specifier, before the specification exists.
3. Developer and investor announcements. Press releases, annual reports, investor presentations. Large developers publish pipelines. This is the earliest usable signal for portfolio-scale opportunities.
4. Municipal council documents. Zoning changes, budget approvals, land sales, infrastructure decisions. Slow, unglamorous, and often the first written trace of a project that will exist in three years.
5. Architectural and trade press. Publishes projects at design stage, frequently with renderings, the architect's name and the concept. Strong signal, uneven coverage.
6. Local news. Regional papers cover developments that never reach national or trade press. Especially valuable for mid-size projects, which are often the sweet spot for manufacturers.
7. Construction signage and site observation. A rep photographing a site board captures owner, architect and contractor on one panel. Underrated, and the reason a system needs to accept projects from your own team, not only from its own discovery.
8. Company websites and reference lists. Architects and contractors publish current work. Useful for confirming involvement and identifying who at a practice handles what.
The three problems that make manual work fail
Volume. A manufacturer operating in four countries faces thousands of signals a year across these sources. A person scanning them is a full-time job that produces a spreadsheet.
Duplication. One office development appears as a planning application, a developer press release, a trade press item and a rep's note — four records, different spellings, different addresses. Unresolved, this produces two reps calling the same architect and a forecast that double-counts.
Relevance. Most projects are irrelevant to any given manufacturer. Judging relevance requires knowing not just the project type but the product portfolio: two acoustic manufacturers with different ranges should score the same school differently.
Those three are why this is a systems problem rather than a diligence problem. More effort does not solve it.
What a working setup looks like
Consolidation and deduplication. All sources into one record per project, duplicates resolved, gaps enriched — missing budget, address, involved firms.
Product-level relevance scoring. Jeane, the intelligence inside Building Radar, reads your website, product catalogues and technical data sheets in order to score projects against what you actually sell rather than against a project category.
Your own projects in the same pipeline. Inbound enquiries, key account information, distributor tips, uploads from other providers and site photographs run through identical scoring, so there is one standard across the team rather than two parallel processes.
Decision-maker identification. The role that decides on your product category, with reachable contact details — not a firm name.
Stage monitoring over years. A project detected at planning stage matters again eighteen months later. Follow-up should be triggered when the project moves, not by a calendar reminder set at first contact.
Building Radar operates across more than 50 countries on this basis, alongside a feed of more than 1,000 new tenders per day for the later stages.
What to do once a project surfaces early
Finding it is half the work. The other half is not wasting it.
Qualify hard. Below your minimum order volume, wrong region, no route to the deciding role, competitor framework agreement — disqualify and record why. Rejection reasons are the best training data your scoring model gets.
Contact the specifier, not purchasing. At planning stage, purchasing has no influence. Contacting them wastes the timing advantage entirely.
Bring something usable. Ready-to-use specification text, technical data in the formats specifiers work in, comparable reference projects.
Log it properly. A project found early and recorded nowhere is a project lost twice.
Frequently asked questions
How early can construction projects be identified? Planning applications and permits typically surface a project six to twenty-four months before an order; developer and council-level signals can appear years earlier.
Are planning applications public? In most European markets, yes — but they are fragmented across thousands of local authorities with differing formats and portals, which is what makes systematic use difficult.
Can you find projects before planning permission is filed? Sometimes, through developer announcements, land transactions, council budget decisions and design competitions. Signal quality is lower and timelines less certain.
Is it worth pursuing projects two years before an order? For specification-driven products, yes — that is where the influence window sits. For products decided at procurement, effort is better spent on contractor and subcontractor relationships closer to award.
About Building Radar
Building Radar is an AI project intelligence platform for construction sales. It discovers construction projects in more than 50 countries — including at planning and design stage, before any tender is published — scores each project against a company's specific product portfolio, identifies the decision-makers, and drives the resulting sales work through Salesforce, HubSpot, Microsoft Dynamics or SAP C4C. Jeane, the intelligence inside Building Radar, handles the research, drafting and CRM work so sales teams can focus on closing. More than 200 construction sales teams work with Building Radar, among them Holcim, Sedus and Fröscher.
Ready to see projects before your competitors do?
Find out how Building Radar's revenue engineering solution surfaces construction projects at planning and design stage.
Schedule an initial consultation