Demo Environment Issue Log Template
Published October 26, 2026 · By Kate Steinmeyer · Templates & Scripts

A demo environment issue log is for problems in the account, data, connection, or setup used for a product demo. A solutions engineer or demo owner can use it during rehearsal and after a failed session to record what the buyer could not see, what fallback was actually tested, and whether the path works again. A product limitation belongs in the buyer conversation and product documentation; it should not be marked as an environment issue that a reset will fix.
Copy the issue log
The first three rows are fictional examples; replace them with issues from the environment you will use. The final row is a blank copyable entry.
| Opened | Environment / version | Issue and steps to reproduce | Severity | Buyer-visible effect | Owner | Workaround | Fix / reset verification | Status / closed date |
|---|---|---|---|---|---|---|---|---|
| Oct 22, example | Synthetic support demo | Agent inbox stays blank after reset | Block | Ticket resolution cannot be shown | Demo owner | Use a verified recording and offer a live retest | Restored fictional tickets; replayed as the agent in a fresh session | Closed Oct 22, example |
| Oct 22, example | Test reporting workspace | Report loads under an admin account but not the presenter account | Degrade | Buyer cannot follow the intended role's path | Environment owner | Explain the issue and show an approved capture | Correct test-account access; rerun the path as presenter | Open |
| Oct 22, example | Demo integration stub | Sample import stops at the confirmation step | Block | Import result cannot be verified live | Technical owner | Show a clearly labeled, current recording | Reset the stub; verify the full import and result with fictional data | Open |
| [date] | [name / build] | [action, expected, actual] | block / degrade / minor | [what the viewer sees] | [person] | [tested path] | [test and result] | open / [closed date] |
Attach logs or screenshots only under your team's data handling rules. Do not paste secrets or real customer records into a shared issue tracker.
Decide whether the demo can still be used
“Block” means the demo setup cannot show the workflow the buyer came to see—for example, required sample data is missing or the presenter account cannot open the right screen. “Degrade” means the path works with an explained limitation or verified alternative. “Minor” means the issue does not change what the buyer can learn from the demo. Escalate based on that impact, not how dramatic the error screen looks.
If the main path is blocked, stop using that version until it is repaired or switch to a verified alternative. Tell the buyer what the alternative does and does not prove. A recording can show a previously verified path; it cannot establish that a current live connection or unavailable feature works.
Close the issue after a fresh-session test
After a fix, use the same role and clean starting state the presenter will use. Run the full path, confirm expected data, and test the backup. Record who verified it and when. If the problem recurs, link the prior issue so the team can find the pattern.
The fresh-session check matters because a cached admin login can make a repaired environment appear healthy while the buyer-facing account still fails. If the workaround was used in a live meeting, record which proof was shown and whether a follow-up test is owed. The issue log should connect a technical fix to the buyer's original question, not merely mark a ticket “resolved.”
The technical risk register covers what could go wrong; this log captures what actually happened.