Dear On Demand Reviews Subgroup Members .. Thanks to Alice, here is a compiled list of suggested high level messages from our subgroup call: * Bucket E is designed to provide greater flexibility. Moving a topic into this bucket does not reduce its importance (i.e. Review of Reviews). * Scoping process being worked on in bucket A subgroup can be leveraged, as applicable, for the threshold process. * Balance between pushing the trigger and pulling out is needed. * Consider a list of examples to illustrate what bucket E could house (similar to examples in annex A of ICANN Bylaws). * Should build a safeguard to ensure this is not used as a way for groups dissatisfied with outcomes of a review or other mechanism to reopen an issue. Notion of high thresholds needs to be built into this. * Should answer a specific question so scope can be contained. * It is key to avoid overlaps. * Threshold process should have a resource check component. * Should distinguish whether recurrence of topics is possible and set clear context around that. * Should elaborate on the notion of “if a specific condition is met” with ability to cancel or defer. * Should build a safeguard that allows for an on-demand review that met the threshold to be stopped while running (e.g. through EC?) Please let us know if you have any comments .. You can find the call material on our Wiki page at https://icann-community.atlassian.net/wiki/spaces/CDOR/pages/987758675/Subgr... [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/spaces...> Kind Regards --Manal