Forum Update: Supporting Community-Led Discussion
The forum was created as a space for shared learning and peer support, and as the community grows, we want to lean more fully into that purpose.
Going forward, PAAB will be taking a more listening-first role in forum discussions. Rather than responding immediately to every question, we’ll be encouraging members to engage with one another, share experiences, and help build collective understanding. PAAB will continue to monitor conversations and will step in to:
- Correct any misunderstandings
- Provide guidance when questions remain unanswered after a few days
- Support discussions where official clarification is needed
Our goal is to foster a collaborative, trusted community where knowledge is shared and strengthened by everyone’s contributions.
Thank you for being part of the conversation.
Shading for renewal of a series/iterative submission
-
Hi, if we are renewing an iterative submission, would the yellow shading for previously approved copy or the blue shading for iteration be preferred?
Hello @username
Apologies for not seeing this sooner.
Thanks for your question. To clarify, iterative submissions (i.e. different iterations within the same PAAB eFile) do not require light blue shading. Blue shading is requested for child files that are part of a series. The blue shading is used to identify the common copy between the child and the parent eFile.
However, whether you’re renewing an iterative submission or a series parent or child submission, you would shade the copy yellow. Once the submission is a renewal, it is more helpful to reference the backfile to which the copy is 100% pickup rather than shading it in relation to a parent file where the copy may be as little as 60% common.
When using the “express renewal” feature, we will not require that the shading be adjusted by virtue of the way in which the “express renewal” platform functions and the nature of the guarantee that nothing has changed.
