Skip to main content

The Standard Public Comment

Interested in submitting a comment on the Non-GMO Project Standard? The Non-GMO Project welcomes comments at any time through our Public Comment form.

Public comment form

For tips on writing effective comments, scroll down or visit the form page.

Please use our Contact Us page for matters not directly related to our official Standard Public Comment Form.

 

Guide to writing comments

Clear and constructive feedback helps improve the Standard. To ensure comments are useful and impactful, consider the following:

Select and describe the observation or suggestion
Select the purpose, type of edit, and importance of the comment by choosing the options that best categorize the feedback and following the corresponding prompts to tailor the comment:

  • Suggestion for Improvement – Recommend changes to enhance clarity, accuracy, or usability. Specify the section, explain the issue, and propose concrete improvements.
  • Proposal for New Content – Suggest adding new material or topics not currently covered. Clearly state what’s missing, why it’s important, and how it improves the Standard.
  • Identification of Errors – Report mistakes, inconsistencies, or inaccuracies. Specify the issue, provide reasoning or evidence, and suggest corrections if possible.
  • Request for Clarification – Ask for further details to better understand the content. Identify what’s unclear, explain the confusion, and suggest how clarity can be improved.
  • General Dissatisfaction – Express concerns about the content. Clearly describe the issue and its impact, and, if possible, suggest ways to address it.
  • Praise – Highlight aspects of the content that work well. Explain why they are effective and how they contribute to the Standard’s clarity or usability.
  • Regulatory/Legal Compliance Concern – Identify potential conflicts with external regulations or policies. Reference specific laws or guidelines, provide context, and explain the compliance risk.
  • Request for Exception/Exemption – Seek an exception to a specific requirement. Explain why the exception is needed, how it aligns with the Standard’s intent, and any mitigating factors.
  • Neutral Observation – Share relevant observations without suggesting changes, criticism, or praise. Provide context on why the observation is important.

  • Technical Accuracy – Propose corrections to factual errors, technical inaccuracies, or incorrect details. Clearly identify the issue and suggest accurate revisions based on evidence or expertise.
  • Grammar/Formatting – Point out grammatical, punctuation, or formatting issues and recommend improvements to enhance readability and consistency.
  • Conceptual Clarity – Suggest edits to improve the presentation of ideas or concepts, making them easier to understand. Identify areas of confusion and propose clearer wording or structure.
  • Scope or Applicability – Recommend changes to adjust the content’s relevance to its intended audience or context. Explain how to refine the focus or broaden applicability as needed.
  • Tone or Language Use – Recommend changes to improve professionalism, consistency, or inclusivity in language. Identify areas where wording may be biased, unclear, or inconsistent with the Standard’s tone.
  • Reject the Proposed Change – Explain why the proposed change should not be implemented. Provide reasoning to support the position and suggest alternatives if applicable.
  • No Edit Proposed – Indicate that the comment does not suggest a specific text change, such as praise, observations, or general feedback. Use this when offering feedback without recommending edits.

Critical, High, Medium or Low?

Specify the concept or section
Specify the concept the comment relates to. Some concepts are best illustrated by one or more parts of the Standard, so if applicable, mention the relevant sections or specific sentences. Identifying all relevant areas helps provide full context.

Explain the importance
Provide a brief explanation of why the comment matters. Will it improve clarity, accuracy, or usability? A short explanation strengthens the impact of the feedback.

Propose a solution (highly encouraged)
If possible, include a suggestion for improvement. While not required, offering a proposed revision can be especially helpful.

Resources

Join our newsletter!

Catch The Butterfly.

Join our newsletter!

Catch The Butterfly.

Join our newsletter!

Catch The Butterfly.

Join our newsletter!

Catch The Butterfly.

Join our newsletter!

Catch The Butterfly.

Join our newsletter!

Catch The Butterfly.

Join our newsletter!

Catch The Butterfly.

Join our newsletter!

Catch The Butterfly.

Sign Up