I woudl not want batch to function this way at all. you can open the constituent from the menu bar and once you have committed the batch you can creat a query and get all the query functions you want.

My issue is that I want to be able to quickly scan through the consituent records before the batch is committed.

It's a few extra clicks, and when you're going through 25 at a time (times 50+ batches a day), every click matters.

Why are you opening so many constituents? The constituent window in batch typically gives all of the necessary information for entering gifts and checking batches. What are you going in and checking on all of these gifts?

I'm not checking on the gifts going in (obviously, it's right in front of me) but I like to double-check summer interns who are sometimes adding 10-20 new consituents per batch. I want to check titles, spouse info, email capture, etc.

Our work is cyclical (we are a Catholic diocese) so for three months out of the year we are processing all of our 33,000 gifts.

I'll be at BBCon if you want to chat!

Is it possible that you let them go in and then dun audit queries based on the batch number immediately after processing. I do not think that this will get a good enough number of votes to make it to a final release (but I could be wrong). Just trying to help in the meantime.

dun = run