diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 79a475da..5657afe5 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -382,32 +382,28 @@ todo: many biz objects are not using new PUT methodology
 
 
 
-CURRENTLY DOING: Signature boilerplate text from global settings
-	maybe store in global first fetch or cache if needed only??
-	won't change much but most people won't need it either
-	can I fetch it on first wo open like the rest of the bundle?? somehow?
+CURRENTLY DOING: 
 
-
-
-todo 3: signature: report helper display signature and form ui control to capture /display signature 
-	for both tech and customer
-	case 3682 implies code to steal to make signatures better so look into that
-	case 2052 is this one
-	case 3673 also directly related
-	v7 import - must put in block at least if not code immediately to import v7 sigs into svg format for display
-		also, depending on ease, it might make sense to have v8 server check type of image i.e. does it start with svg or not and 
-		then auto convert if necessary.
-
-	
-
-3720 3: BUMPABLE CASE I THINK  prevent double booking a tech (some kind of warning)
+3720 3: BUMPABLE CASE I THINK  prevent double booking a tech (some kind of warning)		
 		availability feature??? maybe bump as a new availablity feature where user picks from a popup schedule for that tech?
 		if not maybe a alert from the workorder itself when they save saying double booked??
 		Searching time series and userid is a bit slow maybe or needs custom query not ef able??
 
+		IDEA:
+			global setting allow double booking or not
+			if allowed then no check
+			if not allowed then validation code at server checks and barfs if already booked for that user 
+
 3873 3: subtree woitem lists implement
 	must be some planning on this, forget what I decided exactly
 
+3891 3: Implement a workable duplication system  
+	SEE CASE 3891 for duplicate at client idea
+	Also this is a "3" because this idea rocks and I will likely need to remove duplicate route from every biz object at server and replace with dupe at client instead
+		actually should be quick and easy theoretically since it's a slight variation of the technique used to make new objects and then move to their id with data intact
+		and just setting a few values to 0 or null like concurrency/ id etc
+
+
 todo 2: open object handler for workorder descendants **VERY IMPORTANT**
 	1) get the id of the workorder and item to open from the server using descendant to wo ID
 	2) pass that on to the workorder from 
@@ -418,8 +414,6 @@ todo: how to directly open a workorder quickly when you know the wo number??
 
 todo: picking from part assembly to populate a bunch of parts??
 
-todo 2-3: Implement a workable duplication system  
-	SEE CASE 3891 for duplicate at client idea
 	
 todo: as part of duplication above, REMOVE TEMPLATES ENTIRELY??
 	If can duplicate this way at client and can easily change customer etc do we even need the wo templates anymore?