diff --git a/ayanova/src/components/work-order-items.vue b/ayanova/src/components/work-order-items.vue
index 5cdbdffa..8e74ce48 100644
--- a/ayanova/src/components/work-order-items.vue
+++ b/ayanova/src/components/work-order-items.vue
@@ -12,6 +12,39 @@
     <template v-if="pvm.hasSelectedWoItem">
       <!-- Workorder item "header" form here ??table shows same info as below in form, maybe table is not everything in the columns but just enough to select?? -->
       <!-- Has controls to navigate to other woitems so no need to go up and click on table if don't want to or it's huge -->
+      <!-- Want to support the case that when it's a single woitem workorder then user can just scroll down and enter shit and doesn't need to open or go anywhere to enter things all the way down
+        so a single workorderitem workorder would have all fields exposed and if any grandchildren those are entered in a single form too until the user has more than one 
+        
+        in v7 it's three clicks to go to a grandchild items specific field from the top header, woitem click -> left nav button row selection of area click -> grid row column click
+        in v8 it would be one more click then if it was a multi record grandchild but if it was a single record all teh way down then all would be exposed and visible at hand could go directly to the field in question
+            so in this concept every level exposes an edit form below a grid of one or more items, but grid doesn't show if there is one item so it's very clean.
+            if there is no record at that collection then just a click to add button as unobtrusive but clearly marked as possible (if user has selected to hide that section then doesn't even show and some users don't see at all)
+            if multiple at that level then a grid to select the active row to edit below it showing as much data as possible in each row to help user see at a glance while editing a sibling item
+            When select in grid it highlights that row very well so that user knows for sure which row they are editing (plus it will live update I bet so clear to see)
+            This gives the user as much as possible at hand immediately to view and edit and the option of adding and selecting more items
+            It also ensures a clean interface more like a piece of paper with only stuff added showing
+
+            So every level and collection is a control with 3 states:
+                None entered: it's exposed as a clean and not too intrusive "Section title" control affordance with a title so "Scheduled users +" taking up very little vertical space (this is always visible)
+                1 entered: it's exposed as a edit form below the Title control (no grid)
+                More than 1 entered: it's exposed as a grid below the title control which is used to select a row and an edit form below the grid that is displayed ONLY when a row is selected in the grid
+                    so if they just open the form and haven't picked a row yet then no edit form shows to save vertical space and be cleaner
+                
+
+        e.g. 
+        # single all the way down:
+        WOHEADER
+            singlewoitem record form with all fields showing for edit here
+                schedusers is just an add button until there is one then it's an exposed form until there's two then it's a grid only with click to open and edit each record
+
+        # two all the way down
+        WOHEADER
+            woitemgrid, click to select second item (first automatically selected when opened?), after click it shows immediately below the woitemheader fields and below that the grandchild collections as grids or add button or whole form if one
+                schedusers shows as a grid, click on it to open the form below it, not popup??
+                    Showing the form below the grid of all the other items is actually a handy affordance because you can see what was entered and refer to it in the companion same group items
+                    so if you forgot if you entered a particular user or not in the midst of entry you can see it just above
+        
+        -->
 
       <GzWoItemScheduledUsers
         v-model="value"