Skip to content
DAMREV
Start a Structuring Review

Service

The Programme Design Sprint

The Programme Design Sprint is the DAMREV service that turns a reviewed structure into a designed programme: the instrument, who may hold it, how the register is kept, and which party performs each role. Implementation then starts from a settled plan rather than an open question. The sprint follows the Structuring Review, and its output is yours to use.

What you get

What does the sprint produce?

A designed programme, aligned to the transaction documents and to the roles of the appointed intermediaries. Each element becomes a rule the instrument will enforce, so each is decided here rather than during the build.

How it runs

How does the sprint run, and who is involved?

It starts from the review's reading and ends with a design the client approves. Along the way it settles choices the network leaves to the issuer: on Stellar, an issuer can set authorisation flags and has clawback available on its own asset1.

  1. Start from the review

    DAMREV and the client begin from the Structuring Review's reading and its open points.

  2. Map the roles

    The client, the appointed intermediaries, and DAMREV agree who performs each function.

  3. Write the design

    DAMREV sets out the instrument, eligibility, transfer rules, register, and operating model in writing.

  4. Approve the design

    The client approves the design, and the approval is recorded on the programme record.

Who it suits

Who is the sprint for?

Clients whose structure has passed review and who want the programme decided before anyone builds it. Decisions left to the build get made by whoever is building, and each assumption becomes a rule the instrument enforces.

It suits

  • Clients with a reviewed structure and no programme design
  • Issuers who want every party to agree the roles before build
  • Programmes that will go on to implementation and servicing with DAMREV

It does not suit

  • Structures with open questions on the claim, the vehicle, or the ranking
  • Programmes that have already been built and need servicing
  • Anyone seeking legal advice on the instrument documents

What you provide

What does the client bring to the sprint?

The documents and the people. The design is only as settled as the transaction documents and the parties behind it.

  1. 01

    The Structuring Review reply and any points it raised
  2. 02

    The transaction documents, in draft or final form
  3. 03

    Access to counsel and the appointed intermediaries
  4. 04

    The investor groups and jurisdictions the programme will serve
  5. 05

    The people who will approve the design

How it is charged

How is the sprint charged?

The sprint is charged as orchestration of the programme: the work of designing it and coordinating the parties who will run it. It is the first piece of work under the programme mandate, and the client approves it before anything is built.

Where it leads

What happens after the sprint?

The designed programme goes to implementation, where eligibility evidence can be carried as a reusable credential aligned with the World Wide Web Consortium (W3C) Verifiable Credentials 2.0 standard2. Structuring comes first if the design exposed an open point.

Common questions

What else do people ask?

Short answers to the questions people ask most about this topic.

Is the sprint a separate engagement?

No. The sprint is the design stage of the programme mandate that follows the Structuring Review. Its output is a written design the client approves before DAMREV builds anything.

Does the sprint change the transaction documents?

It aligns the design to them. Where the design exposes a gap in the documents, counsel decides how to close it.

Who approves the design?

The client, through the people it names, and the approval is recorded on the programme record so the built instrument can be traced back to it.

Do we need a Structuring Review before the sprint?

Yes. The sprint starts from the review's reading and the open points it raised. A structure with open questions on the claim, the vehicle, or the ranking goes to structuring first.

What does the sprint produce?

A written design of the instrument, the eligibility model, the transfer rules, the register, and the operating model, approved by the client and recorded on the programme record.

Does the sprint include legal advice?

No. The client's counsel settles the legal points the design depends on, including whether the programme is issuer‑sponsored. DAMREV writes the design around the decisions counsel makes.

References

  1. 1.Chainstack, "What is Stellar". https://chainstack.com/what-is-stellar/ Also: Stellar developer documentation, "Control access to an asset", https://developers.stellar.org/docs/tokens/control-asset-access
  2. 2.World Wide Web Consortium, "Verifiable Credentials 2.0 is a W3C standard". https://www.w3.org/press-releases/2025/verifiable-credentials-2-0/

Last updated:

Ready to build on programmable infrastructure?

Tell us what you want to tokenize. We will show you how DAMREV can run it.