Clara finishes the last answer with four minutes remaining. The work is complete. She has checked the calculation, added the missing explanation and corrected a label. She exports a file, selects it in the submission window and watches a progress indicator reach the end.
She closes the laptop.
Later, the examination record does not contain the completed answer she thought she had handed in. Perhaps the upload remained a draft. Perhaps a final confirmation was required. Perhaps she selected an older file. Perhaps the connection failed before the platform recorded completion. Those possibilities look similar from the student’s chair, but they require different prevention and recovery.
Finishing an online exam answer and submitting it are different achievements. The first produces the work. The second places the correct, readable version into the correct assessment through the authorised process and reaches the completion state that the institution requires.
This guide examines that final handoff. It does not replace general digital preparation, institution-specific instructions or technical support. An unsubmitted or incorrect file does not automatically mean failure in every assessment; consequences and remedies depend on the rules. The fictional scenarios involving Clara, Aisha, Ben, Ryan, Mira, Ethan, Adrian and Jo illustrate how preventable losses can occur without claiming to describe actual students.
The useful question is not simply, “Did you press Submit?” It is, “What evidence shows that the right work reached the right destination in the required state?”
There is more than one meaning of “finished”
A student may mean that the answer is finished intellectually: nothing more needs to be added. A word processor may mean that the file has been saved locally. An upload window may mean that file transfer has completed. An assessment system may still require a separate final action.
Confusing these states creates a failure at the boundary between work and evidence. The student knows what was written, but the examiner can assess only what the authorised system received and makes available for marking.
For a file-based assessment, a useful conceptual sequence is: work completed, correct file produced, file checked, file transferred, required final submission completed, and completion confirmed. Not every platform displays each stage separately. Some combine them, while others automate particular transitions.
For an answer typed directly into a platform, the sequence may be different. There may be no separate file export, and saving may occur automatically. The important principle remains: learn the official meaning of the states rather than assuming the words on one platform mean the same thing on another.
Do not turn this model into an invented instruction to click an extra button everywhere. In an assessment that officially auto-submits at a specified point, the correct workflow may rely on that behaviour. In another, waiting for an assumed automatic submission may leave the work incomplete.
The model helps the student ask precise questions before the examination. Which stage is automatic? Which requires action? What confirms it? What happens if the connection fails between stages? The answers belong to the assessment provider, not to a generic internet checklist.
Official platform guidance makes the distinction concrete
Moodle’s assignment documentation explains that after saving a file submission, the displayed status can depend on the assignment configuration. It may be submitted for grading, or it may remain a draft requiring the student to complete the submission action. The existence of a visible uploaded file is therefore not enough to infer the final state in every Moodle assignment.
Turnitin’s Standard assignment guide distinguishes the file-review stage from the final submission stage in its Classic workflow and tells students to wait for the completion notice. Its guidance also describes how to check the assignment when the expected receipt does not appear.
These examples concern particular assignment workflows. They are useful for understanding submission states, but they are not proof that every timed exam uses those products or the same buttons. A university may use an entirely different examination system, or configure different assessment conditions within its learning platform.
The practical lesson is to identify the exact workflow in the official demonstration or instructions. Write down the completion state that matters. “I will see the file listed” may be insufficient if the instructions also require a declaration or final confirmation.
Equally, a generic warning about missing buttons should not cause unnecessary clicking after an already completed submission. Confirm the state through the recognised route. Do not perform extra actions merely to reduce unease when those actions could replace, reopen or alter the submitted work.
The aim is an accurate understanding of completion, not a ritual of pressing every button that sounds reassuring.
Check the destination before checking the document
The right file in the wrong assessment is still the wrong handoff. Before upload, identify the course, examination, component and submission area. Similar names can make two destinations look interchangeable when they are not.
A fictional course may have a practice submission, a main examination submission and a separate supplementary-material area. A student who practised successfully can still make an error by returning to the practice link out of habit.
Use the official route rather than a search result, an old browser tab or a link forwarded informally. Check the title and relevant date or component identifier. If the institution uses candidate numbers or anonymous marking, follow its naming and identification instructions exactly.
Do not add a student’s full name to a document simply because it seems helpful. Some assessments require anonymity. Conversely, do not omit an identifier the instructions require. The correct identity convention is part of the submission specification.
Where several files or components are required, create a small pre-exam map: which work goes to which destination, in which format, and under which identifier. The map should be prepared from official instructions and used only where permitted during the assessment.
This is not administrative decoration. It prevents the student from having to solve a routing problem during the final minutes. A completed answer should not be placed at risk because the candidate must decide, under time pressure, which of several nearly identical submission areas is the real one.
Separate the writing limit from the submission deadline
Some assessments include a defined period for writing and a separate period for scanning or uploading. Others use one combined deadline. A remote examination may also have an availability window that is different from the individual time allowed after starting.
These arrangements cannot be inferred from one another. An upload allowance is not automatically permission to continue writing. A platform remaining open is not automatically an extension. An email saying that a deadline exists does not tell you whether transfer must begin or finish before that deadline.
Read the exact instructions and resolve ambiguity in advance. Record the relevant time zone where the examination is international or remote. Do not rely on a hurried mental conversion between an institution’s displayed time and the student’s local clock.
Consider a fictional exam whose writing period ends at 14:00 and whose authorised transfer window ends at 14:10. A sound plan distinguishes stopping the academic work from completing the handoff. The candidate should not treat those ten minutes as extra composition time unless the instructions expressly allow it.
For an exam with one combined deadline, the transfer must fit inside the same total allowance. Finishing the final paragraph at the last second leaves no room for a process that still requires export, review, upload or confirmation.
The useful planning object is a backward timeline from the official completion deadline. Identify the last moment to begin each required step with a realistic margin. The times should come from rehearsal and official requirements, not from a universal claim that every student needs exactly five or ten minutes.
The final file is a separate object from the document on the screen
A student may continue editing a document after exporting an earlier version. The file selected for upload can therefore differ from the open document that now looks complete. This is a version problem, not a failure of writing or understanding.
Use a simple finalisation routine. When the academic work is ready, save it through the approved method, produce the required submission format, and inspect that exported object. The inspection must concern the actual file that will be transferred, not the source document still open in another application.
Mira’s fictional folder contains an early outline, a working document and two exported versions. She recognises the right subject in every filename. That is not sufficient discrimination. The final handoff needs one unambiguous candidate file that matches the latest permitted work.
Follow the institution’s filename convention. Where no precise convention is specified, use a clear name that distinguishes the final object without adding prohibited identity information. Avoid a collection of files called final, final-new and final-really-new when one checked file would be easier to manage.
Do not delete the source or earlier authorised evidence impulsively during an incident. Retention and storage must follow the assessment rules, especially for secure material. The aim is to prevent accidental selection, not to destroy information that the institution may need to investigate a problem.
After any permitted substantive edit, assume that an earlier exported file may be stale. Produce and check the current version again before any authorised replacement. A familiar filename is not proof that the contents reflect the newest work.
Inspect the middle pages, not only the beginning and end
A quick first-page and last-page check can catch some mistakes, but it cannot establish that every page between them is present and readable. A missing middle page may contain the only working for an important question.
For a multi-page file, compare the page count with the expected sequence and inspect each page at a readable scale. Check order, orientation, clipping, blank areas, duplicated pages and whether diagrams or equations remain legible. The aim is not to proofread the entire examination again; it is to verify that the file faithfully carries the work.
In a fictional seven-page upload, pages one and seven look correct. Page four is a blurred photograph, and page five is an accidental duplicate of page three. A beginning-and-end check would miss both problems. A page-sequence check would reveal them.
Question numbering provides another route through the file. Does the examiner have a clear sequence from the question label to the associated work? Where an answer continues on another page, follow the required convention for indicating continuation.
For a typed export, inspect symbols and layout that may change during conversion: fractions, subscripts, tables, images and page breaks. A document can look correct in the editing application while rendering differently in the exported format.
This verification should be rehearsed before exam day so that it becomes proportionate and quick. The student is checking transport integrity: did the actual answer survive conversion into the submitted object? Academic correctness is a separate question.
Handwritten uploads need an assembly plan
A handwritten online examination creates a production sequence after the thinking and writing: organise pages, capture them using an authorised method, combine them where required, inspect the result and submit. Every additional step takes time and can introduce an error.
Prepare the physical routine beforehand. Use permitted paper, numbering and identification conventions. Keep completed pages in a consistent order. Where a phone, scanner or other device is allowed for transfer, practise the exact authorised workflow rather than assuming ordinary photography experience will be enough.
Lighting, focus and camera position should make the writing readable. A dark edge or shadow may obscure a minus sign, index or diagram label. The question is not whether the photograph looks attractive. It is whether the examiner can reliably read the evidence of the student’s work.
Do not depend on an unfamiliar online file converter during a secure examination. Uploading exam answers to a third-party service can create privacy and rule problems. Use only the tools and storage locations permitted by the institution.
If the instructions require one combined file, practise combining the full page set. If they require separate files, keep the mapping between each file and its component explicit. Do not choose the arrangement based on what is convenient when the assessment has specified something else.
At the end of rehearsal, ask another person to inspect harmless practice material on a different screen where appropriate. The learner knows what the handwriting is supposed to say; an independent reader of practice work can reveal legibility problems that the writer overlooks. Never use this step to share protected live exam content with an unauthorised person.
File type and file size are constraints, not cosmetic details
A submission area may restrict file formats, file count or size. The required format may also differ from the format the student usually uses for homework. Confirm those constraints before producing the final object.
Changing a filename extension is not the same as converting the file. Renaming an image with a document extension does not make it a valid document in that format. Use the approved export or conversion process and inspect the result.
Where compression is necessary and permitted, preserve readability. A very small file is not useful if the equations and annotations cannot be read. A very large file is not useful if it exceeds the upload limit or takes longer than the available transfer window.
Measure the practical trade-off using sample work before the exam. Produce a file with approximately the expected page count and detail, then test whether it remains legible and can be transferred through the authorised practice route. A one-page trial may not reveal the behaviour of a long scanned script.
Do not add unnecessary formatting, decorative images or duplicate pages that increase size without carrying assessable work. At the same time, do not remove required diagrams or supporting pages merely to make an upload faster.
The institution’s format rules remain decisive. A file that opens successfully on the student’s device may still be unacceptable for the submission area. Preparation should establish both local readability and compatibility with the receiving system.
Measure the whole handoff, not just the upload bar
Students often estimate submission time by remembering how quickly one small file uploaded. The real final-mile process may include saving, exporting, checking, naming, locating, transferring, waiting for processing and completing a confirmation.
Time the entire sequence during rehearsal. Record where delay occurs. Does the student spend two minutes finding the correct version? Does scanning dominate? Does combining pages require unfamiliar steps? Is the final declaration easy to miss?
Consider a constructed rehearsal in which file production takes three minutes, inspection takes two, transfer takes one and completion checks take one. The handoff lasts seven minutes, even though the upload itself takes only one. Reserving two minutes because “uploads are quick” would not match the actual workflow.
Add a reasonable margin based on the assessment conditions, but do not treat a few rehearsals as proof of an exact safe percentile. Connection conditions, file complexity and platform demand can change. The purpose of measurement is to replace a guess with better evidence, not to guarantee that no delay can occur.
If the measured routine does not fit the allowed time, solve the problem before the examination. Simplify approved steps, practise tool use, clarify the required format or discuss access needs with the institution. Do not plan on an unofficial extension.
Time allocated to submission is not wasted academic time when submission is required for the academic work to be marked. It is part of completing the assessment through the channel the institution has chosen.
A local save is not a remote receipt
A save indicator can establish that an application has stored work in a particular place. It does not automatically establish that the assessment system has received the same version. Likewise, a cloud-sync indicator may concern storage rather than submission.
Ask what the indicator actually reports. Is it a local application state, a file-transfer state, an assignment-submission state or a final assessment-completion state? The labels may resemble one another, but their consequences differ.
In a fictional typed exam, Ben sees that his answer has been saved and assumes the assessment is complete. Yet the instructions require final submission of the attempt. His writing is preserved somewhere in the system, but the required handoff has not been completed.
In another fictional assessment, auto-submission is the official completion mechanism. A learner who tries to force a separate file workflow could create unnecessary risk. That is why the correct general advice is to verify the documented state, not insist on one universal sequence of buttons.
Use the platform’s own explanation of draft and submission states where applicable. For other systems, consult the relevant candidate instructions. A successful homework upload on a different platform is not evidence that the examination behaves identically.
The distinction is simple enough to rehearse: where is the work now, what action remains, and what evidence will show completion? Those questions are more reliable than the reassuring feeling that something has been saved.
What a receipt proves—and what it does not
A receipt can provide evidence that a submission event occurred. It may identify the assessment, file, submission identifier and recorded time. It does not automatically prove that the uploaded file is the intended version, that every page is readable or that the answer is academically correct.
Turnitin’s student guide to Standard assignments describes submission status, the ability to open the submitted work, a submission ID and a downloadable receipt containing file details and submission time. These are complementary pieces of information, not interchangeable assurances.
Where the system permits it, inspect the submitted object through the authorised view. Compare it with what was intended: correct assessment, correct component, correct file, expected pages and current version. Then retain the permitted receipt or reference in the approved way.
Do not assume that an email must arrive immediately. Turnitin’s Moodle Direct V2 guidance notes that email and Moodle-message receipts depend on an administrator setting. In that workflow, missing email alone is not sufficient evidence that the submission failed.
The reverse is also important: a message received after a first upload does not prove that a later replacement was completed. Check which event the receipt refers to. Time and file details can distinguish an old acknowledgement from the final authorised submission.
Preserve evidence without collecting prohibited material. A secure exam may restrict screenshots, local copies or retention of answers. Use the platform’s permitted receipt mechanism and the institution’s instructions rather than inventing a private archive of protected content.
Do not wait for a grade or similarity score to decide whether submission occurred
Submission, processing, feedback and grading are different stages. A completed handoff may precede a grade by a substantial interval. A blank grade field is not by itself evidence that no work was received.
Turnitin’s assignment guide distinguishes submission status from grade, feedback and similarity information. It explains that some fields depend on assessment settings and release dates. Students should use the designated submission evidence rather than wait for every column to populate.
This matters in the final minutes because waiting for the wrong indicator can consume time or trigger unnecessary resubmissions. A student may believe that no similarity result means an upload is incomplete when the official status already confirms submission.
Conversely, the existence of a report associated with an earlier file does not show that a newer intended version has replaced it. The relevant question remains the identity and state of the submitted object.
Do not interpret a similarity score as an academic mark or as a universal verdict on whether work is acceptable. That is a separate assessment and academic-integrity question. The final-mile task here is narrower: establish whether the required work has been handed in through the authorised route.
During practice, show the learner which indicators answer which questions. This reduces the temptation to treat the most visually prominent number or icon as proof of everything. Good verification asks a specific question and checks evidence that can actually answer it.
Resubmission may replace more than the file you intended to change
A student notices a wrong page and decides to upload only the corrected page. That may work in one system and erase essential parts of the submission in another. Replacement behaviour must be understood before using it.
The University of Surrey’s guidance on incorrect coursework files in SurreyLearn warns that a later submission usually overwrites the previous submission and all its files, so a replacement needs all required files. This is coursework guidance for that environment, not automatic permission to resubmit in a timed examination.
The example illustrates a wider question worth asking: does a new upload add to the existing set, replace one object, or replace the whole submission? The student should not infer the answer from the word upload.
If replacement is allowed, prepare the complete corrected set that the rules require. Inspect it before transferring. Afterward, verify the new completion state and confirm that the intended components remain present.
Do not assume a successful earlier receipt protects a later incomplete replacement. The assessment may treat the latest authorised submission as the final one. Which version counts is a rule to establish, not a reassuring assumption.
Where the interface or instructions are unclear, use the authorised support route rather than testing replacement behaviour on the live assessment. A small rehearsal using harmless sample files can reveal the workflow without placing actual marks or confidential examination material at risk.
After a deadline, a technical possibility is not permission
A platform may have a feature that allows an instructor to reopen a submission or grant an extension. That does not mean a student is entitled to use it, or that a particular late file will be accepted without consequences.
Turnitin’s guidance on incorrect submissions distinguishes workflows and describes instructor intervention after a due date, including different processes for Classic and newer Standard assignments. It also distinguishes a first late submission from a resubmission. The software’s available actions do not replace the institution’s assessment policy.
If a problem is discovered after the deadline, report it promptly through the specified process. Describe what happened factually. Identify the assessment, recorded time, file or submission reference and the nature of the discrepancy, using only information you are authorised to share.
Do not alter timestamps, invent a technical error, or describe an unverified assumption as a fact. A clear report is more useful than an elaborate story designed to sound conclusive. The institution may have logs or other evidence that the student cannot access.
Continue only with the actions the institution permits. Do not assume that sending the script to several staff members, uploading through an unrelated portal or sharing a cloud link constitutes valid submission. It may create confidentiality problems without solving the assessment problem.
The honest boundary is important: this guide can help a student prepare a clearer handoff and incident report. It cannot promise that a late correction, replacement or appeal will be accepted.
When the outcome is uncertain, reconcile before repeating
A stalled indicator can produce a difficult moment: did the platform receive the file, or not? Repeated clicking may feel active, but it can obscure which attempt is current or create unintended replacements. Doing nothing indefinitely can also waste a limited transfer window.
The appropriate response comes from the platform’s documented procedure and the institution’s support instructions. Where an authorised submission-status view exists, use it to determine whether the event completed. Where the system directs the candidate to contact a proctor or support service, follow that route.
Do not infer complete failure solely from a missing acknowledgement, and do not infer success solely because a local progress bar reached the end. The state is uncertain until the relevant evidence is available.
In a fictional rehearsal, Ethan uploads a file and the acknowledgement does not appear. The permitted assignment view shows a completed submission with the expected file and time. A new upload is unnecessary. In a different rehearsal, the view shows only a draft, so the documented remaining action must be completed.
These are illustrations, not universal troubleshooting instructions. A secure exam may restrict navigation or require the candidate to remain on the current screen while support investigates. Do not use browser refresh, a second login, another device or a new attempt unless the official process permits it.
The principle is to act on observed state rather than on the urge to repeat. A known incomplete handoff and an unknown handoff are different situations, and the recovery process should preserve that distinction.
Prepare an incident report that separates observation from interpretation
A useful report begins with what the student actually observed. “At approximately 14:06, the upload screen displayed this error” is more precise than “the system deleted my exam”. The latter may be true, but it is an interpretation that needs evidence.
Prepare the categories before exam day: assessment identifier, component, time and time zone, permitted device or platform context, action attempted, displayed message, observed submission state and support reference. Do not include unnecessary personal information or protected question content.
Where allowed, retain the official receipt, incident number or relevant permitted log. Follow the institution’s rules on screenshots and file retention. A general desire to prove a problem does not authorise copying a secure examination.
Explain what remains unresolved. Was the file absent, the version wrong, the pages unreadable, the status incomplete or the acknowledgement missing? Those descriptions help support staff identify the next check.
Do not claim that a file was submitted before a deadline merely because it was saved locally before that time. Local creation, export and remote submission are separate events. The report should distinguish them honestly.
Finally, use the designated channel and reporting deadline. A message to a friend, tutor or unrelated member of staff may not reach the people responsible for the assessment. Preparation should establish the official support route so that the student does not have to discover it while trying to preserve the remaining work.
The practice submission should use the whole expected workflow
A one-page test upload proves little about a ten-page handwritten examination if the main difficulty lies in scanning, ordering and combining pages. A short typed paragraph proves little about a submission requiring equations, diagrams or several components.
Use harmless sample material that resembles the expected output. Include a diagram, a page continuation, a table or a special symbol where those are likely. Use the intended authorised tools and the official practice area, not the real graded submission destination.
Time the complete sequence and record each delay. Then inspect the remotely submitted sample where the system permits it. Does it contain all pages? Are the symbols readable? Does the receipt identify the expected file and event? Can the learner explain the difference between saved, uploaded and submitted?
Practise a permitted correction only if the sample environment is designed for it. Determine whether replacement affects one file or the full set. Do not intentionally upload incorrect material to a live examination as a test.
A parent or teacher can help prepare the routine before the examination. During the actual assessment, assistance must follow the rules. A familiar adult should not assume that technical help, scanning help or document handling is permitted merely because it does not involve answering a question.
The rehearsal is complete when the learner can execute and explain the handoff without improvising. That is stronger evidence than saying, “I know how to upload files.” The assessment requires a specific object, destination, deadline and completion state.
A worked final-ten-minutes example
Imagine a fictional assessment with one combined deadline and a permitted file upload. Clara’s rehearsed handoff takes about seven minutes under ordinary conditions. She chooses a planned stopping point that leaves a margin rather than writing until the last possible second.
At the stopping point, she saves the current work and exports the required format. She opens the exported file, checks all pages against the expected sequence and notices that a diagram is clipped. Because the check occurs before upload, the problem is still local and correctable through the permitted workflow.
She corrects the export, inspects the changed page and verifies that the file still contains the full set. She then selects the official submission area, checks the component identifier and uploads the intended file.
The platform presents a review stage. Clara verifies the file details and completes the documented final action. The recognised submission state appears. She checks the permitted receipt information and retains it as instructed.
Now change one condition. Suppose the acknowledgement does not appear and the instructions require contacting the proctor rather than leaving the screen. The correct response is that authorised incident route, not an improvised refresh based on this example.
The scenario is not a universal seven-minute recipe. It shows why a measured handoff and a protected margin matter: they create time to detect a production error before it becomes a remote submission problem. The margin should be based on the actual workflow, allowed time and the learner’s needs.
Keep content errors separate from handoff errors in the review
After a practice assessment, review two different objects: the answer the learner produced and the answer the receiving system actually holds. They may be identical. If they are not, identify the point where the difference appeared.
A content error belongs to teaching, reasoning or expression. A production error may involve conversion, missing pages or unreadable images. A routing error places work in the wrong component. A submission-state error leaves a required final action incomplete. An evidence error leaves the learner unsure what happened because the confirmation was not checked.
These categories are a practical framework, not a formal platform taxonomy. They help avoid prescribing more subject revision when the immediate failure was a wrong file, or blaming technology when the submitted answer itself was incomplete.
Make the repair bounded. If page ordering failed, rehearse page assembly. If versions were confused, simplify the final-file routine. If the status was misunderstood, repeat the official demonstration. If the workflow exceeded the allowed time, measure and redesign the permitted sequence before the next simulation.
Then retest the repaired handoff using fresh sample material. Do not declare the process secure merely because a teacher corrected it once. The learner needs to carry the procedure independently under realistic conditions.
The wider Diagnostics & Recovery Hub supports the same principle at other points in learning: locate the mechanism before choosing the repair. Here, the mechanism lies between completed work and the evidence available to the examiner.
What institutions and adults can clarify before examination day
Students benefit from a clear completion definition. Show what a successful submission looks like, which action makes it final and how the candidate can verify the submitted object. A practice environment should make those distinctions observable rather than bury them in several unrelated documents.
Clarify the clock. State whether transfer time is included, what the submission deadline means, what time zone applies and whether any separate allowance prohibits further writing. Ambiguity at this point can affect even a well-prepared student.
Clarify the failure route. Identify the support channel, permitted evidence, actions to avoid and any reporting requirement. Students should not have to choose between preserving exam security and documenting a technical problem without guidance.
For learners with relevant access needs, discuss arrangements early enough to test the authorised workflow. A submission process that is routine for one student may involve additional barriers for another. Generic speed targets should not override approved adjustments.
Parents and tutors can support preparation by rehearsing harmless sample work, checking that instructions are understood and helping the learner identify unresolved questions. They should not become unauthorised participants in the live examination.
These are proposed clarity measures, not claims about every institution’s current practice. The shared goal is straightforward: make the final handoff predictable enough that the assessment can evaluate the learner’s work rather than an avoidable misunderstanding of the delivery channel.
The final question is about evidence
Before closing the authorised examination workflow, the learner should know what was required, which object was submitted, where it went, what completion state was reached and what permitted evidence confirms the event. Each answer should refer to something observed, not merely something intended.
That does not require compulsive checking. Once the correct object and recognised completion state have been verified through the official process, unnecessary repeated actions can create new risks. Verification should end when its defined questions have been answered.
Clara’s final success is not the dramatic moment when she finishes the hardest calculation. It is the quieter moment when the right version of that calculation is present in the right submitted file, within the required process, ready for the examiner to assess.
Online submission is the last part of examination performance, not a chore that happens after performance is over. Prepare it, rehearse it, give it time and check the evidence that it actually happened.
Continue with the right repair
Use How to Prepare for an Online Exam for broader digital readiness, the no-backtracking examination guide for irreversible question and section boundaries, and the Examinations & Assessment Hub for the wider assessment map.
Official documentation and boundaries
The workflow examples use Moodle assignment guidance, Turnitin Standard submission guidance, Turnitin’s student assignment guide, Turnitin Moodle Direct V2 guidance, Turnitin’s incorrect-paper support guidance and Surrey’s coursework replacement guidance. These illustrate specific systems and settings. None grants permission to resubmit, extend a deadline, retain secure material or use an alternative channel in another assessment.