Rulebook design
Design your rulebook with us.
Together we define what your digital credentials prove, which data they contain and which rules apply.
What is a rulebook?
A rulebook specifies a type of digital credential. It describes what the credential proves, which data it contains and how parties issue and verify it. It also covers the technical format and agreements on validity, revocation and changes.
We can design a complete rulebook with you or build on an existing one. Together we develop the meaning, data and rules for your use case. This service can be purchased separately, without using the Ver.iD platform.
- Meaning and data
- What does the credential prove? Which data does it contain and what does it mean?
- Technical specification
- How is the data recorded, signed and exchanged?
- Trust and maintenance
- Who may issue, how do you check the proof and which rules apply to validity and changes?
Our guidance.
Together we develop the content and rules of your rulebook. Our specialists help you answer these three questions and guide the review with the participating parties.
Meaning and data.
What does the credential prove and which data does it contain? Together we define its meaning and determine the information needed for your use case. You receive data definitions your subject-matter experts and developers can use consistently.
For each field, we define its meaning and source, whether it is required or optional, and any conditions linking it to other fields. We reuse suitable existing definitions and align the technical format with the use case and applicable standards. The rulebook describes the credential type; an issued credential contains the actual data.
- Data source
- ACME University student administration
- Define the scope
- Registration says nothing about attendance, results or a diploma.
- ExamRequired
Official name of the examination as recorded in the academic administration.
Example value: Data structures
- LocationOptional
Campus, building and room where the student takes the examination. Included only once the location has been confirmed.
Example value: North Campus, room B.204
Issuance and verification.
Who can issue the credential, which source do they use, and how does the party using it verify the proof? We define issuance requirements, responsibilities and checks, so issuers and verifiers know which agreements apply to your use case.
Together we document how source data is checked, how the credential reaches the correct recipient and how its origin and integrity are verified. We align trust agreements and technical choices with the intended use and the participating parties’ requirements. The party using the credential decides which proof it accepts and for what purpose.
- Issuer
- ACME University issues the credential based on a confirmed registration in the student administration.
- Recipient at issuance
- Before issuance, ACME checks that the recipient is the student the registration belongs to.
- Checks by the receiving party
- The receiving party checks the signature, trusted issuer, validity and revocation status.
- Use of the proof
- The receiving party decides whether this registration is sufficient proof for its process.
Validity and maintenance.
When is the credential valid and how do we handle revocation and changes? Together we determine what happens when data changes or a credential may no longer be used. We also determine how the rulebook is updated when the use case or agreements change.
We document validity conditions, grounds for revocation and current-status checks. We also determine who maintains the rulebook, who reviews changes and how new versions are adopted. Changing the rulebook does not automatically change previously issued credentials.
- End of validity
- Time from which this attestation is no longer valid. Validity ends no later than the scheduled end of the examination sitting.
- Revocation
- If the registration is cancelled, the credential is revoked.
- Changing the definition
- The participating parties review a proposed change to a field’s meaning. The rulebook maintainer records the decision and the new version.
How we work together.
We agree which rulebook to design or extend, which parties need to review it and what we will deliver. Existing agreements and documentation provide the starting point. You do not need to know the data fields or all the experts involved in advance.
Your team brings the domain expertise
You explain what the credential needs to prove and how your data and processes work. You share available agreements, documentation and examples and appoint a contact. Together we identify the domain, technical, privacy and legal expertise needed.
Our specialists develop the design
We write the definitions and rules, reuse suitable existing agreements and explain the design choices. We discuss concrete scenarios with your team, incorporate feedback and record decisions and outstanding questions.
The responsible parties confirm choices
The designated reviewers assess the parts of the design relevant to their roles. Issuers and organisations using the credential confirm the commitments they are responsible for or need to contribute to. We clearly record any missing participation or confirmation as an outstanding issue.
What you receive at handover
- The rulebook in editable Markdown files, with the agreed meaning, data definitions and rules.
- A record of the sections reviewed, decisions confirmed and outstanding questions, identifying the responsible parties involved.
- Agreements on who maintains the rulebook, how changes are reviewed and which next steps are needed.
We explain the rulebook and outstanding questions to your team and the participants identified at the start. The design engagement ends when the agreed version has been reviewed and handed over. Your organisation decides on next steps and who will maintain the rulebook.
The design engagement can be purchased on its own. Technical testing, implementation, publication and support with later maintenance are agreed separately. Review by the responsible parties is not certification or a guarantee that other organisations will accept the credential.
Practical questions
Not if it is already clear what the credential must prove and how it will be used. We can then start designing straight away. If the use case, participating parties or suitable agreements are still unclear, we determine together which questions need exploring first.
- Do we need an exploration first?
- Not if it is already clear what the credential must prove and how it will be used. We can then start designing straight away. If the use case, participating parties or suitable agreements are still unclear, we determine together which questions need exploring first.
- Can you build on our existing sector agreements?
- Yes. We start from available agreements, definitions and documentation. Together we determine what can be used for digital credentials and which data, technical choices or rules still need development. This aligns the rulebook with the agreements already in place in your sector.
- What if participating organisations have different requirements?
- We identify the differences and discuss them using concrete scenarios. Our specialists explain the options and their consequences; the organisations involved confirm the commitments they are responsible for. We clearly record any decisions that still need agreement.
- Can we use the rulebook outside the Ver.iD platform?
- Yes. The rulebook describes the use case according to the agreed standards and participant requirements. Using the Ver.iD platform is not mandatory. Whether another system supports the design depends on the chosen technical representation and that system’s capabilities; the integration needs a separate assessment.
- How much time will our team need to contribute, and what determines the costs?
- Your team contributes domain expertise and reviews design choices. The work and costs depend on the kinds of digital credentials, available documentation, parties involved and review rounds. We start with a no-obligation conversation and agree the activities, schedule, your team’s contribution and costs before work begins.
Which agreements do you want to put into practice?
Tell us which credential you want to issue or use, what you already have and which expertise you need. In our first conversation, we will identify the right support and scope.