SRP acknowledges the document's thorough explanation of the components of a Proposal. To enhance practicality, SRP recommends including an example or template of a typical Proposal document. This may be a valuable reference for Task Forces.

The list of items the Proposal includes is indicating that all are needed for a complete Proposal. If this is the case I wonder if the alternative updates considered could be “if applicable” so that we don’t create alternative updates for the sake of checking the box that we have included all the items in the list for the Proposal.

The list also includes a proposed implementation timeline, which is fine from a Proposal completeness perspective, but APS would be concerned with the implementation timeline of multiple Proposals being sequential resulting in Participants always preparing for the next change. Something that has worked well in similar environments, is to have a standard release schedule for changes – Potentially something like in the shoulder months before each Binding Season could make sense in the WRAP context for standard enhancement release timeframes Participants could follow and be prepared for.

In terms of sequence, it may be beneficial to switch the order of 3.2.2 and 3.2.3. That way it reads the Proposal is ready for comment followed by the comment format, as written it could be taken that the comment format is for a different comment period than the one that occurs after the Proposal is ready for comment. Alternatively, 3.2.2 could move down to section 4.