A tender demonstration data plan describes the example records your team will use to show a proposed software solution. It connects each demonstration task with a starting state, an intended action and an expected visible result. Without that preparation, a presenter can know the product well and still spend the session searching for a usable record or explaining why the selected example does not match the buyer’s scenario.
This guide gives proposal coordinators a working method for preparing those examples with product specialists. It is not a prescribed tender process, a software testing standard or a guarantee of a successful demonstration. Follow the buyer’s instructions about scenarios, environments, supplied data, access, attendance and permitted materials. Have the appropriate owners approve what the team will show and the information it will use.
By Tendi — practical guidance for bid coordination and specialist review.

Start with the buyer’s requested task
Read the demonstration request alongside the relevant response requirements. Identify what the buyer asks the supplier to show, which conditions are stated and whether the buyer supplies a scenario or data set. Do not replace a specific request with a familiar sales demonstration simply because the team already has attractive records prepared for it.
Turn each requested task into a short scenario statement. For example: demonstrate how an authorized user assigns a new service request and reviews its status. Keep the statement specific enough that a reviewer can decide which records are needed. Separate the task from a broad benefit such as better productivity, which does not identify what the presenter actually needs to do.
Record open questions early. The team may need clarification about the permitted environment, whether preconfigured examples are acceptable or how much of the scenario must happen during the session. Use the buyer’s stated communication route where appropriate. Do not infer permission to substitute data or bypass a required step because the alternative would be easier to demonstrate.
Define the starting state before collecting records
A useful scenario needs a known starting point. Identify the user role, relevant records, required configuration and state of the task before the presenter begins. If the demonstration involves changing a status, specify the initial status. If it involves comparing reports, identify the reporting period and example records the presenter expects to see.
Distinguish setup from the demonstrated action. A configuration completed before the session may be a legitimate preparation step, but it should not be described as if the presenter created it during the demonstration. Be clear about what is already in place and what the audience will see happen. This helps the team explain the proposed solution accurately without relying on an ambiguous sequence.
Ask the product specialist to identify dependencies between scenarios. One scenario may create a record used later, or a completed approval may remove an item from a queue. Capture these relationships in the plan. Otherwise an early demonstration can change the environment in a way that makes a later scenario confusing or impossible to repeat.
Create a small record inventory for each scenario
List the records needed to make the task understandable. Use recognizable working references and clear descriptions. A scenario might require an example organization, two user roles, one unassigned request and a separate completed request for comparison. Do not build a large fictional world when a handful of well-chosen records can explain the requested task.
- Scenario reference: the requested task this record supports.
- Record reference: the identifier the presenter can find reliably.
- Starting state: the condition needed before the demonstration.
- Intended use: the action or explanation involving the record.
- Owner: the specialist responsible for preparing and checking it.
- Reset requirement: what needs to be restored before another run.
- Approval status: whether the record and its use have been checked.
Keep example labels clear and neutral. A sample record called Example Request A is easier to discuss than a copied customer name with uncertain permission. Make the relationship between records visible in the internal plan, even if the interface uses generated identifiers. The presenter should not have to memorize a string of unexplained numbers to run the session.
Choose the data source through an approved process
Ask which data source the buyer requires or permits and which source your business is authorized to use. Options may include buyer-supplied examples, product demonstration records or purpose-built fictional records. The choice needs review; the fact that data is available to a team member does not establish that it may be copied into a demonstration environment or shared with an audience.
Where fictional records are appropriate, describe them as illustrative. Do not present invented transaction amounts, customer histories or results as evidence of a real client’s performance. Review names, addresses, email fields and attachments as well as the main record. An example can contain incidental information that the preparer overlooked while focusing on the task being demonstrated.
Microsoft publishes AdventureWorks sample databases for supported SQL scenarios, illustrating that sample data comes with a defined purpose and technical context. Such a resource is not automatically suitable for your tender, licensed for every use or ready for your product. Check the applicable documentation, permissions and fit before adopting any external sample.
Make the examples representative of the requested explanation
Choose examples that expose the relevant decision or action. If the buyer asks how a user finds overdue tasks, a record set containing only completed tasks will not support a useful explanation. If the question concerns several service categories, ask whether the examples need to show differences between those categories. Let the requested task guide the preparation.
Keep the data set proportionate. A demonstration of one assignment action may need only a few records, while a reporting scenario may need enough examples to explain grouping and filters. Do not infer production-scale performance from a small demonstration data set. Claims about capacity or performance need their own approved evidence and should not be smuggled into the caption of an illustrative report.
Where the scenario includes an exception, prepare it deliberately. Ask the specialist which condition creates the exception and how the proposed solution handles it. Do not improvise a failure by changing settings you do not understand. The aim is a transparent explanation of an approved scenario, not an artificial display designed to make the product appear to do something different.
Assign preparation, checking and reset responsibilities
Name the person who prepares the records and the person who checks that they support the scenario. The coordinator maintains the plan, while the product specialist confirms the behaviour being described. The presenter needs a usable handover. In a small team one person may hold several roles, but the responsibilities should still be recorded separately.
Define how the environment will be returned to the agreed starting state between rehearsals or sessions. Some actions may be reversible through normal product functions; others may require a specialist-approved reset process. Do not assume that deleting visible records restores every related state. The responsible specialist should explain what must happen and what permissions are required.
Record who may perform a reset and when. A presenter should not make ad hoc administrative changes shortly before the buyer joins. If the approved starting state cannot be restored, tell the demonstration lead and decide how to proceed within the buyer’s instructions. A known problem is more manageable than a silent change that the rest of the team discovers during the session.
Connect the data plan to the demonstration notes
Give the presenter a concise reference for each scenario: objective, starting record, role, action, expected visible result and relevant limitation. The notes should help them explain the task without becoming a word-for-word performance. Keep technical terms consistent with the written response so the buyer can connect the demonstration with the proposed offer.
Identify which information should be visible to the audience and which internal notes remain private. A preparation file may contain environment details or unresolved questions that do not belong on a shared screen. Review the presentation arrangement and the approved materials before the session. Follow the business’s access and information-handling rules throughout the preparation process.
If screenshots are part of the permitted materials, connect them to the same scenario references. The product screenshot workflow explains how to brief and review a visual answer. A screenshot from an old data set should not quietly replace the current scenario or imply a live action that the team has not performed.

