Hello Doireann,
I had a look, and think you are referring to the fact that the latest Comparison you had in the review in question has the "Complete" buttons disabled (in the "view(stats)" dialog). This isn't a problem and in fact, it is expected.

Comparisons are created as "snapshots" meaning that their "stats" are frozen in time, so to provide an audit record of disagreements as required. The side effect is that the "complete" (all agreements) button refers to the situation as it was when the comparison was created. As such, it is potentially dangerous: if the situation has changed (i.e. one reviewer revisited some reference and changed some decisions), it could lead to erroneously "completing" some disagreements that did not exist when the comparison was created.
To avoid this risk, we've added a safety check: the system automatically disables the "Complete" button whenever it detects that something has changed since the comparison was created. We believe this isn't a problem, as in such cases, it's easy enough to create a new ("fresh") comparison.

In your case, however, nothing needs to be done. It appears that the button in question is disabled because it has been used already (and/or because the agreed codings have been completed via other routes). I can say this with confidence because of what can be seen in the "Review Statistics" tab (main screen, lower right corner): in there, nothing is listed in the "Incomplete coding" section, meaning that all the decisions made re "1st Screen on Title & Abstract" are completed (2026 items, to be precise).
If I understood your concern correctly, it means that all is well and that you can proceed to the next phase (presumably full-text retrieval and screening on full-text).

It's possible that I've misunderstood your question, if so, I apologise. Please do come back to us with more details and we'll be happy to rectify.

Best wishes,
Sergio