diff --git a/exercises/exercise4/Exercise4_Description.md b/exercises/exercise4/Exercise4_Description.md
index 9db1371922dfacfed6a18d7aff54d73cea9f6896..e265db43f8af9e87cec709e44768697db610081f 100644
--- a/exercises/exercise4/Exercise4_Description.md
+++ b/exercises/exercise4/Exercise4_Description.md
@@ -19,7 +19,9 @@ Details:
     *   CAN_WRITE
     Your application will need to check that for any authenticated request the permissions. A GET request should only be able to be reached if the request is authenticated AND has the CAN_READ header set to true. All other requests should only be reachable if the the request is authenticated and CAN_WRITE is true. No request should be able to proceed unless authenticated first.  
 
-3. Lastly, you will need to define functions that validate the data in your requests. If the data does not match the fields in the struct you are storing you should respond with a 404 status error along with the message: "Invalid data for type <your type>"
+3. Lastly, you will need to define functions that validate the data in your requests. If the data does not match the fields in the struct you are storing you should respond with a 404 status error along with the message: "Invalid data for type <your type>"  
+
+4. You need to create a readme file named __DataAndRoutes.md__ in which you indicate what the data is your api is modeling (i.e. what is the struct you define) and what are all the routes you created.
 
 
 To deliver your submission you will need to commit your changes locally and push to your repo on the university gitlab server.