diff --git a/app/templates/views/roadmap.html b/app/templates/views/roadmap.html
index ff9d38a01..23a1bdfac 100644
--- a/app/templates/views/roadmap.html
+++ b/app/templates/views/roadmap.html
@@ -12,61 +12,88 @@
{{ content_metadata(
data={
- "Last updated": "27 April 2022",
- "Next review due": "12 July 2022"
+ "Last updated": "1 November 2022",
+ "Next review due on": "15 December 2022"
}
) }}
- The US Notify roadmap shows what we’re working on and some of the things we’ve done.
- The roadmap is only a guide. It does not cover everything we do, and some things may change.
+ The Notify roadmap shows what we’re working on and what we're planning to do next.
+ This roadmap is only a guide. It does not cover everything we do, and some things may change.
You can contact us if you have any questions about the roadmap or suggestions for new features.
- Things we’re working on
+ What we’re working on
Now
+ We are investigating the Notify concept, building on the notifications tool pioneered by the UK.
+ To do this, we are convening a pilot with a small set of partners.
+ Goals during this stage:
+
-
- - Make it easier for services to pick their own email branding
- - Help services to get better value for money
- - Improve the time it takes some of our webpages to load
+ - Achieve compliance to begin piloting, such as ATO and privacy standards
+ - Demonstrate that a government-run notifications tool provides a unique value
+ - Gather data from the pilot to improve the product
+
+
+ Features prioritized during this stage:
+
+
+
+ - Bulk, individually customizable SMS sending via web UI
+ - Organization permissions settings for various team members to edit/send
+ - Reusable message templates
+ - 7-day records deletion
+ - Message send/failure analytics
Next
+ If the pilot is successful, we hope to recruit additional high-impact partners to improve outcomes for low-income individuals and families.
+
+ Goals during this stage:
+
- - Explore ways to share common content patterns
- - Make it easier for organisations to find the usage data they need
+ - Complement Notify with practical guidance and support services
+ - Iterate on existing features and implement new features based on what we've learned so far
+ - Hone our measurement approaches to better quantify impact
+
+
+ Features prioritized during this stage:
+
+
+ - SMS sending via API integration
+ - Single-level decision bidirectionality (e.g. reply “YES” if, or “NO” if…)
+ - Self-service account creation
+ - Application status page
+ - Scheduled send option
Later
+ In the future, we may decide to expand beyond SMS, or to offer the service government-wide
+
+ Features to be considered during this stage:
+
- - Let services preview their email branding
- - Let services upload their own logo for emails and letters
- - Meet our targets for accessibility
+ - Email sending via UI and API
+ - Multiple-level decision bidirectionality (greater than one layer decision-tree)
+ - Open-text reply bidirectionality (rather than reply yes or no, 1 or 2, etc.)
+ - Multilingual interface and content library options
+ - Recurring scheduled send (e.g. “Send each Monday for 3 weeks”)
- Things we’ve done
+
{% endblock %}