How does validation treat documents that are being reviewed when the validation starts, but their coding has not been saved yet?

During the validation process, documents that are in review but for which coding has not yet been saved are treated as unreviewed documents. This is because the validation system recognizes that while a reviewer may be working on a document, any changes or coding that are made during that review session will only be acknowledged once they have been saved. Until the coding is saved, the system cannot classify the documents as coded; thus, they remain in an unreviewed state. This distinction is essential to ensure that the validation process accurately reflects the true status of the documents, allowing for proper tracking and management of the review workflow. The validation outcome relies on saved changes to define the documents' status adequately, maintaining the integrity and accuracy of data management during the review process.