Hi Jennifer,
short answer is "No", I'm afraid. The idea being that if you are double-coding, you want to look at all disagreements, "by definition"...
I am guessing that you already know that you can "batch" complete agreements, via the creation of comparisons.
The typical workflow would be:
1) do all double coding, create comparisons, complete agreements in bulk, assess disagreements manually.
2) if you still have items to code/screen but don't want to do them in a double(/multiple) blind exercise, put the code-set in "single-user" mode. All codes added from this point on will be automatically "completed".
However, there may be situations where one wants some items to be evaluated by one person only, while others are still being duble-coded. In this case the workflow becomes:
1) do all the coding, making sure that each reviewer sticks to the appropriate work allocations.
2) deal with all the double coding that was performed. This is done by creating one comparison per each batch of items that have been coded by more than one person (requires some discipline on the work allocation side).
3) once all items from 2) have been completed, you can batch-complete what's left on a per-reviewer basis via the review statistics tab. This is 100% safe at this point.
the drawback of this "variation" is that completing items that are expected to be coded by a single user in batch (via review statistics) may be inadvisable, if and when the same people are involved in single and double coding rounds. You may however instruct the reviewers to complete their coding as they go through their "single user" allocations (in "Document Details" this is done by clicking on the little "no entry" red icon visible at the root of the screening code-set).
Does this help?
Sergio