diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 272bbfa9..7dea7dc2 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -192,10 +192,12 @@ todo: workorder status list first, it's a table of created items, keep propertie
 	SelectRoles - who can select the status (still shows if they can't select but that's the current status, like active does)	
 		This is best handled at the client.  It prefetches all the status out of the normal picklist process, more like how other things are separately handled now without a picklist
 		client then knows if a status is available or not and can process to only present available ones
-		Server can use a biz rule to ensure that it can't be circumvented	
+		Server can use a biz rule to ensure that it can't be circumvented
+		UI defaults to any role	
 	DeselectRoles - who can unset this status (important for process control)
-	FinishedStatus bool - this is a final status indicating all work on the workorder is completed, affects notification etc			
-		when set this, lock is checked in UI automatically and they need to remove it to force unlock and final
+		UI defaults to any role
+	CompletedStatus bool - this is a final status indicating all work on the workorder is completed, affects notification etc				
+		UI defaults to false but when set to true auto sets lockworkorder to true (but user can just unset lockworkorder)
 	LockWorkorder - this status is considered read only and the workorder is locked
 		Just a read only thing, can just change status to "unlock" it
 		to support states where no one should work on a wo for whatever reason but it's not necessarily completed