Build realistic demo cases without using client secrets

Sample records can test the workflow while keeping source and rights boundaries clear.

ContractCanvas insights

Invent the transaction coherently

Use an invented client, scope and fee. Make the deliverables, effort and payment assumptions agree. A case with contradictory dates or unexplained costs distracts from the software behaviour being tested.

Keep research separate

Public research can inform the kinds of services and decisions represented. Label sample transactions as examples. Keep public-source references in the research directory and label the scenario as sample where users select or inspect it.

Test meaningful variation

Create cases with missing inputs, fee conflicts, scope changes and abandoned reviews. These are more useful than hundreds of identical completed records. Ensure users can distinguish editable examples from actual saved work and can recover after a failed import.

Check attachments

Use invented documents with known contents and no copied signatures, private identities or confidential text. Verify that attachment bytes survive export and restore. The ContractCanvas beta is designed for this sample-data evaluation; real client files require an approved data arrangement and production controls.