diff --git a/devdocs/todo.txt b/devdocs/todo.txt
index baf5a244..0f377048 100644
--- a/devdocs/todo.txt
+++ b/devdocs/todo.txt
@@ -14,17 +14,25 @@ CURRENT MASTER PLAN IN CLIENT TODO
 REALLY MAKING MORE PROGRESS WHEN CLIENT DEV DRIVES BACKEND DEV, STICK TO THAT!!
 -----------------------
 
-TODO: return the list as objects as specified
+GRID LISTS TODO NOW:
+	- Make a joined table list for development 	
+		- Widget list with User and their email
+	- Make regular list of widgets with all columns no joins as second list
+	- Once both lists are working, abstract away the commonalities into other classes
+	- There's going to be a fair number of data source lists in routes so..
+		- NOT immediate issue, but once the lists are working...
+		- Do I make a route for each one or user provides a key of which list they want and that goes into a single route to return the data?
+		- What about when there are dozens of reports, do they all hang off each object type controller or is there just a central data list route for all combined?
+			- i.e. if I want to make a widget->user->Email report and a separate user email report are they each in widget and user
+			- Or, because they are read only lists used for many things do they just go into a central route for read only lists?
+			- Also rights issues might affect this..?
+	- Update tests when appropriate (when it's working fully and not mocked)
+	- Mock return objects for now with the new fields to include in the response see core-main-grids.txt and core-display-format-template-system.txt
 
-TODO: Make a joined table list for development	
-	- Widget list with User and their email
-	- Working query:
-		/*
-                    Select awidget.id as widgetid, awidget.name as widgetname, auser.name as username, auser.id as userid, auseroptions.emailaddress
-                    from awidget
-                    left outer join auser on (awidget.userid=auser.id)
-                    left outer join auseroptions on (auser.id=auseroptions.userid)
-                    */
+
+
+
+TODO: return the list as objects as specified
 
 CLIENT CUSTOM FIELDS CHANGE
 	- Must use numeric instead of text values now
@@ -34,18 +42,6 @@ TEST CHANGES
 	- Must use numeric instead of text values now
 	- Test datatypes enum picklist 
 
-GRID LISTS TODO NOW:
-
-	- RECODE GETLIST in WidgetBiz
-	- Return JSON and internally work with JSON so the list can return dynamic object
-		- https://devblogs.microsoft.com/dotnet/try-the-new-system-text-json-apis/
-		- https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#fast-built-in-json-support
-	- Combine PickList route and WidgetList route into single "List" route with an internal nameof "WidgetList"
-		- if mini=true then it sends back the two column result templated
-		- Otherwise it sends back the full list (templated)
-	- NOTE: REPORT LIST will be it's own kettle of fish so to speak so don't concern about it now YAGNI TTM!
-	- Update tests when appropriate (when it's working fully and not mocked)
-	- Mock return objects for now with the new fields to include in the response see core-main-grids.txt and core-display-format-template-system.txt