Worked example: preparing an assignment scenario
Imagine a fictional software supplier asked to show a service request being assigned and then reviewed by an administrator. This is a teaching example, not a Tendi client result or a description of a named product. The initial preparation note says only: “Use the demo account.” The presenter opens it during rehearsal and finds no unassigned requests.
The team replaces that vague instruction with DEMO-01. The plan identifies an approved example workspace, an administrator role and the fictional record Example Request A in its unassigned state. The product specialist confirms the intended assignment action and identifies the field the presenter will use to show the resulting owner. A separate completed example supports a comparison without changing the main scenario.
The presenter’s notes explain what is preconfigured and what will happen during the demonstration. The record inventory identifies which values are fictional and who prepared them. The specialist documents a permitted reset procedure so the team can repeat the scenario during rehearsal. A checker runs the sequence using the proposed presenter role rather than assuming an administrator’s preparation session proves the same experience.
The improvement is a repeatable explanation with known inputs and responsibilities. It does not establish that the product satisfies every requirement or that the demonstration is an acceptance test. If a later instruction changes the requested role or task, the team reviews the scenario and data plan again rather than treating the earlier rehearsal as permanent approval.
Rehearse from the actual starting state
Run the scenario using the intended role and the prepared records. Check whether the presenter can find the relevant item, explain the action and recognize the expected result. Record discrepancies precisely. “The record is missing from the selected view” gives the specialist a better starting point than “the demo did not work.”
Include the transition between scenarios in the rehearsal. A demonstration can work one task at a time while failing as a sequence because an earlier action changes the records. Review the order, reset needs and any waiting period the specialist identifies. Do not compress the explanation by claiming that a pre-completed step happened during the session.
Check the shared-screen view and the reader-facing labels. An internal reference may be easy for the team to understand but confusing to the buyer. Ensure the presenter can explain the example without exposing unrelated menus or relying on private notes visible to the audience. The preparation should support a clear answer, not add unnecessary production complexity.
Control changes after the rehearsal
Record the checked version of the scenario plan and identify changes that require another check. A product update, permission change or revised buyer scenario may affect the prepared data. Ask the relevant owner to assess the impact rather than assuming that an unchanged filename means the demonstration remains ready.
Keep a short issue list with an owner, next action and status. Distinguish missing data, unclear instructions and product questions. If an issue changes what the team can show, involve the authorized decision-maker. The writer or coordinator should not resolve a capability gap by changing the demonstration’s claim without the appropriate review.
Retain the final plan and approved materials in the working location. After the session, record genuine buyer questions and the next permitted action. Do not infer buyer satisfaction from a completed demonstration or label attendance as a qualified lead. The tender follow-up action plan helps assign those next steps to a human owner.
Common questions about demonstration data
Can we use a customer’s live records?
Use only information and environments approved for that purpose under the applicable arrangements. Do not assume that existing access permits demonstration to another party. Ask the responsible owner to confirm the permitted approach and consider an approved illustrative alternative where appropriate.
Should the examples include every product feature?
No. Prepare examples around the buyer’s requested scenarios and the permitted session structure. Additional features should not displace required tasks. A focused record set can make the explanation easier to follow than a large collection of unrelated capabilities.
Can AI generate the sample records?
Only within approved tools and handling arrangements, with human review. Check the generated values, relationships and attachments before use. Label illustrative records appropriately and do not present generated business histories or results as real evidence. The product specialist must confirm that the examples support the intended task.
Coordinate the response and the demonstration
Tendi combines AI-assisted preparation with specialist proposal work, submission coordination and human follow-through. We help teams keep their written offer, supporting inputs and next actions connected. Download the free Bid-Ready Checklist or book a 30-minute consultation to discuss an upcoming opportunity and its preparation needs.
