# What should be in a Q1 GRC demonstration script?

Our proposed acceptance tests focus on exceptions rather than a perfect-path demonstration:

| Test | What the supplier must demonstrate | Buyer acceptance question |
|---|---|---|
| Restricted evidence | A permitted user can access an item; an unapproved user and their AI assistant cannot | Are restrictions maintained in search, summaries, exports and linked records? |
| Contradictory evidence | The system receives two inconsistent control artefacts | Does it expose the conflict rather than silently produce a confident conclusion? |
| Revoked access | A user or agent loses permission during an active workflow | What stops, what remains accessible and what is logged? |
| Failed integration | An evidence feed stops or returns incomplete data | Can the buyer identify stale evidence and recover without duplicate or lost records? |
| Migration and exit | Records are exported with the agreed relationships, files and history | Can another team reconstruct the relevant decision without relying on the incumbent interface? |
| Administrator handover | A buyer administrator changes routing, ownership and reporting | What can be maintained through supported configuration, and what needs specialist work? |

Set pass criteria before demonstrations. Record configuration, version, test data and unresolved issues so that a later release does not inherit an earlier pass automatically.