Why Confidentiality Shapes the Entire Site Selection Process
The moment a company begins evaluating new locations for an office, distribution center, or manufacturing facility, a clock starts ticking. Word travels fast in commercial real estate markets. Landlords talk to each other, brokers trade intelligence at industry events, and local economic development officials sometimes surface a prospect's name before any terms are agreed. Protecting the identity of the searching organization is not a procedural nicety — it is a strategic necessity that affects negotiating leverage, workforce stability, and competitive position.
Understanding how to use code names and non-disclosure agreements in site selection means treating confidentiality as a project discipline from day one, not as an afterthought once a short list is formed. Every member of the project team, every adviser, and every counterparty who touches the search should operate under a shared confidentiality framework before any property address, incentive package, or headcount projection is shared.
What a Code Name Actually Does for a Search
A code name replaces the real organization's identity with a neutral, unrelated label for all external communications throughout the search. The name itself carries no meaning that could hint at the industry, parent company, or project scope. Common practice is to select a word that is memorable enough for internal coordination but generic enough that even a curious landlord or economic development officer would find nothing useful in it.
The operational benefit is straightforward. When a broker submits requests for information or tours a building on behalf of "Project Cedar," the building owner cannot immediately research the prospect's balance sheet, run headcount estimates, or reach out to the prospect's facilities team directly. That information asymmetry gives the project team time to evaluate options on their merits before the market adjusts pricing in response to the prospect's perceived urgency or financial capacity.
Code names also provide a clean audit trail. Every document, data room, financial model, and email thread that references the project by its code name creates a traceable record of what was shared with whom and at what stage. If a leak occurs, that record becomes the first tool for identifying the breach point.
The code name should be assigned before any external contact is made — before a broker is retained, before an economic development agency is briefed, and before any site visits are scheduled. Assigning it retroactively forces the team to reconstruct an information timeline that may already be compromised.
Selecting a Code Name That Holds Up Under Scrutiny
Choosing the wrong code name creates its own risk. Names that reference the company's industry, geography, or strategic direction can narrow the field of guesses quickly. A logistics company that uses "Project Runway" or a semiconductor manufacturer that uses "Project Silicon" has effectively broadcast a clue. The safest code names are drawn from entirely unrelated domains — natural elements, mythological figures, or neutral geographic terms that have no connection to the searcher's business.
The team should also avoid reusing code names from prior searches. Sophisticated market participants, particularly in major industrial or office submarkets where the same advisers and landlords recur, may recognize a code name pattern and begin associating it with a known corporate parent. A fresh, unused name for each discrete project eliminates that risk.
Once selected, the code name should be registered internally so that project management systems, document storage, and financial models all reference it consistently. Any document that carries the real company name alongside the code name should be treated as restricted distribution and stored separately from materials intended for external sharing.
How Non-Disclosure Agreements Complement the Code Name
A code name is a practical convention. A non-disclosure agreement is a legal instrument. Together they create the confidentiality architecture that allows a site selection search to proceed without exposing the organization's identity, intentions, or financial terms to the broader market. The NDA defines what information is confidential, who may receive it, how it may be used, and what remedies are available if it is disclosed without authorization.
In site selection, NDAs are typically bilateral — both the prospect organization and the counterparty agree to protect each other's information. A landlord or developer may have sensitive financial information about a building's debt structure or existing tenant mix that it needs to protect in exchange for sharing detailed floor plans or infrastructure specifications. A mutual NDA acknowledges both parties' interests and tends to move more quickly toward execution than a unilateral instrument.
The scope definition within the NDA matters as much as the confidentiality obligation itself. A poorly drafted scope clause can exclude critical categories of information by accident. Project financial models, headcount projections, incentive negotiation positions, and timeline constraints should all be named explicitly as confidential information if they are being shared across the table.
Drafting the NDA: Core Provisions That Protect a Search
The term of the NDA is the first provision that requires careful attention. Site selection searches can run from six months to several years depending on the complexity of the project, the availability of suitable supply, and the pace of incentive negotiations. An NDA with a twelve-month term may expire before the project closes, leaving sensitive information unprotected at exactly the moment when a final lease or purchase agreement is being negotiated. A term of two to three years, or alternatively a term that runs through a defined period after the transaction closes, gives the project team a durable protection window.
The permitted use clause defines what the receiving party may do with the confidential information. In site selection, the permitted use should be limited to evaluating the specific opportunity — not to informing the recipient's own development decisions, marketing efforts, or conversations with other tenants or buyers. A landlord who learns that a prospect needs fifty thousand square feet of industrial space near a specific port should not be permitted to use that information to market competing buildings or alert other brokers.
Carve-outs for publicly available information and for information that the receiving party independently developed are standard in commercial NDAs. The project team's counsel should review these carve-outs to ensure they are narrowly written. Broad carve-outs can effectively swallow the protection the NDA was designed to provide if a counterparty claims that the prospect's identity was already publicly available from a trade press report or a regulatory filing.
Remedies and dispute resolution provisions govern what happens when a breach occurs. Monetary damages can be difficult to quantify when the harm from a leak is a loss of negotiating leverage or a premature workforce announcement. Many site selection NDAs include explicit acknowledgment that breach may cause irreparable harm and that injunctive relief is an appropriate remedy, which simplifies the path to court if the receiving party begins sharing confidential information.
Sequencing NDA Execution Across the Search Team
A site selection search rarely involves a single counterparty. The project team typically includes the occupier's internal real estate and legal staff, one or more external advisers or brokers, economic development agencies at the state and local level, architecture and engineering consultants, environmental assessors, and financial advisers who model incentive packages. Each of these parties needs a calibrated version of the NDA matched to the information they will receive and the role they will play.
External advisers who manage the full search — coordinating broker tours, preparing financial comparisons, and presenting shortlisted options — require the broadest NDA because they will be exposed to the most sensitive project information. Architecture and engineering consultants who are engaged only to assess structural capacity at shortlisted buildings require a narrower instrument that limits their permitted use to that specific technical evaluation.
Economic development agencies occupy a particular position in this sequence. They are often the first external party to learn that a prospect is evaluating a jurisdiction, because incentive programs require early engagement to allow time for legislative or administrative approvals. Most state and local development agencies maintain confidentiality policies as a matter of practice and can point to their own non-disclosure commitments. Nevertheless, a signed NDA between the prospect organization and the agency creates a contractual foundation that is more reliable than a policy statement. The code name should still be used in those conversations until the organization is prepared to disclose its identity formally, typically at the point of a public announcement tied to an incentive commitment.
Managing Code Name Discipline Inside the Project Team
Confidentiality breaches in site selection searches are more often the product of internal carelessness than deliberate disclosure. An employee who mentions a city being evaluated in an offhand conversation, a finance team member who includes the real company name in a spreadsheet sent to an external broker, or an executive who discusses the search in a public forum before any announcement is ready — these are the common failure modes.
Project discipline starts with a defined access list. The project team should document who has access to the full project identity and who operates only on a need-to-know basis. Junior staff preparing financial analysis or scheduling tours can often complete their work knowing only the code name and the general property parameters. The project sponsor, lead adviser, legal counsel, and HR leadership typically require full information because their decisions hinge on understanding the real organization's constraints.
Communication hygiene reinforces the access list. All external emails, tour request letters, requests for proposal, and negotiation correspondence should use the code name exclusively. Internal communications that use the real company name should be flagged as restricted. Shared drives, document management systems, and financial models should have separate folders for code-name-labeled external materials and real-name internal records. The separation is not complicated to maintain, but it requires a deliberate setup at the start of the project before habits form around looser practices.
Handling Incentive Negotiations Under a Code Name
Incentive negotiations are the phase of a site selection search where confidentiality tension is highest. State and local governments want to announce investments, job commitments, and capital expenditures publicly because those announcements have political value. The prospect organization wants to hold its cards until a final decision is made, a signed incentive agreement is in place, and an internal announcement plan is ready.
The resolution is typically a phased disclosure schedule negotiated alongside the incentive package itself. The prospect agrees to a public announcement date that follows the signing of any incentive agreement and precedes the start of construction or tenant improvements. Until that date, the development agency agrees in writing to refer to the project only by its code name in any internal documents, board presentations, or legislative briefings that might be accessible through public records requests.
This arrangement requires coordination between the prospect's legal team, the economic development agency's counsel, and sometimes the governor's office or a state cabinet if the incentive package requires executive approval. The code name appears in draft legislation, grant applications, and board resolutions until the agreed disclosure date. Once the announcement is made, the code name is retired and all public documentation is updated with the real organization's name.
It is also worth reviewing how public records laws in the relevant jurisdiction treat economic development documents. In many states, documents submitted as part of a confidential business attraction process carry a statutory exemption from public records disclosure for a defined period. The project team's legal counsel should confirm the applicable exemption period at the outset so that the phased disclosure schedule is calibrated to match the statutory window.
What Happens When Confidentiality Breaks Down
Even a well-constructed confidentiality framework can be breached. A building owner's property manager mentions a tour to a competing landlord. A local newspaper picks up a tip from a county planning office. A vendor who was shown a floor plan posts a question on a professional forum that inadvertently reveals the building address and the prospect's headcount requirements. When a breach occurs, the project team's response in the first twenty-four to forty-eight hours determines how much damage is contained.
The first step is to identify the scope of what was disclosed and to whom. If the breach was contained — a single conversation between two people who have already signed NDAs — the exposure may be limited and manageable with a direct conversation and a written reminder of confidentiality obligations. If the information reached a publication or a broad professional network, the containment window has likely closed and the team needs to shift to a managed disclosure posture.
A managed disclosure under breach conditions means the project team controls the narrative by releasing accurate information through its own channels before speculation and rumor fill the void. This typically involves briefing key stakeholders — employees, local officials, and major customers — in a coordinated sequence, often within hours of each other, so that no single group learns of the project from a secondary source. The code name is retired at that point, and the project proceeds under the real organization's identity.
Post-breach, the legal team should evaluate whether the breach constitutes a violation of the signed NDA and what remedies are proportionate. In most site selection contexts, the goal is not litigation but remediation — restoring workable relationships with the counterparty and protecting the transaction timeline. Litigation is a last resort reserved for cases where the breach was deliberate and caused quantifiable harm to the negotiating position.
Integrating Confidentiality Protocols Into the Project Workflow
Confidentiality is most durable when it is built into the project workflow rather than enforced through periodic reminders. At the project kickoff, the lead adviser should walk every team member through the code name convention, the NDA execution timeline, the access list, and the communication protocols. That briefing should be documented and acknowledged in writing by each team member.
As the search progresses from market analysis to short list to active negotiation, the confidentiality framework should be reviewed at each stage. New team members who join at the short-list phase need to be briefed and added to the NDA structure. Consultants who finish their engagement and leave the project team should receive a written reminder of their continuing obligations under the NDA. Access permissions in shared systems should be updated as the team composition changes.
Building the Financial Evaluation While Protecting Identities
Financial modeling in site selection involves information that is doubly sensitive. The prospect's internal cost targets, capital budget, and occupancy timeline reveal strategic intentions that competitors would find valuable. At the same time, landlord and seller financial data — debt service, existing lease economics, and net operating income — is equally protected. Running a rigorous financial comparison while keeping both sets of data protected requires a clear understanding of what information is needed at each stage and what can be held back until later.
Early-stage financial modeling typically uses placeholder assumptions for the prospect's identity-specific costs — custom tenant improvements, branding, or specialized infrastructure — so that the analysis can proceed without disclosing the full scope of the prospect's requirements. As the search narrows to two or three finalists, those placeholders are replaced with real figures shared under the executed NDA with the specific counterparties at that stage.
Coordinating with Brokers and Advisers Under NDA
The broker or adviser retained to manage the search is typically the first external party to execute an NDA and the one who will coordinate NDA execution with all other market participants. That coordination role requires the adviser to maintain a log of who has signed, what version of the NDA they signed, and what information was shared under each executed agreement.
Version control matters because site selection NDAs are often customized for each counterparty. A developer who owns a greenfield site and is being asked to prepare a build-to-suit proposal may require a different permitted use clause than an existing building owner being asked only for a tour and a term sheet. The adviser who tracks these variations protects the project team from situations where a counterparty claims it was not covered by an NDA for a specific piece of information.
Advisers who operate across multiple markets — as is common in national and international site selection searches — also need to manage confidentiality across jurisdictions where NDA enforceability standards may differ. The project's legal counsel should confirm which jurisdiction's law governs the NDA and whether that choice-of-law selection will be recognized in the markets where the search is active.
Announcing the Decision and Retiring the Code Name
The announcement of a site selection decision is a coordinated communications event, not simply the end of a confidentiality period. The sequence typically begins with internal employee communication, followed by notification of local officials and economic development partners, and then a public announcement timed to align with any required regulatory disclosures or incentive agreement signings.
The code name is formally retired in the announcement materials, which replace every reference to the project's working label with the real organization's name and the specific location decision. Internally, file systems and project records are updated to reflect the real identity, and the code-name folders are archived rather than deleted — they form part of the project's compliance record in the event of any future dispute about what was disclosed and when.
Post-announcement, the NDA obligations do not simply disappear. The term provisions of each signed NDA define how long counterparties must continue protecting the information they received during the search. Parties who received financial models, headcount projections, or incentive negotiation materials remain bound by their confidentiality obligations for the duration of the NDA term, even though the project's identity is now public. The project team's legal counsel should confirm which parties remain bound and for how long.
Maintaining a Site Selection Record for Portfolio and Compliance Purposes
Every site selection search produces a body of documentation that has ongoing value beyond the transaction itself — lease NPV analyses, scoring matrices, NDA execution logs, incentive agreement drafts, and correspondence that explains why certain locations advanced and others did not. Retaining that record in an organized, accessible form supports portfolio decision-making in future cycles and provides a defensible audit trail if any aspect of the process is later questioned.
The record should distinguish between documents that were created under NDA and documents that are freely disclosable. Scoring matrices, financial models, and negotiation records that incorporate counterparty confidential information should be labeled accordingly and stored with access controls that match the obligations under the relevant NDA. Public records — survey reports, title commitments, incentive agreement public filings — can be stored without restriction.
A well-maintained site selection record also provides context that supports workforce and operations decisions tied to the new location. Headcount ramp schedules, capital expenditure timelines, and incentive performance milestones that were negotiated during the search become operational commitments that need to be tracked against actual performance. Connecting those commitments to the lease or ownership record ensures that the organization does not inadvertently miss a milestone that carries a clawback provision or a reporting obligation.
About Advantai
Advantai is a commercial real estate intelligence and operations platform operated by ADVANTAGE AI LLC, a Delaware limited liability company. It connects client relationships, property research, documents and financial decisions in one workspace for commercial real estate teams — advisers and brokerage teams, occupier and facility teams, and portfolio teams. The platform covers CRM and origination, requirements and site selection, Property X-Ray (an interactive 3D building workspace), financial modeling and comparison, document intelligence, transactions and diligence, client collaboration, and portfolio strategy with critical dates. The optional Super Agent upgrade adds specialist, source-backed research and automated scenario analysis.
Get Started with Advantai
Ready to see your next move clearly? Go to advantaico.com, click Request a demo and tell us about your next project. Prefer to start with a single project? Visit advantaico.com/getting-started to plan your first one.