Keep your RFP response confidential, part by part

Confidentiality on a bid holds when you decide it part by part. Mark only the parts of your response a buyer could justify withholding, give each one a reason the buyer can record, and keep a record of every person, partner and tool the buyer's pack reached. A blanket confidentiality legend and a signed NDA each cover at most half the problem. This guide follows the order the work happens in during an RFP response: reading the terms, extending them to partners, clearing tools, marking the response with publication in mind, and closing the bid.

Before you start: owners, inputs and policies

Gather four inputs before the pack arrives, and name an owner for each decision they feed. Tick these off:

• The buyer's NDA or confidentiality terms, whether a separate agreement or clauses in the tender instructions.
• The tender's instructions on marking confidential information, such as a required schedule or form.
• Your company's AI and information-handling policy, with its list of approved tools.
• The partners, subcontractors and consultants likely to need some or all of the pack.

Then name the owners. Legal reviews any term that binds the company beyond this bid. Whoever owns your information policy, IT or information security, for instance, confirms which tools and drives may hold the pack. The bid manager decides what the response marks confidential and answers for it, as for everything else in the response.

BSI's PAS 360:2023, the bid and proposal management code of practice, treats roles and responsibilities as part of good working practice. Confidentiality is where a missing owner shows fastest. A decision nobody owns gets made by whoever downloads the pack first, and by the time you notice, the files are already on three laptops and in someone's chat history.

Read the RFP non-disclosure agreement before anyone opens the pack

Route the buyer's non-disclosure agreement to whoever signs it before anyone downloads the pack, because accepting the terms is usually the condition of access. What you agree there governs every step that follows.

Read it in two halves. The first half governs the bid itself: what counts as confidential information, who may receive it, what it may be used for (preparing your response and nothing else), where it may be stored and what happens to it at the end, whether that's return, destruction or a written confirmation of either. These are terms the bid manager can work with, and they set the rules for the partner, tool and close-out steps below.

The second half reaches beyond the bid, and it goes to legal. Look for exclusivity or non-compete wording, non-solicitation of the buyer's staff, any claim on intellectual property in your response or in ideas you share at clarification, indemnities or uncapped liability for a breach, and an obligation that runs for years after the award. A non-solicitation clause, for example, can bind your whole company rather than the bid team, and accepting that is a decision for someone with authority beyond the bid. If you're unsure which of the buyer's documents bind you before award, this guide to whether an RFP is legally binding sets out the distinction.

Give the storage and processing terms a second read. A clause that limits where documents may be held, or bars disclosure to any third party without consent, decides later whether a cloud drive or an AI tool counts as a permitted place or as an unauthorised third party. Where a term is unclear, raise it with the buyer before you sign. A clarification question on a confidentiality term is cheap before signature and awkward once the pack has been shared.

Extend the terms to every partner who sees the pack

Check that the NDA's definition of permitted recipients covers your subcontractors, consultants and consortium partners before you send them anything, because you, not they, are bound by the buyer's terms.

Agreements commonly let you share with "representatives" on a need-to-know basis, but definitions vary. Some cover employees, professional advisers and affiliates and stop there. Some require the buyer's written consent for any third party. Some make you liable for anything a representative does with the information. Read the clause against your actual partner list, name by name.

Where the terms allow sharing, flow them down before the files go out. That means a back-to-back confidentiality agreement or a signed undertaking from each partner that matches the buyer's terms on use, storage and return, rather than your standard teaming NDA, which may be looser than what you've just accepted. Where the terms require consent, ask the buyer for it, naming the partners.

Then keep a recipient log from the first share. Copy these fields into it:

• Name and organisation
• Role on the bid
• Files or sections received, with version
• Date shared, and how (portal, drive link, email)
• Terms they're bound by: the buyer's NDA, a flow-down agreement or a consent reference
• Date returned or destroyed, and the confirmation received

The same log does the work at close-out, when the buyer's terms ask for every copy back or destroyed. Without it, you're relying on memory. Share by section where you can, too: a subcontractor pricing one lot may not need the full pack, and every file you don't send is one you won't have to chase.

Clear each AI tool and shared drive before the pack goes in

Run two tests on every AI tool and shared drive before any part of the pack goes in: the buyer's terms first, then your company's own policy. The buyer's terms decide where its documents may be stored and processed and whether a third party may handle them. Your policy decides which tools the company has approved. A tool can pass one test and fail the other.

Many security leaders already suspect, or have evidence, that this risk sits inside their own organisation. A Gartner survey of 302 cybersecurity leaders, run between March and May 2025, found that 69% of organisations suspect or have evidence that employees use prohibited public GenAI. On a bid, that might be a writer pasting a long specification into a personal chat assistant account to summarise it. Gartner advises CIOs to define clear enterprise-wide policies for AI tool use and to audit regularly for shadow AI. A bid team can't wait for the audit, so it applies the policy at the point of upload.

The test is the same whatever form the AI takes: a chat assistant such as ChatGPT, Claude or Gemini; Microsoft Copilot in Office; AI added to your content library; or an in-house build. General-purpose AI writes a decent first draft fast, and that isn't the question here. The question is whether the buyer's terms allow you to store and process documents where the tool stores and processes them, and whether your company has approved the tool for confidential material received from a third party. For each tool, check in this order:

