Simplify communication of required items in draft PDF phases
I have two thoughts about simplifying how we communicate what's required. I'll put them in the comments for discussion. What other ideas do people have for making this 1-easier to read and 2-reducing overall number of required things?
-
Iteration 1: consolidate int the outcomes/activities table @fseifoddini !66615 (merged) !66555 (merged) !66617 (merged) !66620 (merged) !66621 (merged) -
Iteration 2: is there a better design solution? @jackib #9534 (closed)
Edited by Farnoosh Seifoddini