diff --git a/getQuestionsData.html b/getQuestionsData.html
new file mode 100644
index 0000000..4451645
--- /dev/null
+++ b/getQuestionsData.html
@@ -0,0 +1,31 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+    <meta charset="UTF-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Customised Qualifiers</title>
+</head>
+<body>
+    <h1>Importing of customised qualifiers</h1>
+
+    <p>This form allows you to export the customised qualifying information relating to the survey</p>
+    <p>You will need to enter the appropriate surveyId, and then click submit, and the data will be imported
+        into the <a href='./reportTemplate.html'>analysis tool</a></p>
+    </p>
+
+    <p>If you enter no surveyId or invalid one, then the script will check for that value and create a template anyway. At
+        some point in the future these invalid templates may have to be cleaned up?
+    </p>
+    
+
+  <form action="getQuestionsData.php" method="POST">
+    <label for="surveyId">Survey ID:</label>
+    <input type="text" id="surveyId" name="surveyId" required>
+    <button type="submit">Submit</button>
+  </form>
+
+
+
+
+</body>
+</html>
\ No newline at end of file
diff --git a/getQuestionsData.php b/getQuestionsData.php
index 7ecdc2f..7adc26c 100644
--- a/getQuestionsData.php
+++ b/getQuestionsData.php
@@ -73,7 +73,7 @@ if ($stmt->fetch()) {
     echo "This process only ever needs to be carried out once for each survey.<br>".PHP_EOL;
     echo "Skipping data export.<br>".PHP_EOL;
     echo "<br><br>";
-    echo "You now need to <a href=''>go and export the answer data</a> before you can <a href='./reportTemplate.html'>get the survey reports</a>";
+    echo "You now need to <a href='./getSurveys.php'>go and export the answer data</a> before you can <a href='./reportTemplate.html'>get the survey reports</a>";
 
 
     return;
diff --git a/index.html b/index.html
index c0588f4..bb70beb 100644
--- a/index.html
+++ b/index.html
@@ -8,12 +8,14 @@
 <body>
     <h1>PROCESS</h1>
     <ul>
-        <li>1.  Get the survey identification number (SurveyID). This is a unique value associated with each survey and is of the 
+        <li>Get the survey identification number (SurveyID). This is a unique value associated with each survey and is of the 
             form SV_cwKjMqAqGxImjMG. All of them start with 'SV_' and there is then a random selection of characters. 
         </li>
-        <li>2.  Import the 'customised' qualifier questions into the database. This only has to be done once.</li>
-        <li>3.  Import the survey answers into the database. This only has to be done once, unless additional people complete
-            the survey, in which case repeating this process will import the additional completed surveys.
+        <li><a href='./getQuestionsData.html'>Import the 'customised' qualifier questions into the database.</a> This only has to be done once.</li>
+        <li><a href='./getSurveys.php'>Import the survey answers into the database.</a> This only has to be done once for each
+            survey, unless additional people complete the survey. If that happens, then repeating this process will import the additional completed surveys.
+        </li>
+        <li>Go to the <a href='./reportTemplate.html'>report template</a> and create the required analysis visuals for your report. 
         </li>
     </ul>
     
@@ -22,13 +24,13 @@
         "eoQ Framework - How to achieve great EO Template - 15 May 2025 Quality Assurance v2" 
         surveyId (SV_cwKjMqAqGxImjMG) or a clone of this survey.</p>
 
-    <p>This data is then saved into a local database in order to speed up display and avoid
+    <p>This data is then imported into a local database in order to speed up display and avoid
         costs associated with repeatedly accessing the QUALTRICS API. This requires 2 steps
         before the data can be used as outlined in the process above.
     </p>
 
     <p>Data in the database is then manipulated to produce the graphics using a custom graphics
-        library using d3.js to produce the visualisations that you see in the reportTemplate.html file.
+        library using d3.js to produce the visualisations that you see in the <a href='./reportTemplate.html'>reportTemplate</a> file.
     </p>
 
 </body>
