diff --git a/.gitleaksignore b/.gitleaksignore
index 98f14c38..711d2daa 100644
--- a/.gitleaksignore
+++ b/.gitleaksignore
@@ -1,5 +1,5 @@
 # SEE: https://github.com/gitleaks/gitleaks/blob/master/README.md#gitleaksignore
 
 cd9c0efec38c5d63053dd865e5d4e207c0760d91:docs/guides/Perform_static_analysis.md:generic-api-key:37
-e4da81343a2eb3c00e0b8d90f89817d8b3a82dca:docs/_includes/components/pagination.html:ipv4:25
-e4da81343a2eb3c00e0b8d90f89817d8b3a82dca:docs/_includes/components/pagination.html:ipv4:41
+13eb65f8a80c17ba5cb27caf96d8b66867879715:docs/_includes/components/pagination.html:ipv4:25
+13eb65f8a80c17ba5cb27caf96d8b66867879715:docs/_includes/components/pagination.html:ipv4:41
diff --git a/.tool-versions b/.tool-versions
index e848dbb3..4cf4ecae 100644
--- a/.tool-versions
+++ b/.tool-versions
@@ -1,10 +1,11 @@
-# This file is for you! Please, updated to the versions agreed by your team.
-
 gitleaks 8.18.4
 nodejs 18.18.2
 pre-commit 3.6.0
 terraform 1.7.0
 vale 3.6.0
+python 3.13.2
+
+
 # ==============================================================================
 # The section below is reserved for Docker image versions.
 
@@ -17,7 +18,7 @@ vale 3.6.0
 # docker/ghcr.io/nhs-england-tools/github-runner-image 20230909-321fd1e-rt@sha256:ce4fd6035dc450a50d3cbafb4986d60e77cb49a71ab60a053bb1b9518139a646 # SEE: https://github.com/nhs-england-tools/github-runner-image/pkgs/container/github-runner-image
 # docker/hadolint/hadolint 2.12.0-alpine@sha256:7dba9a9f1a0350f6d021fb2f6f88900998a4fb0aaf8e4330aa8c38544f04db42 # SEE: https://hub.docker.com/r/hadolint/hadolint/tags
 # docker/hashicorp/terraform 1.5.6@sha256:180a7efa983386a27b43657ed610e9deed9e6c3848d54f9ea9b6cb8a5c8c25f5 # SEE: https://hub.docker.com/r/hashicorp/terraform/tags
-# docker/jdkato/vale v2.29.7@sha256:5ccfac574231b006284513ac3e4e9f38833989d83f2a68db149932c09de85149 # SEE: https://hub.docker.com/r/jdkato/vale/tags
+# docker/jdkato/vale v3.6.0@sha256:0ef22c8d537f079633cfff69fc46f69a2196072f69cab1ab232e8a79a388e425 # SEE: https://hub.docker.com/r/jdkato/vale/tags
 # docker/koalaman/shellcheck latest@sha256:e40388688bae0fcffdddb7e4dea49b900c18933b452add0930654b2dea3e7d5c # SEE: https://hub.docker.com/r/koalaman/shellcheck/tags
 # docker/mstruebing/editorconfig-checker 2.7.1@sha256:dd3ca9ea50ef4518efe9be018d669ef9cf937f6bb5cfe2ef84ff2a620b5ddc24 # SEE: https://hub.docker.com/r/mstruebing/editorconfig-checker/tags
 # docker/sonarsource/sonar-scanner-cli 5.0.1@sha256:494ecc3b5b1ee1625bd377b3905c4284e4f0cc155cff397805a244dee1c7d575 # SEE: https://hub.docker.com/r/sonarsource/sonar-scanner-cli/tags
diff --git a/docs/_includes/breadcrumb.html b/docs/_includes/breadcrumb.html
index 525cdbee..14c49afe 100644
--- a/docs/_includes/breadcrumb.html
+++ b/docs/_includes/breadcrumb.html
@@ -40,6 +40,12 @@
     </li>
     {% endif %}
 
