FWIW, we use Rules for this rather than includes. For us, this has a number of added benefits.
First, we can add configuration options using rules. For forms, things like who should be emailed when the form is completed, how the form should be constructed (options for dropdowns, etc) things like that can be configured by the user adding the rule to the page.
Second, content editors don’t need to learn about includes. They already know rules and can easily reuse forms all over the site. For example, we have a contact us form that is used on several different “department” pages. The rule allows it to be configured specifically for that department, but we only have 1 rule to manage from a maintenance standpoint.
Third, we can put the forms in HTML pages which are more easily indexed by the search engine and it allows us to place the form after some introductory HTML or otherwise embed them into the page.
Last, instead of stuffing the view, logic, etc all into an include
.cfm file we can put the logic into the rule’s CFC, the view HTML into the view webskins and keep that separated somewhat. Sure, with an include you could create your own CFCs for logic, but this saves that step since the rule requires a CFC to be created anyway.
Includes are great when necessary but we almost never use them and find rules to be a better option in almost every case.