diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index fb745bbe..baf965c1 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -46,10 +46,17 @@ CURRENT TODOs
 =-=-=-=-=-=-=
 
 
-TODO: Time to consider layout of main shell as the grids stuff is starting to touch on it
+TODO: Time to LOCK IN the layout of main shell as the grids and much other stuff is starting to touch on it and time is over for playing with the design it needs to be cemented
+	- PLAN OUT NAVIGATION AND MAIN APPEARANCE AND STUB OUT AS MUCH AS POSSIBLE NOW
 	- Right now it's just a bunch of sample stuff, not realistic
 	- Navigation panel can support up to 3 layers https://vuetifyjs.com/en/components/lists#nested-lists
 		- So, could replicate existing v7 nav panel essentially, just not as many layers for workorders likely but who knows at this point, cross that ditch when...etc etc
+		- v7 nav panel has 12 sections that in turn contain many or few things
+			- ? Consider if any can be consolidated, 12 is a lot and many things are the same things, also quote , pm service wo all have many levels but I'm guessing I won't be doing it that way again so maybe all types can go into a single top level service item  and then each one is a single item
+				- i.e. take away the tree for service workorders -> items and only have service workorders?  Is this doable?
+	- NAVIGATION PANEL and ROLES
+		- RAVEN nav panels are supposed to comparmentalize by roles which is a good idea so 
+			- Subitems should go into the appropriate role, not necessarily as it was in v7
 	- TTM 
 		- This is increasingly becoming the driving force here
 		- Not going with the fancy modular recomposable UI and I know v7 style will work	
@@ -57,6 +64,8 @@ TODO: Time to consider layout of main shell as the grids stuff is starting to to
 	- Consider LOGOUT as a button at the very bottom of the nav menu using the APPEND slot as it is done in this example here: https://vuetifyjs.com/en/components/navigation-drawers#colored-drawer
 
 
+
+
 TODO: Two kinds of mass fetch records in RAVEN
 	- 1) Reporting records
 		- Need to filter, sort and will probably pull in many different tables so would be a set of dedicated objects for that purpose at server 
@@ -68,6 +77,8 @@ TODO: Two kinds of mass fetch records in RAVEN
 		- Need to filter sort and search
 		- Uses templated name display format
 		- Server needs to take into account display format
+	- ACTION required: 
+		- Make sure the server supports this
 
 TODO: Errors - make sure all user displayed errors have an error number if they might be something tech support needs to know (case 1854)
 	- I guess this is a LT feature really