+    {% if page.parent == "Pagination example" %}
+    <li class="nhsuk-breadcrumb__list-item">
+      <a class="nhsuk-breadcrumb__link" href="{{site.baseurl}}/pagination-example">Pagination example</a>
+    </li>
+    {% endif %}
+
   </ol>
 
   <!-- Mobile breadcrumb back -->
diff --git a/docs/_includes/components/contents-list.html b/docs/_includes/components/contents-list.html
new file mode 100644
index 00000000..24142d1f
--- /dev/null
+++ b/docs/_includes/components/contents-list.html
@@ -0,0 +1,25 @@
+{%- comment -%}
+NHS Contents List Component
+Used for mini-hub navigation
+
+Parameters:
+- items: array of objects with 'title', 'url', and optional 'current' (boolean)
+
+Example usage:
+{% include components/contents-list.html items=page.mini_hub_pages %}
+{%- endcomment -%}
+
+<nav class="nhsuk-contents-list" role="navigation" aria-label="Pages in this guide">
+  <h2 class="nhsuk-u-visually-hidden">Contents</h2>
+  <ol class="nhsuk-contents-list__list">
+    {% for item in include.items %}
+    <li class="nhsuk-contents-list__item{% if item.current %} nhsuk-contents-list__item--current{% endif %}">
+      {% if item.current %}
+      <span class="nhsuk-contents-list__current" aria-current="page">{{ item.title }}</span>
+      {% else %}
+      <a class="nhsuk-contents-list__link" href="{{ item.url | prepend: site.baseurl }}">{{ item.title }}</a>
+      {% endif %}
+    </li>
+    {% endfor %}
+  </ol>
+</nav>
diff --git a/docs/_includes/components/pagination.html b/docs/_includes/components/pagination.html
new file mode 100644
index 00000000..39ad1231
--- /dev/null
+++ b/docs/_includes/components/pagination.html
@@ -0,0 +1,48 @@
+{%- comment -%}
+NHS Pagination Component
+Used for mini-hub page navigation
+
+Parameters:
+- previous: object with 'title' and 'url' (optional)
+- next: object with 'title' and 'url' (optional)
+
+Example usage:
+{% include components/pagination.html previous=page.previous_page next=page.next_page %}
+{%- endcomment -%}
+
+<nav class="nhsuk-pagination" role="navigation" aria-label="Pagination">
+  <ul class="nhsuk-list nhsuk-pagination__list">
+    {% if include.previous %}
+    <li class="nhsuk-pagination-item--previous">
+      <a class="nhsuk-pagination__link nhsuk-pagination__link--prev"
+        href="{{ include.previous.url | prepend: site.baseurl }}">
+        <span class="nhsuk-pagination__title">Previous</span>
+        <span class="nhsuk-u-visually-hidden">:</span>
+        <span class="nhsuk-pagination__page">{{ include.previous.title }}</span>
+        <svg class="nhsuk-icon nhsuk-icon__arrow-left" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"
+          aria-hidden="true" width="34" height="34">
+          <path
+            d="M4.1 12.3l2.7 3c.2.2.5.2.7 0 .1-.1.1-.4.1-.5v-2h11c.6 0 1-.4 1-1s-.4-1-1-1h-11V9c0-.2 0-.4-.1-.5-.2-.2-.5-.2-.7 0l-2.7 3c0 .2 0 .4.1.5h-.1z">
+          </path>
+        </svg>
+      </a>
+    </li>
+    {% endif %}
+    {% if include.next %}
+    <li class="nhsuk-pagination-item--next">
+      <a class="nhsuk-pagination__link nhsuk-pagination__link--next"
+        href="{{ include.next.url | prepend: site.baseurl }}">
+        <span class="nhsuk-pagination__title">Next</span>
+        <span class="nhsuk-u-visually-hidden">:</span>
+        <span class="nhsuk-pagination__page">{{ include.next.title }}</span>
+        <svg class="nhsuk-icon nhsuk-icon__arrow-right" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"
+          aria-hidden="true" width="34" height="34">
+          <path
+            d="M19.6 11.66l-2.73-3A.51.51 0 0 0 16 9v2H5a1 1 0 0 0 0 2h11v2a.5.5 0 0 0 .32.46.39.39 0 0 0 .18 0 .52.52 0 0 0 .37-.16l2.73-3a.5.5 0 0 0 0-.64z">
+          </path>
+        </svg>
+      </a>
+    </li>
+    {% endif %}
+  </ul>
+</nav>
diff --git a/docs/_layouts/mini-hub.html b/docs/_layouts/mini-hub.html
new file mode 100644
index 00000000..a117f782
--- /dev/null
+++ b/docs/_layouts/mini-hub.html
@@ -0,0 +1,49 @@
+---
+layout: default
+---
+
+<div class="nhsuk-width-container">
+  <main class="nhsuk-main-wrapper" id="maincontent" role="main">
+    <div class="nhsuk-grid-row">
+      <div class="nhsuk-grid-column-two-thirds">
+
+        {%- comment -%}
+        Mini-hub heading with topic subtitle
+        {%- endcomment -%}
+        <h1>
+          <span role="text">
+            {{ page.title }}
+            {% if page.mini_hub_topic %}
+            <span class="nhsuk-caption-xl nhsuk-caption--bottom">
+              <span class="nhsuk-u-visually-hidden">
+                -
+              </span>
+              {{ page.mini_hub_topic }}
+            </span>
+            {% endif %}
+          </span>
+        </h1>
+
+        {%- comment -%}
+        Contents list navigation
+        {%- endcomment -%}
+        {% if page.mini_hub_pages %}
+        {% include components/contents-list.html items=page.mini_hub_pages %}
+        {% endif %}
+
+        {%- comment -%}
+        Page content
+        {%- endcomment -%}
+        {{ content }}
+
+        {%- comment -%}
+        Pagination navigation
+        {%- endcomment -%}
+        {% if page.previous_page or page.next_page %}
+        {% include components/pagination.html previous=page.previous_page next=page.next_page %}
+        {% endif %}
+
+      </div>
+    </div>
+  </main>
+</div>
diff --git a/docs/pages/get-started/check-which-features-you-need-and-register.md b/docs/pages/get-started/check-which-features-you-need-and-register.md
new file mode 100644
index 00000000..6ca6efea
--- /dev/null
+++ b/docs/pages/get-started/check-which-features-you-need-and-register.md
@@ -0,0 +1,25 @@
+---
+layout: mini-hub
+title: Check which features you need and register
+nav_order: 6
+permalink: /get-started/check-which-features-you-need-and-register
+mini_hub_topic: Answer a few questions to see which features you need before you register
+mini_hub_pages:
+  - title: Check you can use NHS Notify
+    url: /get-started/check-you-can-use-nhs-notify
+  - title: Read and understand our terms of service
+    url: /get-started/read-and-understand-our-terms-of-service
+  - title: Understand our onboarding timescales
+    url: /get-started/understand-onboarding-timescales
+  - title: Check you are ready for integration
+    url: /get-started/check-you-are-ready-for-integration
+  - title: Check which features you need and register
+    url:
+    current: true
+previous_page:
+  title: Check you are ready for integration
+  url: /get-started/check-you-are-ready-for-integration
+next_page:
+---
+
+Link to decision tree and register interest form.
diff --git a/docs/pages/get-started/check-you-are-ready-for-integration.md b/docs/pages/get-started/check-you-are-ready-for-integration.md
new file mode 100644
index 00000000..7f46c727
--- /dev/null
+++ b/docs/pages/get-started/check-you-are-ready-for-integration.md
@@ -0,0 +1,184 @@
+---
+layout: mini-hub
+title: Check you are ready for integration
+nav_order: 5
+permalink: /get-started/check-you-are-ready-for-integration
+mini_hub_topic: You must follow the steps to prepare for integration
+mini_hub_pages:
+  - title: Check you can use NHS Notify
+    url: /get-started/check-you-can-use-nhs-notify
+  - title: Read and understand our terms of service
+    url: /get-started/read-and-understand-our-terms-of-service
+  - title: Understand our onboarding timescales
+    url: /get-started/understand-onboarding-timescales
+  - title: Check you are ready for integration
+    url:
+    current: true
+  - title: Check which features you need and register
+    url: /get-started/check-which-features-you-need-and-register
+previous_page:
+  title: Understand our onboarding timescales
+  url: /get-started/understand-onboarding-timescales
+next_page:
+  title: Check which features you need and register
+  url: /get-started/check-which-features-you-need-and-register
+---
+
+## 1. Prepare your integration
+
+You must prepare your integration before you can get access to NHS Notify's integration environment.
+
+You'll need technical or developer support to complete tasks in this step.
+
+### If you're using NHS Notify API
+
+You'll need to:
+
+{% include components/details.html
+heading='Set up your APIM application ID'
+text="To set up an APIM application ID, you need to:
+
+1. <a href='https://digital.nhs.uk/developer' target='_blank'>Sign in to your NHS Digital developer account (opens in a new tab)</a>.
+2. Create an APIM application.
+3. Select 'integration test' as the environment.
+4. Select 'Communications Manager (integration environment)' as the connected API.
+   "
+   %}
+
+{% include components/details.html
+heading='Choose how you want to see your message performance'
+text="To see how your messages perform, you can <a href='https://digital.nhs.uk/developer/api-catalogue/nhs-notify#get-/v1/messages/-messageId-' target='_blank'>get the status of a message (opens in a new tab)</a> or choose to receive <a href='https://digital.nhs.uk/developer/api-catalogue/nhs-notify#post-/%3Cclient-provided-message-status-URI%3E' target='_blank'>realtime message callbacks (opens in a new tab)</a>.
+
+If you want to receive realtime message status callbacks, you'll need to:
+
+- decide which [message, channel or supplier statuses](/using-nhs-notify/message-channel-supplier-status) you want to receive
+- prepare an endpoint URL for your integration
+  "
+  %}
+
+### If you're using NHS Notify MESH
+
+You'll need to:
+
+1. <a href="https://digital.nhs.uk/developer/api-catalogue/nhs-notify-mesh/set-up-nhs-notify-mesh#set-up-your-mesh-mailboxes" target="_blank">Set up your MESH mailboxes (opens in a new tab)</a> and make a note of their IDs.
+2. Decide which reports you want when you get reports on how your messages perform.
+
+## 2. Confirm your setup to get access to our integration environment
+
+You must confirm how you'll be set up with NHS Notify using our online form so we can prepare your integration environment to meet your needs.
+
+{% include components/inset-text.html
+  text='Only complete the online form and confirm your setup if you’ve been invited to onboard.'
+  classes='nhsuk-u-margin-top-2'
+%}
+
+{% include components/action-link.html
+    url='https://forms.office.com/Pages/ResponsePage.aspx?id=slTDN7CF9UeyIge0jXdO4-wXWyN79ZdLkmec1Fsc491UNFRYSDFTOUs5TzZQUjlOVUlGWTQxQTlMQy4u'
+    text='Confirm your setup with NHS Notify'
+%}
+
+### Before you confirm your setup
+
+In the form you'll be asked to:
+
+{% include components/details.html
+heading='Confirm your use case'
+text='You can only use NHS Notify if your organisation or service sends messages that are:
+
+- [part of a campaign](/using-nhs-notify/campaigns)
+- [triggered when something happens in your service](/using-nhs-notify/event-based-messaging)
+- [sent directly on a one-to-one basis](/using-nhs-notify/direct-messaging)
+  '
+  %}
+
+{% include components/details.html
+heading='Provide your message sender names'
+text='When you send messages you’ll need to tell your recipients who your messages are from by creating message sender names.
+
+Before you provide your message sender names, you should understand more about:
+
+- [NHS App sender names](/using-nhs-notify/tell-recipients-who-your-messages-are-from#nhs-app-sender-name)
+- [email sender names and from addresses](/using-nhs-notify/tell-recipients-who-your-messages-are-from#email-sender-name-and-from-email-address)
+- [email reply-to email addresses](/using-nhs-notify/tell-recipients-who-your-messages-are-from#reply-to-email-address)
+- [text message sender names](/using-nhs-notify/tell-recipients-who-your-messages-are-from#text-message-sender-name)
+  '
+  %}
+
+{% include components/details.html
+heading='Provide more detail about your messages and how they’ll be sent'
+text='You’ll be asked if your organisation or service will:
+
+- have finished drafts of the messages you want to send
+- send NHS App messages and if so, which links and URLs you’ll include
+- send letters in other languages and if so, which languages
+- send letters in accessible formats and if so, which formats
+- use Personal Demographics Service (PDS) fields
+- have your PDS test data ready
+- use custom personalisation fields
+- have test data prepared for your custom personalisation fields
+
+The form will also ask for the routing plans that you want to use for your messages.
+'
+%}
+
+{% include components/details.html
+heading='Tell us who will create and submit templates'
+text='You do not need to do this if you send direct messages and use free-text inputs.
+
+When you get access to NHS Notify’s integration environment, you’ll need to [create and submit your templates](/using-nhs-notify/create-and-submit-a-template). These templates will be used as the messages you send when you go live.
+
+To access this feature, you must nominate someone in your organisation or service to sign in with NHS Notify. This is because creating and submitting templates is only available to one person in an organisation or service at this time.
+
+To sign into NHS Notify you must have a Care Identity (CIS2 authentication). If you do not have a Care Identity, we can help you create one.
+'
+%}
+
+{% include components/details.html
+heading='Give accurate estimates on your message volumes and frequency'
+text='We need to understand how many messages you need to send and how often to set up your integration environment.
+
+You’ll need to provide:
+
+- how many messages you want to send per day
+- the maximum amount of messages you might send per day
+  '
+  %}
+
+After you submit the form, it will be reviewed by NHS Notify's onboarding team.
+
+They'll contact you to either:
+
+- ask you about some of the answers you provided
+- provide access to NHS Notify's integration environment
+
+## 3. Build your integration
+
+Once you get access to our integration environment, you can start building your integration with <a href="https://digital.nhs.uk/developer/api-catalogue/nhs-notify" target="_blank">NHS Notify API (opens in a new tab)</a> or <a href="https://digital.nhs.uk/developer/api-catalogue/nhs-notify-mesh" target="_blank">NHS Notify MESH (opens in a new tab)</a>.
+
+How you build your integration to meet your needs is your responsibility.
+
+If you're sending campaign or event based messages, you need to create and submit your templates during this step. You will also need to [approve your messages before we send them]({% link pages/using-nhs-notify/approve-your-messages.md %}).
+
+## 4. Complete integration testing
+
+You'll need to [complete integration testing]({% link pages/using-nhs-notify/complete-your-testing.md %}) to make sure you're ready to start sending messages with NHS Notify.
+
+If you're sending NHS App messages, you'll also need to [complete NHS App testing]({% link pages/using-nhs-notify/complete-your-testing.md %}).
+
+### If you're using NHS Notify API
+
+Your onboarding manager will ask for your:
+
+- production (PROD) application name
+- PROD application ID
+- consumer organisation name
+- JWKS resource URL (if you’re self-hosting)
+- key ID for JWKS and public key (if NHS Notify is hosting your keys via APIM)
+
+### If you’re using NHS Notify MESH
+
+Your onboarding manager will ask for your PROD Mesh Mailbox ID.
+
+## Next step
+
+Once you've completed all these tasks, you can check which NHS Notify features you'll need and register your interest.
diff --git a/docs/pages/get-started/check-you-can-use-nhs-notify.md b/docs/pages/get-started/check-you-can-use-nhs-notify.md
new file mode 100644
index 00000000..b9e53063
--- /dev/null
+++ b/docs/pages/get-started/check-you-can-use-nhs-notify.md
@@ -0,0 +1,71 @@
+---
+layout: mini-hub
+title: Check you can use NHS Notify
+nav_order: 2
+permalink: /get-started/check-you-can-use-nhs-notify
+mini_hub_topic: How to get prepared and start using NHS Notify
+mini_hub_pages:
+  - title: Check you can use NHS Notify
+    url:
+    current: true
+  - title: Read and understand our terms of service
+    url: /get-started/read-and-understand-our-terms-of-service
+  - title: Understand our onboarding timescales
+    url: /get-started/understand-onboarding-timescales
+  - title: Check you are ready for integration
+    url: /get-started/check-you-are-ready-for-integration
+  - title: Check which features you need and register
+    url: /get-started/check-which-features-you-need-and-register
+previous_page:
+next_page:
+  title: Read and understand our terms of service
+  url: /get-started/read-and-understand-our-terms-of-service
+---
+
+What you need before you start.
+
+## Organisation type and funding
+
+You must:
+
+- be funded, directly or indirectly, by the NHS or NHS England
+- have funding or a budget agreed for sending messages
+
+## Message types and content
+
+You must:
+
+- intend to only send communications to patients or other members of the public – NHS Notify cannot be used to message NHS staff
+- not use NHS Notify to send marketing communications
+- check if other organisations or teams within NHS are already sending messages about the same subject matter
+
+{% include components/inset-text.html
+  text='If you intend to add links in NHS App messages, you must also onboard to NHS Login'
+  classes='nhsuk-u-margin-top-2'
+%}
+
+## Commercial and data
+
+You must:
+
+- have a way to get the NHS numbers of your recipients
+- be prepared to sign a connection agreement as an NHS England organisation
+- be prepared to sign our Memorandum of Understanding and agree to our Payment terms
+
+## Technical preparation
+
+You must complete:
+
+- connection to MESH if you intend to use it for integration
+- all sandbox testing
+
+You must also have the right technical support available to build your integration with NHS Notify:
+
+- Tester
+- Clinical safety advisor
+- Technical advisor
+- Information governance or security advisor
+
+## Next step
+
+If you meet all these criteria, you now need to make sure you’re ready commercially.
diff --git a/docs/pages/get-started/get-started.md b/docs/pages/get-started/get-started.md
index 77005dbd..9c5fbb37 100644
--- a/docs/pages/get-started/get-started.md
+++ b/docs/pages/get-started/get-started.md
@@ -5,32 +5,19 @@
 layout: page
 title: Get started
 nav_order: 1
-has_children: true
+has_children: false
 permalink: /get-started/
 ---
 
-## 1. Check if NHS Notify is right for you
+Before we can invite you to register your interest in using NHS Notify, you need to check:
 
-You can only use NHS Notify if your organisation or service sends:
+- your organisation can use it
+- it's the right messaging product for your needs
 
-- [event-based messages]({% link pages/about/event-based-messaging.md %})
-- [direct messages]({% link pages/about/direct-messaging.md %})
-- [messages that are part of a campaign]({% link pages/about/campaigns.md %})
-
-You also need to have:
-
-- funding or a budget agreed for sending messages
-- a way to get the NHS numbers of your recipients
-- technical or developer support to build your integration with NHS Notify
-
-You should also know [how to onboard with NHS Notify]({% link pages/get-started/onboard-with-notify.md %}).
-
-## 2. Register your interest
-
-Complete the following form to register your interest with NHS Notify. This will open in a new tab.
+The following steps will help you check this.
 
 {% include components/button.html
-    text="Register your interest"
-    url="https://forms.office.com/Pages/ResponsePage.aspx?id=slTDN7CF9UeyIge0jXdO4-wXWyN79ZdLkmec1Fsc491UNUNJUkpPTjBXMjdZM0xZT0ZHRUxBNFVWMy4u"
+    text="Check you can use NHS Notify"
+    url="/get-started/check-you-can-use-nhs-notify"
     target="_blank"
 %}
diff --git a/docs/pages/get-started/onboard-with-notify.md b/docs/pages/get-started/onboard-with-notify.md
index 153a61f2..1277fe7b 100644
--- a/docs/pages/get-started/onboard-with-notify.md
+++ b/docs/pages/get-started/onboard-with-notify.md
@@ -1,5 +1,5 @@
----
 # Feel free to add content and custom Front Matter to this file.
+
 # To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
 
 layout: page
@@ -7,6 +7,7 @@ title: Onboard with NHS Notify
 parent: Get started
 nav_order: 2
 permalink: /get-started/onboard-with-nhs-notify
+
 ---
 
 Use this page to find out what you need to do step by step to onboard with NHS Notify.
diff --git a/docs/pages/get-started/read-and-understand-our-terms-of-service.md b/docs/pages/get-started/read-and-understand-our-terms-of-service.md
new file mode 100644
index 00000000..966791c9
--- /dev/null
+++ b/docs/pages/get-started/read-and-understand-our-terms-of-service.md
@@ -0,0 +1,80 @@
+---
+layout: mini-hub
+title: Read and understand our terms of service
+nav_order: 3
+permalink: /get-started/read-and-understand-our-terms-of-service
+mini_hub_topic: You must read and understand our terms of service before you register
+mini_hub_pages:
+  - title: Check you can use NHS Notify
+    url: /get-started/check-you-can-use-nhs-notify
+  - title: Read and understand our terms of service
+    url:
+    current: true
+  - title: Understand our onboarding timescales
+    url: /get-started/understand-onboarding-timescales
+  - title: Check you are ready for integration
+    url: /get-started/check-you-are-ready-for-integration
+  - title: Check which features you need and register
+    url: /get-started/check-which-features-you-need-and-register
+previous_page:
+  title: Check you can use NHS Notify
+  url: /get-started/
+next_page:
+  title: Understand our onboarding timescales
+  url: /get-started/understand-onboarding-timescales
+---
+
+You must read and understand all of our service terms and get a legal opinion before you continue.
+
+## Online connection agreement
+
+If you’re an NHS England organisation, you’ll need to sign our [online connection agreement (opens in a new tab)](https://digital.nhs.uk/developer/guides-and-documentation/online-connection-agreement){:target="\_blank"}.
+
+## Payment terms
+
+The payment terms document is a financial agreement that sets out our charges and rules.
+
+It will forms part of your wider connection agreement with NHS England.
+
+[Read and understand our payment terms (opens in a new tab)]({% link pages/pricing-and-commercial/how-to-pay.md %}){:target="\_blank"}
+
+## Memorandum of understanding
+
+To use NHS Notify, you must agree to the terms in this memorandum of understanding and the payment terms.
+
+We’ll send you the memorandum of understanding to sign digitally during onboarding. You must sign this before you can go live with NHS Notify.
+
+[Read and understand our memorandum of understanding (opens in a new tab)]({% link pages/pricing-and-commercial/memorandum-of-understanding.md %}){:target="\_blank"}
+
+## General terms and conditions
+
+The purpose of the NHS Notify service terms and conditions is to outline the criteria that:
+
+- a Connecting Party must be compliant with
+- are mandatory to be able to use the NHS Notify service
+
+[Read and understand our general terms and conditions (opens in a new tab)](https://digital.nhs.uk/services/nhs-notify/terms-and-conditions){:target="\_blank"}
+
+## Security
+
+NHS Notify is part of NHS England and is built for the security needs of its organisations and services.
+
+[Read and understand our security features and policy (opens in a new tab)]({% link pages/footer/security.md %}){:target="\_blank"}
+
+When you’ve read and understood these and received appropriate legal advice, you must now check you’re ready to integrate.
+
+## Acceptable use policy
+
+All End User Organisations using the NHS Notify service should read and abide by this NHS Notify acceptable use policy and the connection agreement acceptable use policy.
+
+[Read and understand our Acceptable use policy (opens in a new tab)](https://digital.nhs.uk/services/nhs-notify/acceptable-use-policy){:target="\_blank"}
+
+## Privacy (transparency notice)
+
+All End User Organisations using the NHS Notify service should read and abide by our privacy (transparency) notice.
+
+[Read and understand our privacy policy (opens in a new tab)](https://digital.nhs.uk/services/nhs-notify/transparency-notice){:target="\_blank"}
+
+## Next step
+
+Once you've read and understood our service terms, make sure you understand our onboarding timescales.
diff --git a/docs/pages/get-started/understand-onboarding-timescales.md b/docs/pages/get-started/understand-onboarding-timescales.md
new file mode 100644
index 00000000..7f4691a6
--- /dev/null
+++ b/docs/pages/get-started/understand-onboarding-timescales.md
@@ -0,0 +1,31 @@
+---
+layout: mini-hub
+title: Understand our onboarding timescales
+nav_order: 4
+permalink: /get-started/understand-onboarding-timescales
+mini_hub_topic: You should understand our onboarding timescales before you register
+mini_hub_pages:
+  - title: Check you can use NHS Notify
+    url: /get-started/check-you-can-use-nhs-notify
+  - title: Read and understand our terms of service
+    url: /get-started/read-and-understand-our-terms-of-service
+  - title: Understand our onboarding timescales
+    url:
+    current: true
+  - title: Check you are ready for integration
+    url: /get-started/check-you-are-ready-for-integration
+  - title: Check which features you need and register
+    url: /get-started/check-which-features-you-need-and-register
+previous_page:
+  title: Read and understand our terms of service
+  url: /get-started/read-and-understand-our-terms-of-service
+next_page:
+  title: Check you are ready for integration
+  url: /get-started/check-you-are-ready-for-integration
+---
+
+You must understand how long it might take to go live with NHS Notify so you can plan your integration.
+
+CONTENT TBC
+
+## Next step
diff --git a/scripts/config/pre-commit.yaml b/scripts/config/pre-commit.yaml
index 37ca6375..3156979c 100644
--- a/scripts/config/pre-commit.yaml
+++ b/scripts/config/pre-commit.yaml
@@ -31,10 +31,3 @@ repos:
     args: ["check=staged-changes"]
     language: script
     pass_filenames: false
-- repo: local
-  hooks:
-  - id: lint-terraform
-    name: Lint Terraform
-    entry: ./scripts/githooks/check-terraform-format.sh
-    language: script
-    pass_filenames: false
diff --git a/scripts/config/vale/styles/Vocab/words/accept.txt b/scripts/config/vale/styles/config/vocabularies/words/accept.txt
similarity index 100%
rename from scripts/config/vale/styles/Vocab/words/accept.txt
rename to scripts/config/vale/styles/config/vocabularies/words/accept.txt
diff --git a/scripts/config/vale/styles/Vocab/words/reject.txt b/scripts/config/vale/styles/config/vocabularies/words/reject.txt
similarity index 100%
rename from scripts/config/vale/styles/Vocab/words/reject.txt
rename to scripts/config/vale/styles/config/vocabularies/words/reject.txt