diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index a146ede4..8b5868a2 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -5,8 +5,20 @@
 REPORTING
 
 TODO:
-	Plan how it would work, templating engine runs how, what steps lead from render route to produced report?
-	simlute it on paper before coding it
+	Investigate how it would work through mockups, templating engine runs how, what steps lead from render route to produced report?
+	Steps:
+		Render route hit 
+			template with content, script and style is retrieved
+				(for testing from default report in memory or whatever is easiest)
+			Datasource determined (for testing from report default)
+			render engine determined (for testing from report default)
+			locale determined (for testing from report default)
+			Render out and return
+				call render engine, provide report and data as one object I guess
+					check with jsreport source, what do they do for this?
+				return results to browser
+
+
 	Review jsreport modules for each aspect to get an idea what they dealt with for each type of op
 
 	Find c# versions of all required tools to see if going to need dependency on Node or not
@@ -19,6 +31,12 @@ TODO:
 		just hit a route to trigger a static test then expand from there doing all the trickiest stuff first as proof of concept.
 		Once it renders a report of each type we need in mock then can actually code
 
+	TODO: CODE TEST:
+		Make an initial report controller
+		Make a test render route for each type of test want to do (easier than a lot of other options)
+			this way can just hit the route and view in the browser, rest is static at server
+		Make a test render method right inside teh controller for initial testing
+			headless chrome first, chrome already installed can probably just run it
 
 
 CLIENT UI