A practical workflow for reviewing learner work in Word, PDF and Excel

To make document-based assessment easier to review without losing oversight, agree a consistent sequence: confirm the submission and its version, check evidence against the criteria, record queries, review any proposed document changes, then complete your usual marking and quality checks before releasing results. A simple workflow makes responsibilities clearer; it does not replace your awarding organisation’s rules or your centre’s approval process.

The example below uses a fictional spreadsheet-based training task. Adapt it to the qualification specification, assessment conditions and internal procedures that apply to your learners. JCQ’s vocational and technical qualifications instructions cover matters including marking, authentication, internal standardisation and moderation; the relevant awarding body’s subject-specific rules take precedence where they differ. Read the JCQ instructions for VTQ non-examination assessments.

1. Confirm the right task and submission

Before opening the work for marking, check that you have the correct learner, task, assessment series and submission. For a spreadsheet, confirm that you have received the expected file and that it opens. For Word or PDF, check the document is readable and includes the expected sections or supporting evidence.

• Check the file name and submission details against your normal records.
• Confirm the applicable task brief and criteria, including any version or series requirements.
• Note missing, unreadable or unexpected files and follow your usual process to resolve them.
• Keep the original submission identifiable; do not silently replace it with a working copy.

For example, a learner’s spreadsheet task might ask them to analyse a fictional monthly training budget. The reviewer first confirms that the file is the learner’s submission for the correct task and that the relevant sheets, formulas and charts are present. If a sheet is missing, record the issue and follow centre policy rather than assuming what the learner intended.

2. Read the criteria before judging the evidence

Set out the assessment criteria alongside the work, then look for evidence that addresses each one. In the spreadsheet example, a criterion might require the learner to interpret trends and justify a recommendation. A total in a cell may be relevant, but it does not by itself show that the learner has interpreted the data or explained their reasoning.

Record the connection between evidence and criteria in a way another reviewer can follow: for instance, “Sheet 2, rows 8–12: comparison of monthly costs; explanation of the change is not evident.” Keep comments specific and distinguish between an observation, a question for clarification and a marking decision.

Where the evidence is unclear, note the exact issue and use the permitted route for a query. Do not provide assistance that the assessment rules prohibit, or turn a clarification into coaching on how to meet the criterion. JCQ guidance says centres should refer to the relevant specification when deciding what help is permitted. Check the applicable assessment instructions.

3. Record queries and proposed changes

Document questions while reviewing, rather than relying on memory or scattered email threads. A useful query record states what needs checking, who is responsible, what evidence is needed and whether the issue affects the marking decision.

If someone proposes a document edit or an imported change, inspect it before accepting it. Check what changed, whether the change is supported by the original evidence and whether applying it would alter the learner’s submitted work or the assessor’s record. Keep your team’s existing rules for correction, redrafting, approval and result release in force.

4. Mark, then apply your normal quality checks

Once the evidence has been reviewed, make the assessment judgement against the approved criteria and record a rationale where your process requires it. If another assessor or internal quality assurer is responsible for sampling, standardisation or approval, keep that step. Do not treat a document comparison, automated suggestion or tidy-looking output as a substitute for professional judgement.

Before work is returned, check that the marked document corresponds to the correct learner and submission, that comments and marks are in the intended locations, and that any changes or continuation pages are understandable. Retain and authenticate work in line with your qualification requirements and centre procedures.

Where EduMark Flow may fit

EduMark Flow is in beta. It connects Word, PDF and Excel assessments with online learning, reviewed document changes, marking and quality assurance. EduMark describes a workflow in which a team can bring in an original document, review questions and evidence, compare proposed file changes, and have a person review marking decisions. The available actions depend on assignment rules and document support; during beta, generated files need human review. It is not a reason to remove your existing approval steps.

For example, a team could use its agreed criteria to review a learner’s spreadsheet, record a discrepancy for follow-up, inspect proposed document changes and then proceed through its normal marking and QA route. Before relying on any returned document, check the source and output—including tables, formulas, charts, images and any continuation pages—as layouts can vary.

The practical test is simple: can a colleague see which version was reviewed, what evidence supports the judgement, what questions were raised and who completed each approval? If not, improve the hand-offs and records before trying to speed up the process.

Product details are based on EduMark’s public platform information checked on 17 October 2026. Follow your awarding organisation’s current instructions and your centre’s procedures.