How do I configure Supporter Comments for Regulations.gov?

Follow the steps below to set up the comment content supporters will submit through your Advocacy form. These steps take place inside the form after you've connected it to a Regulations.gov document.

Step 1: Add comment text

When drafting your comment text, keep these limits in mind:

• Comment: Up to 4,000 characters

  • Special characters (such as emojis) are not supported

• Signature: Optional, and added to the bottom of the comment if included

Fields like Subject and Target Greeting (used in other advocacy forms) aren't available here because comments are submitted to documents rather than individuals.

Step 2: Decide whether supporters can customize the comment

You can select Allow supporters to customize this comment.

This option is commonly used to let supporters personalize their message. Note that agencies may choose not to display comments that look identical, though all comments are still counted.

Step 3: Understand required supporter information

Regulations.gov requires a first and last name for public comments. Unless a signature is included, Regulations.gov only receives the supporter's name. Any other contact information collected on the form stays in EveryAction and is used to create or update the supporter's contact record.

Step 4: Review confirmation messaging

Selecting Regulations.gov as your delivery channel automatically updates your form's confirmation messaging with default text, which you can edit if needed:

Thank You message (default):

• Headline: "Your comment has been submitted"
• Body: "Thank you for making your voice heard on this important issue. Your comment has been submitted and will be reviewed by rulemakers and posted as a public comment on Regulations.gov."

Confirmation email (default):

• Subject: "Thank you for submitting your comment"
• Body: "Dear {{FirstName or 'friend'}}, Your comment has been submitted. It will be reviewed by rulemakers, who will respond when making their final decision. It may also be posted publicly. Thank you for taking this important action to shape public policy."

Deactivation message (default):

• "Sorry, the comment period for this document has ended."

Step 5: Set a deactivation date

Set the form's deactivation date (the date your form stops accepting submissions) at least 1–2 days before the comment close date. Regulations.gov's API limits how many comments can be submitted per hour, so comments may queue and take hours or even days to fully deliver during high-demand periods—building in this buffer helps ensure all comments are submitted before the comment period closes.

If your form remains active after the comment period ends, submissions will still go through and supporters won't see an error—but the agency won't accept those comments unless it's choosing to accept late comments for that document. If an agency is accepting late submissions, comments will continue to be submitted via the API for as long as they're being accepted.

Not quite what you were searching for?

• Navigate back to the Advocacy Resource Index.

How do I configure supporter comments for Regulations.gov in EveryAction? | What character limit applies to Regulations.gov comments in EveryAction? | Can supporters edit their comment before submitting on Regulations.gov? | What information does Regulations.gov require for public comments? | How do I allow supporters to customize their advocacy comment? | How do I set a deactivation date for a Regulations.gov advocacy form? | What happens to confirmation messages when I select Regulations.gov as the delivery channel?