diff --git a/devdocs/todo.txt b/devdocs/todo.txt
index b2727003..8fc505a9 100644
--- a/devdocs/todo.txt
+++ b/devdocs/todo.txt
@@ -1,17 +1,16 @@
 # now
 
+- License agreement for QBI - update, is a copy of ayaNova server license agreement right now
+- DOCS for QBI
+- Post as qbi rc.1
+- build AyaNova server package fresh, update test copy, test from here with downloaded qbi rc.1 build 
+- If all is well then post about it on the forum
+
+
+
+- DOCST for integration UI
+	todo: document availability of integration objects and routes with examples in developer section (just quickie)
 
-DOING: adding integration objects and routes for qbi and others
-	todo NEXT: Have models and schema done, now need biz object and routes
-		should require biz admin to install initially an integration but subsequent can use it's own roles as required
-		it isn't really a normal biz object so find a similar one that doesn't need to implement corebizobject stuff
-			unless it does for UI and controlling from admin area
-			giong to need an icon for this as well as translations for front end
-	todo: on delete integration must cascade delete integration log as well so make sure that's defined in the schema
-	todo: document this in the developer section
-	todo: needs a front end to show the integration log, the integrations as a collection list and openable item where it can be disabled, deleted etc
-		needs to be available to bizadmin I guess and possibly accounting?? or should each integration control which roles see it??
-		or should the UI for each integration be *in* the integration itself and also in one place for biz admin to super control all integrations and troubleshoot log sb available to ops
 	todo: doc front end additions for integrations
 		in docs the role rights to integration object is:
 		 Change =  AuthorizationRoles.BizAdmin
@@ -38,11 +37,9 @@ DOING: adding integration objects and routes for qbi and others
 
 			However, the UI at client likely only shows for a biz admin role so these are actually two separate things to document unlike normally when the ayaclient is the only thing to document
 
-JUST DONE: posted rc.1 updated forum (and turned off "views" column in custom css in forum as well it was looking pathetic)
-
-Post rc.2 for QBI integration as well as QBI once docs are ready as a stalling tactic?
 
 
+**THIS BETA BIT BELOW IS DONE..NO?***
 TODO: REMOVE BETA TEST DOCS AND LICENSE FROM MANUAL
 	switch to real license and docs
 	CONFIRM ALL PLATFORMS
@@ -53,23 +50,14 @@ TODO: remove beta banner from login form
 todo: BIG PICTURE
 
 	
-	QBI NEEDS TO BE DONE BEFORE RAVEN RELEASE AS RAVEN MAY REQUIRE MORE OBJECTS FOR DATA MAPPING AND OPTIONS SAVING IN CENTRAL LOCATION ETC
-		This saves users needing to back up their local QBI only settings and mappings separate from RAVEN backup
-		Integration objects and integration log plus front end to see that shit and remove / control it
-
-	QBI order of release decision (does raven qbi need to be released along with v8 simultaneously??)
-		if yes then need to whip that shit up pronto with a beta to go with RC for raven
-		figure out how many active qbi users, like will this prevent most people from upgrading?
-		Make a QBI test app but not completely filled in yet in vstudio on v7 laptop then try to open and build in .net core??
-		or figure out the state of .net windows apps, actually also was going to look into platform support for qb desktop api just to see whats out there
-		Beta release QBI (not sure how the fuck that will work or even how to test it but whatever)
-		need a trial of qb desktop maybe
 	
-	Outlook integration extension??
+Outlook integration extension??
+	This can wait until after official release when / if people ask for it
 		wtf to do with that, are there any other extensions actively being sold that I need to worry about?
 		this should probably be more like office365 integration at this point, need stats on desktop outlook but it must be vanishingly small aty this point?
 
-	Pricing policy and plan
+
+YES SOONEST - Pricing policy and plan
 	New website at the ready
 		including live eval as planned below
 	New Rockfish ASAP
@@ -79,6 +67,7 @@ todo: validate the rate limiting by tailing the error log and hitting test raven
 
 
 todo: QBOI deprecation
+	BUT...this is probably going to be needed for future again so keep on back burner 
 	done: QBOI removed from website except still in docs and in trial installer
 	done: Product is set to inactive with ShareIt, no one can buy it now
 	OUTSTANDING: I will need to remove it from the AyaNova installer completely