1. Where the tool stores and processes uploaded files, against any location requirements in the buyer's terms.
2. Whether the tool's provider counts as a third party under the buyer's terms, and if so, whether you need the buyer's consent.
3. Whether your AI policy approves the tool for confidential material received under an NDA.

Shared drives get the same test, plus one more step. Set up a restricted folder for each bid, with access limited to the people in your recipient log, rather than dropping the pack into the team's general bid area, where anyone with access to past bids can open it. At kick-off, tell writers and subject matter experts by name which tools are cleared for this bid.

Mark confidential information in a tender response part by part

Mark only the parts of your response a buyer could justify withholding, and give each its reason, because a public buyer that's asked to release your information decides for itself, and a clear reason gives it something to weigh. In England, the Cabinet Office's guidance to public buyers on publication says information can only be withheld on sensitive commercial grounds after a public interest test, and tells buyers to record and keep their justification. Your mark doesn't decide the outcome; the buyer's recorded reasoning does. A blanket legend across every page gives the buyer nothing to record, and a mark on something plainly public, such as your company history, can make the marks that matter look like reflex.

What a buyer can justify withholding

The same guidance lists examples of commercial information that could potentially be withheld: financial models and business plans, including details of profit margins and overheads; individual pricing elements; and proprietary details of your solution. That's a sound shortlist to start from, because these are the parts whose release would hand a competitor something it could use. In a typical response, that points to the pricing breakdown by rate or line item, the cost model behind it, and the method statements or technical design that set your solution apart.

Expect some things to be published, whatever you mark. The guidance says commercial sensitivity should not be grounds for withholding the contract value itself, so plan for the total value to appear even where your pricing breakdown is redacted. In the EU, Directive 2014/24/EU bars a public buyer from disclosing information a supplier has designated confidential, including technical or trade secrets and confidential aspects of tenders, subject to national law, particularly on access to information. Hence, designation triggers the duty without settling every request. Under the Procurement Act 2023, in England, Wales and Northern Ireland, a buyer that withholds information must publish or notify the fact that it is doing so and on which ground, so even a redaction is visible to your competitors.

The reason that goes with each mark

Give each mark a reason the buyer could lift straight into its own record. A useful reason has three parts: what is marked, by section or table reference; the harm release would cause, and to whom; and how long the sensitivity lasts.

For example, a reason for a rate card might say that the day rates in the pricing schedule's second table reflect your current margin structure, that a competitor could use them to undercut you on the next contract, and that they stay sensitive for the life of the contract. The last part earns its place. A rate that's sensitive during the contract may not be years later, and saying so makes the rest of your reasoning more credible.

Collect the reasons in one schedule at the front of the response, or in whatever form the tender's instructions require, and mark the pages to match. Before submission, read the marks against the schedule once, so that nothing is marked without a reason and nothing with a reason goes unmarked. Name the person who wrote the reasons as the contact if the buyer asks about a mark.

Close the bid and keep client material out of other bids

When the contract is awarded, or the bid is lost, return or destroy the buyer's documents as its terms require, and work through the recipient log to reach every copy, partners included. Each partner returns or destroys what it received and confirms it in writing, and you record the date against its row. Your own copies count too: the restricted folder, local downloads, email attachments and anything uploaded to an approved tool. Where the terms let you keep a copy for legal or compliance purposes, record what you kept, where and why.

Keep the buyer's documents out of your content library. Your own answers can go back in once they're approved for reuse. The buyer's specification, its pricing templates and anything it told you at clarification were received under its terms, and they stay under them.

The same discipline runs the other way, for your own clients. A case study that names a client and its results may have been cleared for one bid or one purpose, and reusing it elsewhere without that client's approval puts at risk the very relationship it was meant to evidence. Record each approval against the item in the library: who approved, for what use and until when, so a writer can see at a glance whether a named case study is cleared for this response. For how to set up a library whose items carry an owner and a reuse status, see building an auditable library.

In SEQUESTO: your team tags each document in the Knowledge Hub of SEQUESTO's agentic operating system (aOS) by confidentiality, and a client-specific case study can require approval before reuse. Only documents tagged as shareable are suggested for an external submission.

Confidentiality checklist for each bid

Run this at kick-off and again at close-out. Each line is either true for the bid or it isn't:

• The buyer's NDA was read before the pack was opened, and legal cleared every term that reaches beyond the bid.
• Every partner, subcontractor and consultant who received files is covered by the terms, flowed down where needed, and listed in the recipient log.
• Every tool and drive holding the pack was cleared against the buyer's terms and the company's AI policy, and the pack sits in a restricted folder for this bid.
• Every confidential mark in the response has a reason stating the part, the harm and how long the sensitivity lasts, and the schedule matches the marked pages.
• The bid manager knows what a public buyer may still publish, including the total contract value in England, and has accepted it before submission.
• Every copy of the buyer's pack, partners' included, has been returned or destroyed and confirmed in the log. No buyer document or unapproved client material sits in the content library.

Start with the first line on your next bid, before the download link is clicked. That's the point where the other five lines are still easy to get right.