A reliable digital marking workflow begins before the first mark is awarded. Clear scans, predictable page order and a short reconciliation check prevent most import problems.
The aim is not to create an archival-quality reproduction of every sheet. It is to create a complete, readable and correctly identified working copy of each student’s script.
Choose the right scanning setup
For a class set, an automatic document feeder is usually faster and more consistent than photographing pages individually. A scanning app on iPhone or iPad can still work for a small number of scripts, oversize pages or a paper that needs rescanning.
Whichever method you use, prioritise:
- even lighting and a flat page;
- readable faint pencil;
- correct orientation;
- full page edges;
- consistent page dimensions;
- one dependable output format, normally PDF.
Colour can help distinguish teacher stamps, diagrams and highlighted source material, but greyscale may be adequate for plain black-and-white scripts. Test both with the faintest real student writing rather than a clean blank paper.
Decide how scripts will be grouped
There are two sensible patterns.
One PDF per student
Separate files are easy to inspect and re-import. Use a consistent filename such as candidate-1042-smith.pdf. Avoid names alone if two students may share a surname, and avoid placing sensitive information in a filename that will be emailed or moved outside the school’s approved storage.
One combined PDF for the class
A single file reduces scanning interruptions. It works best when every script has the same number of pages or uses a reliable cover sheet or separator. If one student inserts an extra sheet, the remaining page boundaries can shift, so reconciliation is essential.
Your marking app may support both. Trial the grouping method with one small batch before scanning the entire class.
Prepare the paper stack
Five minutes of preparation can save a long repair job later.
- Put scripts in roster or candidate-number order.
- Remove staples and unfold corners.
- Check that continuation sheets are attached to the correct student.
- Place all pages in the same orientation.
- Count the expected pages for each script.
- Keep a note of known exceptions, such as an approved extra sheet.
If papers have anonymous candidate numbers, preserve that process during scanning. Do not add student names to digital filenames merely for convenience if blind marking is required.
Use settings that preserve handwriting
There is no single perfect resolution because handwriting, paper and scanning hardware vary. Choose the lowest setting that keeps small characters, mathematical notation and light pencil readable at normal marking zoom.
Run a test with:
- faint pencil;
- blue or red ballpoint;
- a graph or diagram;
- writing near the gutter;
- an answer on the reverse of a page;
- correction fluid or erased work.
Open the resulting PDF on the iPad you will actually use for marking. A scan that looks acceptable on a desktop monitor may be tiring to read repeatedly on a smaller display.
Name and store files consistently
Use one naming rule for the whole assessment. Include an assessment identifier and candidate or roster identifier when files will otherwise be ambiguous. Avoid labels such as scan1-final-new.pdf.
Keep three states separate:
- source scans: the untouched files produced by the scanner;
- working import: the copies brought into the marking app;
- returned exports: the marked PDFs produced at completion.
This separation gives you a clean source if a script must be imported again. Store each state using the school’s approved data-handling process.
Reconcile the batch before marking
Do not assume that a successful scan means a complete scan. Reconcile the digital batch against the paper stack and roster.
Check:
- number of students;
- pages per student;
- first and final page identity;
- page orientation;
- blank pages that are genuinely blank;
- duplicate feeds;
- missing reverse sides;
- legibility of the weakest scans.
Then open a student near the beginning, middle and end of the batch. In a combined file, this spot-check helps detect a boundary shift caused by one missing or extra page.
Handle exceptions instead of hiding them
If a page is unreadable, rescan it from the paper original. If a script has an extra page, record the exception explicitly. If the student identity is uncertain, keep the script unassigned until it can be checked.
Guessing is the most expensive response because scores and feedback may then be attached to the wrong student. A good marking tool should surface unassigned or incomplete material before marking begins.
Protect student data
Scanned scripts contain personal and educational data. Follow your school’s policies for device access, file storage, transfer and deletion. Avoid personal email, consumer file-sharing links and unapproved OCR services.
Ask any marking software provider clear questions:
- Is the source script processed on the device or uploaded elsewhere?
- What works without an internet connection?
- Where are imported files stored?
- How can a teacher export and delete the data?
- What happens to local work if a subscription changes?
The answers should be specific rather than hidden behind a general claim about security.
Move from scans to marking
Once the batch is verified, attach the correct assessment structure and choose a marking order. For structured papers, question-by-question marking can reduce repeated navigation between answers and the mark scheme. If handwriting on the page is central to the process, use the Apple Pencil marking guide for annotation and export checks.
Nib is built to take scanned scripts into a structured iPad workflow, where each page stays connected to its student, questions, scores and feedback. The result is still the teacher’s mark—just without the physical reshuffling and repeat data entry around it.