diff --git a/ConceptualisationToR.md b/ConceptualisationToR.md
index de07539..a559734 100644
--- a/ConceptualisationToR.md
+++ b/ConceptualisationToR.md
@@ -4,14 +4,36 @@
 
 ### Scope
 
+> List and describe the scope of the project.
+
 ### Deliverables
 
+> List and describe the deliverables of the project.
+
 ## Project roles and responsibilities
 
+> Describe the roles and reponsibilities of the people involved in the project.
+
 ## Resources, financial and quality plan
 
+> Describe the resources needed and how they are going to be obtained, provided or paid for.
+> 
+> This means man-hours of effort, infrastructure, etc. and their cost.
+
 ## Work breakdown structure and schedule
 
+> Describe the project timeline and its main milestones.
+> 
+> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
+> 
+> Each project phase will have its own ToR in a separate file.
+
 ## Key issues and risks
 
+> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
+> 
+> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
+
 ## Assumptions and constrains
+
+> List of any significant assumptions we have made at the time of preparing the ToR.
diff --git a/FinalDesignDevelopment.md b/FinalDesignDevelopment.md
new file mode 100644
index 0000000..a1f39de
--- /dev/null
+++ b/FinalDesignDevelopment.md
@@ -0,0 +1,39 @@
+# Final Design and Development ToR
+
+## Project objectives
+
+### Scope
+
+> List and describe the scope of the project.
+
+### Deliverables
+
+> List and describe the deliverables of the project.
+
+## Project roles and responsibilities
+
+> Describe the roles and reponsibilities of the people involved in the project.
+
+## Resources, financial and quality plan
+
+> Describe the resources needed and how they are going to be obtained, provided or paid for.
+> 
+> This means man-hours of effort, infrastructure, etc. and their cost.
+
+## Work breakdown structure and schedule
+
+> Describe the project timeline and its main milestones.
+> 
+> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
+> 
+> Each project phase will have its own ToR in a separate file.
+
+## Key issues and risks
+
+> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
+> 
+> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
+
+## Assumptions and constrains
+
+> List of any significant assumptions we have made at the time of preparing the ToR.
diff --git a/Implementation.md b/Implementation.md
new file mode 100644
index 0000000..3fc7481
--- /dev/null
+++ b/Implementation.md
@@ -0,0 +1,39 @@
+# Implementation and Stabilisation ToR
+
+## Project objectives
+
+### Scope
+
+> List and describe the scope of the project.
+
+### Deliverables
+
+> List and describe the deliverables of the project.
+
+## Project roles and responsibilities
+
+> Describe the roles and reponsibilities of the people involved in the project.
+
+## Resources, financial and quality plan
+
+> Describe the resources needed and how they are going to be obtained, provided or paid for.
+> 
+> This means man-hours of effort, infrastructure, etc. and their cost.
+
+## Work breakdown structure and schedule
+
+> Describe the project timeline and its main milestones.
+> 
+> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
+> 
+> Each project phase will have its own ToR in a separate file.
+
+## Key issues and risks
+
+> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
+> 
+> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
+
+## Assumptions and constrains
+
+> List of any significant assumptions we have made at the time of preparing the ToR.
diff --git a/PIR.md b/PIR.md
new file mode 100644
index 0000000..183126f
--- /dev/null
+++ b/PIR.md
@@ -0,0 +1,39 @@
+# Post-Implementation Review ToR
+
+## Project objectives
+
+### Scope
+
+> List and describe the scope of the project.
+
+### Deliverables
+
+> List and describe the deliverables of the project.
+
+## Project roles and responsibilities
+
+> Describe the roles and reponsibilities of the people involved in the project.
+
+## Resources, financial and quality plan
+
+> Describe the resources needed and how they are going to be obtained, provided or paid for.
+> 
+> This means man-hours of effort, infrastructure, etc. and their cost.
+
+## Work breakdown structure and schedule
+
+> Describe the project timeline and its main milestones.
+> 
+> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
+> 
+> Each project phase will have its own ToR in a separate file.
+
+## Key issues and risks
+
+> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
+> 
+> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
+
+## Assumptions and constrains
+
+> List of any significant assumptions we have made at the time of preparing the ToR.
diff --git a/PilotDesignDevelopment.md b/PilotDesignDevelopment.md
new file mode 100644
index 0000000..a559734
--- /dev/null
+++ b/PilotDesignDevelopment.md
@@ -0,0 +1,39 @@
+# Conceptualisation ToR
+
+## Project objectives
+
+### Scope
+
+> List and describe the scope of the project.
+
+### Deliverables
+
+> List and describe the deliverables of the project.
+
+## Project roles and responsibilities
+
+> Describe the roles and reponsibilities of the people involved in the project.
+
+## Resources, financial and quality plan
+
+> Describe the resources needed and how they are going to be obtained, provided or paid for.
+> 
+> This means man-hours of effort, infrastructure, etc. and their cost.
+
+## Work breakdown structure and schedule
+
+> Describe the project timeline and its main milestones.
+> 
+> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
+> 
+> Each project phase will have its own ToR in a separate file.
+
+## Key issues and risks
+
+> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
+> 
+> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
+
+## Assumptions and constrains
+
+> List of any significant assumptions we have made at the time of preparing the ToR.
diff --git a/PilotExecution.md b/PilotExecution.md
new file mode 100644
index 0000000..f931f24
--- /dev/null
+++ b/PilotExecution.md
@@ -0,0 +1,39 @@
+# Pilot Execution ToR
+
+## Project objectives
+
+### Scope
+
+> List and describe the scope of the project.
+
+### Deliverables
+
+> List and describe the deliverables of the project.
+
+## Project roles and responsibilities
+
+> Describe the roles and reponsibilities of the people involved in the project.
+
+## Resources, financial and quality plan
+
+> Describe the resources needed and how they are going to be obtained, provided or paid for.
+> 
+> This means man-hours of effort, infrastructure, etc. and their cost.
+
+## Work breakdown structure and schedule
+
+> Describe the project timeline and its main milestones.
+> 
+> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
+> 
+> Each project phase will have its own ToR in a separate file.
+
+## Key issues and risks
+
+> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
+> 
+> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
+
+## Assumptions and constrains
+
+> List of any significant assumptions we have made at the time of preparing the ToR.
diff --git a/README.md b/README.md
index 4323357..cbc4494 100644
--- a/README.md
+++ b/README.md
@@ -93,15 +93,15 @@ Such eco-system is made of several components:
 
 - [Conceptualisation](ConceptualisationToR.md)
 
-- Pilot Design and Development
+- [Pilot Design and Development](PilotDesignDevelopment.md)
 
-- Pilot Execution
+- [Pilot Execution](PilotExecution.md)
 
-- Final Design and Development
+- [Final Design and Development](FinalDesignDevelopment.md)
 
-- Implementation and Stabilisation
+- [Implementation and Stabilisation](Implementation.md)
 
-- Post-Implementation Review
+- [Post-Implementation Review](PIR.md)
 
 ## Key issues and risks