diff --git a/devdocs/todo.txt b/devdocs/todo.txt
index b06c7a45..4570bc69 100644
--- a/devdocs/todo.txt
+++ b/devdocs/todo.txt
@@ -19,9 +19,7 @@ CODING WORK
 +++++++++++
 
 Overall plan for now: anything standing in the way of making the initial client shell UI needs to be done first, everything else can wait
-	- Audit log
-		- CRUD methods for widget
-		- replicate crud to other objects
+	- Audit log		
 		- Route for retrieving as log format for reading (like reports: one for specific object id and type, one for user id as log of what they've been doing etc)
 		- Test with huge dataset
 	- Localized text
@@ -57,6 +55,18 @@ Once I can make the client I need to get into that and make the shell and initia
 	later
 	- Widget CRUD and lists
 		- All input controls and date localization etc etc
+	- LOAD TESTER see below...
+
+LOAD TESTER
+-----------
+After very initial client stuff but before getting too deep into anything, need a load tester that drives the client and makes hundreds of thousands of objects and really exercises the client
+and backend.  I want to know what happens under typical heavy usage simulating months to years of work in just a few minutes.
+I'm guessing something that autodrives a browser or simulates one to access via client UI for full end to end testing.
+	- Should be configurable to simulate various loads:
+		- Smoke test (Quick bug test): excercises one of everything once only looking for fundamental problems
+		- Load test (Slower longer test to look for scaling issues related to a huge, busy office): exercises typical daily load of very large office but configurable to run in simulated days, so
+			can run it as a simulated week with 7 or month with 30 or years by entering in the number of days to simulate.  Would be nice if it did month end type stuff or delayed then billed out etc.
+