Control reports are important to many of our processes. Most of all, they provide snapshots of previous queries, allowing an easy build for a similar query or troubleshooting when your query isn't pulling what you expected.

I used control reports extensively so we can see what criteria were used and how queries were merged. This has saved us a lot of time and effort when trying to track why someone was or was not included in a mailing or email. It has also helped when trying to figure out how we handled things in the previous year.

Control Reports have been so helpful for me. They saved them as part of a projects documentation so I can always go back and explain what choices were made at that particular time. It has saved me numerous times when I've been asked question weeks or months after the initial work. Additionally, they are useful if another person needs to suddenly step into a project for some reason.

Control reports are necessary as they allow for detailed reconciliation and data accuracy. We need to be able to carry over the capabilities in Database view that allow us to identify any discrepancies in data over time and the possible causes behind it.

We will need a way to extract the filters somehow if we don't have control reports in NXT.

When we need to query on a large number of options from a drop down, we need to be able to pull out into a spreadsheet which options are selected in the query for offline comparison.

While some "average" users may not use this feature often, this is one of those features that power users, DBA and DBM users on teams- those who are using the database to its full extent- need in order to carry out their work effectively, track changes, and pinpoint where an issue came from.

It is also more difficult in webview query to easily grab all of the fields used in one of criteria fields or in summary fields than it is in database view query. With the "one of" fields, if they're table fields, you have to go several clicks into set up until you can see all of the appeals or funds (for example) that you selected, so it's not really a good replacement for a control report. Having the control report would mean it would be much quicker to check what your query currently has selected so you can make adjustments faster and with better knowledge. I have several queries I use for once a year purposes and I like to audit what they're pulling before I use them again to make sure they're doing what we intend in the current year, so a way to quickly get the criteria information is very valuable. And that's apart from the win of having this data for historic purposes for specific reports/mailings/etc.

Agree, this is critical to some of our processes, and will allow us to track down problems or errors where they exist. This is one small avenue to getting metadata about our database that doesn't otherwise exist in RE.
It's also important as this tool opens up to move users (i.e. those that wouldn't go into RE7 and are seeing Query for the first time). Query is ostensibly easy to use, but if you don't understand the logic behind how it works it's trivially easy to pull incorrect data. Having a control report would allow more experienced users to identify the root cause and both fix the problem, and educate other users on best practices.

On Town Hall - and agree fully that some form of report to illustrate criteria at a point in time! Need to keep track of how the criteria looked at certain time - because questions often arise weeks/months later.