# data[].attributes.body
If someone else is filling the form (not a content person) how will Content Leads get notified to go back and make a recommendation?

# data[].attributes.body
I'm not sure what this means: "Reference/Source for Suggested Correction" - is it about support for the recommendation / rationale?

# data[].attributes.body
Could there be a dropdown for someone like CM - like TEA Internal - in the feedback source? Just thinking ahead...

# data[].attributes.body
for the conforming edit entries - is there a way to duplicate the form so the person doesn't have to retype all. the. things?

# data[].attributes.body
When submitting the form for revisions, please provide guidance on what information to include in the "reference/source for suggested correction" section for clarity and consistency across submissions.

# data[].attributes.body
for pg/pg range - consider specifying that it is the product page and not the PDF display page.

# data[].attributes.body
Love Love Love it!

# data[].attributes.body
In the form, consider editing "Unit number" to "Unit Number, Program Material or Course Material" or something similar. If that's too long, consider putting those options at the top of the drop down to avoid an "I can't answer this required question" issue.

# data[].attributes.headline
If we are moving edits from this smartsheet to a excel for ECS verification, (1) how do we track that no lines have been missed? (2) what happens if a new edit is identified during the verification process.

# data[].attributes.subject
If we are moving edits from this smartsheet to a excel for ECS verification, (1) how do we track that no lines have been missed? (2) what happens if a new edit is identified during the verification process.

# data[].attributes.headline
Wondering in when we would use "Flag for Review"... is that for when we think a conversation is needed to explain nuance of content specialist thinking before SLT reviews?

# data[].attributes.subject
Wondering in when we would use "Flag for Review"... is that for when we think a conversation is needed to explain nuance of content specialist thinking before SLT reviews?

# data[].attributes.headline
For the grade level question in the form: is there a way to add a "Program" option so that the smartsheet automatically creates individually copies for each course/grade level. This was we do not have to fill out individual forms.

# data[].attributes.subject
For the grade level question in the form: is there a way to add a "Program" option so that the smartsheet automatically creates individually copies for each course/grade level. This was we do not have to fill out individual forms.

# data[].attributes.body
Question: Will we be able to link out to word docs for complicated revisions requiring robust content team notes?

# data[].attributes.headline
Do we actually have different target release dates or are we aiming for Aug 8 like Jenn said?

# data[].attributes.subject
Do we actually have different target release dates or are we aiming for Aug 8 like Jenn said?

# data[].attributes.headline
For "Conforming Edit Location" specify (e.g. Component, page #)

# data[].attributes.subject
For "Conforming Edit Location" specify (e.g. Component, page #)

# data[].attributes.headline
For the Conformed - yes/now in the form: is there a way to automatically open a new section to fill out the conformed/impacted edit so that we don't have to fill out a brand new edit. (1) should save time (2) so the impacted edit is not "forgotten" 

# data[].attributes.subject
For the Conformed - yes/now in the form: is there a way to automatically open a new section to fill out the conformed/impacted edit so that we don't have to fill out a brand new edit. (1) should save time (2) so the impacted edit is not "forgotten" 

# data[].attributes.headline
Confused about milestones vs. tasks. Either way, the who + what/action should be included.

# data[].attributes.subject
Confused about milestones vs. tasks. Either way, the who + what/action should be included.

# data[].attributes.body
Is it possible to add a reminder to the form for users to submit additional forms for conforming changes....in bold red or something similar that will make it super clear that it is not optional?

# data[].attributes.body
The revision tracker is AMAZING!

# data[].attributes.headline
Recommend including a "Not Sure" option for conforming changes. Would hate for someone to just assume or guess on that one.

# data[].attributes.subject
Recommend including a "Not Sure" option for conforming changes. Would hate for someone to just assume or guess on that one.

# data[].attributes.headline
Could it be the case that a flag or feedback is for *all* grade levels and not just one because it's in a programmatic document? For example, if a typo is found in the Program Implementation Guide, we wouldn't want to click a certain grade level from the drop down menu.

# data[].attributes.subject
Could it be the case that a flag or feedback is for *all* grade levels and not just one because it's in a programmatic document? For example, if a typo is found in the Program Implementation Guide, we wouldn't want to click a certain grade level from the drop down menu.

# data[].attributes.headline
Right now there are alot of individual sign offs. How can we condense any TEA sign-offs?

# data[].attributes.subject
Right now there are alot of individual sign offs. How can we condense any TEA sign-offs?

# data[].attributes.headline
I am confused by the section "Publisher-Initiated edits complete". This is only 1 type of edits that we will complete, but they will be all implemented/revisied/verified at the same time. Shouldn't there be 1 larger section for all types of revisions.

# data[].attributes.subject
I am confused by the section "Publisher-Initiated edits complete". This is only 1 type of edits that we will complete, but they will be all implemented/revisied/verified at the same time. Shouldn't there be 1 larger section for all types of revisions.

# data[].attributes.body
There are some rows (for example, Row 27 and 28 in K-5 Math) that are called tasks but seem like informational rows rather than rows that are than task-oriented.

# data[].attributes.headline
Filters! Like a filter per content lead would help.

# data[].attributes.subject
Filters! Like a filter per content lead would help.

# data[].attributes.headline
Create a formula for "milestone + G# + M#". This will allow for two columns for grade and module and then a drag down to update instead of a manual update.

# data[].attributes.subject
Create a formula for "milestone + G# + M#". This will allow for two columns for grade and module and then a drag down to update instead of a manual update.

# data[].attributes.body
inconsistent grain size - some "buckets" have detailed sub tasks and others are more generic.

# data[].attributes.headline
Split ECS and TEA lines (for example, "TEA/ECS verifies edits")

# data[].attributes.subject
Split ECS and TEA lines (for example, "TEA/ECS verifies edits")

# data[].attributes.headline
Might be good to label the buckets of work in a column so that it's filterable?

# data[].attributes.subject
Might be good to label the buckets of work in a column so that it's filterable?

# data[].attributes.headline
For the milestones, getting clearer on what the goal is. "Develop..." could be rewritten to say "XYZ are developed and submitted to ___"

# data[].attributes.subject
For the milestones, getting clearer on what the goal is. "Develop..." could be rewritten to say "XYZ are developed and submitted to ___"

# data[].attributes.headline
Not sure whether the darker blue or the darker grey rows are the milestones. 

# data[].attributes.subject
Not sure whether the darker blue or the darker grey rows are the milestones. 

# data[].attributes.body
some of the entries indicate TEA or SBOE (WHO) but not all. Would be clearer if each task/milestone follows a set structure or formula.

# data[].attributes.body
not clear which are tasks and which are milestones

# data[].attributes.headline
Guidance and external linked resource in the project plan of scope and description of each step. 

# data[].attributes.subject
Guidance and external linked resource in the project plan of scope and description of each step. 

# data[].attributes.headline
Recc to breakout vendors into individual steps so specific start / end  and assigned work durations are clear. Ex: ECS step 19.A

# data[].attributes.subject
Recc to breakout vendors into individual steps so specific start / end  and assigned work durations are clear. Ex: ECS step 19.A