Would it be possible to consolidate the two coding input views (grid coding and one-click-coding) somehow leaving it to the user to decide which method is appropriate for each character at any given time? I provide a mockup for this below where I try to combine the two and provide a "jump list" which I much missed when coding. The idea is that the user opts for the best coding method and what should happend next at any time. This means that the behavior of the Submit, previous and skip buttons depend on how the user ended up in that particular screen. The "jump list" should also toggle between characters and OTUs accordingly. This is of course just me dreaming up an interface that would have fitted my needs but maybe something along these lines could prove useful for others as well. However, while this "power code" example is more powerful it is also a bit more cluttered and perhaps too slow and database heavy to be practical.
Example of a "power coding" mode that combines box-coding and one-click-coding