Walkthrough playbook: Relying parties
A walkthrough of CMDash for relying parties: primes, insurers and customer third-party risk teams, run in the live sandbox in about 17 minutes. It is written for the CMDash sales team and for partners who present the product.
- Public page: www.cmdash.com/for/relying-parties
- Recommended plan: Free
- Length: about 17 minutes, 6 steps
- Read first: Before any walkthrough
Who this is for
A prime contractor's supply-chain or compliance team, a customer's third-party risk team, or an insurer: anyone who asks suppliers for security evidence and has to rely on the answer. They may never use the rest of CMDash.
What they are tired of
- "The questionnaire comes back full of yes, and I cannot check any of it."
- "Every doubtful answer costs another round of e-mail."
What it costs them: Supplier risk accepted on trust, and weeks lost to follow-up.
The line to open with: "Stop taking supplier questionnaires on trust." It is the headline of their page. Say it, then ask whether it is true for them before you show anything.
Before this call
- The sandbox is read-only, so a request cannot be sent from it. Show the pages, and use www.cmdash.com/for/relying-parties for the templates and limits.
The walkthrough
1. The idea (3 min)
- Go to: www.cmdash.com/for/relying-parties
- Show: The three basis labels and what a receipt proves and does not prove.
- Say: "Instead of a yes, you get a signed statement with the numbers behind it and a label: measured, self-assessed or self-attested. You decide how much weight each one bears."
2. A request (3 min)
- Go to: The request templates on the same page, then Compliance → Supplier assurance (
/assurance) in the sandbox - Show: A template and its lines.
- Say: "You pick a template, address it to the supplier, and CMDash sends one invitation link. The supplier proves it owns the e-mail domain, and accepts. Nothing is shared until the supplier grants it."
3. The supplier's side (3 min)
- Go to: Compliance → Supplier requests (
/proof/requests) - Show: Where a supplier sees and answers requests.
- Say: "This is what your supplier sees. It answers from its own organization, on the Free plan if it has no other, and chooses which claims to grant. It can withdraw the grant at any time."
4. Reading what came back (3 min)
- Go to: Compliance → Supplier assurance (
/assurance) - Show: The portfolio: each supplier, claim by claim, with freshness.
- Say: "Every supplier that has shared proof, with whether each claim is still current and how it moved since the last receipt. You see statements, dates and basis. You never see the supplier's evidence."
5. Checking a receipt (3 min)
- Go to: www.cmdash.com/verify
- Show: The verifier.
- Say: "Anyone can check a receipt here with no account and nothing to install."
6. Limits and cost (2 min)
- Go to: The limits table and questions on www.cmdash.com/for/relying-parties
- Show: Requests per day, link life, grant life, the CSV export.
- Say: "Asking, reading and verifying need no paid plan. The limits are on the page."
Questions you will get
"Does my supplier have to pay?"
No. The supplier answers from a Free account.
"Does a valid receipt mean the supplier is secure?"
No. It proves who signed a statement, that it has not changed, and its basis. It does not prove a control is effective or that the supplier is compliant.
"Does it replace our TPRM tool?"
It feeds one: the portfolio exports as a CSV of labels, ids and dates.
"What if the supplier stops sharing?"
Reads stop at the next request and you are alerted. Receipts already delivered stay verifiable because they are signed documents.
Recommended plan and next step
Free. The reasons, as they appear at the foot of the public page:
- The Relying-Party Desk and Supplier Assurance are part of proof receipts, which every plan holds, Free included.
- The supplier answers from a Free account too.
- Checking a receipt needs no account at all.
A paid plan matters only if they also want to run their own program in CMDash.
Next step: Have them create a Free organization and send one request to a supplier they know well. Follow up when the first receipt arrives.