diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 0df005bb..018f28ee 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -3,24 +3,6 @@
 PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route changes etc then back here in order lowest level first as affects the most stuff exponentially so best to do it early
 =-=-=-=-
 
-
-todo: OPS routes CLIENT UI
-	- Backup, restore https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3369
-		
-		Is this two forms or one form?
-			A good philosophy should probably be one form for one task, however people hate naving around too much, however this is not a common thing to much with
-			Viewing backup is a very common and seeing list etc
-			Triggering backup and adjusting settings is very less common
-			maybe it's two forms seperately, not like workorder where it's critical how to move around in hierarchy
-
-		Lists all backup files
-			with download links
-			Backup NOW button triggers backup somehow tied to list, in header or worst case scenario in menu but like to expose it directly
-				Are you sure prompt, will lock server until backup is completed
-		
-		Shows backup settings in editable form
-			can update and save this is the editable content of the form
-
 		
 todo: is client sending jwt with pre-login get server trial status route?  
 	because I see a not authorized response when I go to login page from a previously logged in session