How Do You Back Up HSC Assessments and Major Works?

Your assessment is finished. You close your laptop, then reopen the document the next morning to discover that two pages have disappeared. The cloud says everything is synced. Does that mean your work is safe?

Not necessarily. Cloud syncing can copy mistakes just as efficiently as it copies good work.

To back up HSC assessments and major works properly, save dated versions of your editable files, keep independent copies in different locations, including one offline, export the required submission files, and regularly test whether you can restore everything.

The aim isn’t simply to have more copies. It’s to know exactly which version you can recover, open, and submit when something goes wrong.

01Why saving a file isn’t the same as backing it up

Imagine you’re writing a Chemistry investigation.

You have a document containing your method, results table, calculations, and conclusion. You accidentally delete the results table, save the document, and close it.

Now consider three situations:

The third setup gives you more ways to recover.

Think of cloud syncing as keeping two whiteboards showing the same information. If you erase something on one, the change can appear on the other.

A versioned backup is closer to photographing the whiteboard before making changes. You can return to the earlier state even after the original has changed.

The analogy has a limit: cloud services may also keep historical versions, and an ordinary photograph cannot restore an editable document. What matters is whether the particular system actually preserves a usable earlier copy.

Three files serve different purposes

For an assessment, distinguish between:

• Working file: The editable document, spreadsheet, presentation, video project, or design file you’re currently changing.
• Versioned backup: A preserved copy from a particular stage of development that you can return to.
• Submission export: The finished file in the format your teacher or assessment instructions require, such as a PDF, video, or other specified format.

For example, Physics_Report_v05.docx might be your editable document, while Physics_Report_v05.pdf is the exported file you intend to submit.

The PDF may look correct but won’t necessarily preserve the editable graphs or calculations. The Word document may contain everything but still produce a broken PDF.

You need to check both.

02Build a versioned backup system you can actually follow

You don’t need expensive software or a complicated filing system.

Start with one main folder for each assessment or major work.

Step 1: Give every project a home

Suppose you’re preparing a Physics investigation about pendulum motion.

Your main folder could be called Physics_Pendulum_Investigation.

Inside it, create four folders:

Keep the task notification and marking criteria somewhere easy to find within the project folder.

For a simple written assessment, this might seem slightly excessive. For a major work developed across several months, it becomes far more useful.

Step 2: Save versions that tell you what changed

A filename like final_FINAL_reallyfinal2.docx tells you remarkably little.

Use dates and version numbers instead.

For example:

2027-05-12_Pendulum_Report_v01.docx

2027-05-15_Pendulum_Report_v02.docx

2027-05-18_Pendulum_Report_v03.docx

The dates identify when each snapshot was saved. The version numbers distinguish stages of the work.

You might also add a short description, such as v03_graphs_added, provided the filename stays manageable.

Save a new version after meaningful progress, and before risky changes such as restructuring a report, replacing data, editing a video timeline, or installing new software.

Don’t keep reopening and overwriting your old snapshots. Their purpose is to preserve previous states.

Step 3: Keep independent copies, including one offline

A practical arrangement is:

1. Your main working copy on your computer.
2. A separate cloud copy with version history, where available.
3. A copy on an external drive or USB that you disconnect after copying.

The offline copy matters because it isn’t continuously synchronised with your working files.

If your cloud account becomes inaccessible, your laptop fails, or an unwanted change syncs across devices, a disconnected copy gives you another recovery option.

However, don’t assume an external drive is reliable just because it’s unplugged. Drives can fail, go missing, or contain incomplete copies.

For especially important major works, keep backups in separate physical locations where practical, and protect access to your files. Follow school restrictions on external storage and school accounts.

Step 4: Back up the entire project, not just the document

This is particularly important for assessments involving software.

Suppose you create a video with editing software. Your project file contains instructions about where clips begin, where transitions occur, and how sound should be arranged.

That project file may not contain the original video clips.

If you copy only the editing project to a USB, open it on another computer, and discover that every clip is missing, you haven’t made a complete backup.

The same problem can occur with linked graphs, spreadsheets, fonts, audio files, images, and computer-aided design resources.

Keep the required supporting files with the project. When suitable, package them using the application’s project-collection feature, or preserve the full folder structure and its relative file paths.

Then test the package on another computer or in a separate location.

Step 5: Export what will actually be submitted

Check your task instructions before choosing a format.

For example, a teacher might require a PDF rather than an editable document. A video task may require a particular file type and maximum upload size. Some tasks require multiple separate files.

These are task-specific requirements, not one universal HSC file format.

After exporting, open the export itself and inspect:

• Whether every required page, section, table, graph, and appendix is present.
• Whether mathematical symbols, chemical equations, labels, and units display correctly.
• Whether images have moved, disappeared, or become unreadable.
• Whether videos or audio play correctly, if applicable.
• Whether the filename, file format, and file size match the instructions.

Don’t rely only on the appearance of the editable file.

03Test whether you can restore your backups

A backup is only useful if you can recover the actual work.

Here’s a prediction worth testing: if you copy a project folder to a USB and see the files listed, have you proven the backup works?

No. You’ve proven the files appear to exist on the drive. You haven’t yet shown that they’re complete, readable, and usable.

A restore check goes further.

The restore-check routine

1. Choose a recent backup from your USB, external drive, or cloud version history.
2. Copy it into a separate temporary folder, leaving the original working project untouched.
3. Open the restored files.
4. Check that the document or project contains the expected material.
5. Confirm that any linked resources are present and work correctly.
6. Open or produce an export and check that its contents are intact.
7. Record the last version successfully restored.

For a video project, confirm that the editing timeline opens and the media files load. For a design project, inspect the model and its supporting assets. For a report, check the tables, figures, calculations, and appendices.

You don’t need to perform a full restore check after every small spelling correction.

A sensible routine is to make backups after substantial work sessions, test restoration at major milestones, and perform a final recovery check before an important deadline.

Put that final check into your HSC study timetable rather than leaving it for submission day.

For a long-running major work, repeat the check throughout development.

04What changes when you’re backing up a major work?

A major work can contain several kinds of material that need different protection.

Consider a Design and Technology project involving a physical prototype, digital design drawings, and a development portfolio.

You might be able to back up the digital files perfectly, but you can’t restore a damaged physical prototype simply by opening a PDF.

Think about the project in three parts.

Photographs and design files provide useful evidence of development, but they do not automatically replace the physical item required for assessment.

For HSC practical exam components, NESA’s 2027 HSC student guide explains that students must meet course-specific submission requirements and complete work under appropriate school supervision. The supervising teacher and principal must be able to certify that the submitted work is the student’s own.

That means your backup routine should also preserve genuine drafts, working records, and evidence of how the project developed.

Don’t treat digital recovery as permission to alter a major work after its official completion or hand-in deadline.

If a submitted physical project is damaged, speak to your supervising teacher immediately. NESA has specific procedures for damaged practical works; the appropriate response depends on the course and circumstances.

05An upload failure is a different problem from a lost file

You’ve prepared a complete backup, restored it successfully, and verified the final PDF.

Then the school submission portal stops responding.

Your backups have protected the work itself. They haven’t submitted it.

That’s the crucial difference.

A submission workflow must answer two separate questions:

1. Can you recover the correct work?
2. Has the required recipient actually received the correct file through an accepted submission method?

A successful backup doesn’t prove successful submission. A screenshot of an upload progress bar doesn’t necessarily prove it either.

What to do if an upload fails

First, check the task notification and your school’s submission procedure. If the portal is working, check whether the file was actually received before trying again.

If the upload appears to have failed:

• Preserve the verified submission file without further unnecessary changes.
• Check your internet connection, file type, and file size.
• Check the portal’s submission history or confirmation screen, if available.
• Retry through the approved method while time remains.
• If the problem continues, contact the designated teacher or school contact immediately and follow the published technical-failure or misadventure procedure.
• Keep relevant evidence, such as the error message, attempted submission time, and your contact with the school.

Don’t assume emailing the file automatically counts as submitting it. Use email or another channel only if the school permits or directs it.

Likewise, a computer failure doesn’t automatically entitle you to an extension.

06Which rules apply to backups and submissions?

The backup system above is practical advice, not a set of statewide NESA technical requirements.

Different authorities handle different parts of the process.

Under NESA’s ACE rules for formal assessment, schools must provide written assessment policies covering matters including late submissions and illness/misadventure. For HSC school-based assessment, the rules also address circumstances where an assessment task is not completed by its due date without an upheld illness/misadventure application.

The exact portal, file requirements, contacts, and school procedures must therefore be checked against your own task notification and assessment policy.

NESA’s HSC illness/misadventure process for HSC exams is separate from a school’s handling of an upload problem in a school-based task.

UAC’s undergraduate application process doesn’t provide an alternative submission route for school assessments.

For students preparing for the 2027 HSC, the 2027 NESA student guide is available as at 10 November 2026. Always confirm the rules and dates for your own cohort and course rather than relying on a previous year’s submission arrangements.

07Questions and solutions

These five scenarios test whether you can distinguish saving, versioning, recovery, and actual submission.

Question 1

A student finishes an English assessment on their laptop. The only copy is saved in the laptop’s Documents folder. The teacher requires a PDF.

Explain three actions the student should take to protect the assessment before submission.

Solution 1

The student should create an independent backup, preserve a versioned copy, and export and check the required PDF.

First, they should copy the working assessment to another storage location, preferably using both suitable cloud storage and a separate offline drive.

Second, they should save a dated version that won’t be overwritten by later edits. This gives them a recovery point if they accidentally remove or damage important content.

Third, they should export the document as a PDF, open that PDF, and confirm that the full assessment appears correctly.

Simply clicking Save is not enough. It protects the current state of one file, but it doesn’t guarantee recovery from corruption, deletion, or a failed device.

The exported PDF must also be checked because a correct editable document can produce an incomplete export.

Question 2

A student is preparing a Science Extension investigation.

At 6:00 pm, they save three files to an offline USB:

• Report_v06.docx
• Data_v06.csv
• Graph_v06.png

These files contain four completed trials. The graph matches the data, and the report satisfies the task requirements.

At 7:00 pm, the student adds a fifth trial. The cloud contains Report_v07.docx and Data_v07.csv, but the updated report refers to a new graph file that was never created.

The laptop then fails completely.

The student can open the cloud files on another computer, but has no suitable software to generate the missing graph before the deadline.

The assessment requires a complete report with a graph matching its data. Four trials are sufficient under the task instructions.

Which version should the student prepare for submission, and why? Explain how they should test the recovered work.

Solution 2

The student should restore and prepare v06, because it is the latest available complete, internally consistent version that satisfies the task requirements.

The v07 report includes a fifth trial, but its required updated graph doesn’t exist. Attaching Graph_v06.png without changing the report would create a mismatch between the five-trial data and the four-trial graph.

The tempting choice is v07 because it is newer. However, a newer file is not necessarily a more complete or valid submission.

The student should copy all three v06 files into a separate recovery folder, open the report, and compare its figures with Data_v06.csv.

They should confirm that the graph represents the four trials discussed in the report.

Next, they should export the recovered report in the required format and check the exported result.

Finally, they should preserve the original USB backup and create a new independent copy of the restored project.

The deciding constraint is consistency. The report, dataset, and graph must describe the same investigation.

Because four trials meet the task requirements, the complete v06 submission is preferable to an incomplete five-trial version.

Question 3

A school requires a report to be submitted through its online portal by 11:30 am. Email is not an accepted submission method unless the school specifically authorises it.

At 11:21 am, a student uploads the final PDF. The progress bar reaches 100%, but no confirmation appears.

At 11:23 am, the portal still lists an older draft as the most recently accepted submission.

The student’s internet connection returns to normal at 11:26 am.

Explain what the student should do before the deadline, what evidence they should retain, and what they should do if the portal continues to fail.

Solution 3

The student should immediately try to submit the verified final PDF through the portal again, then check whether that exact file has been accepted.

The progress bar reaching 100% is not sufficient evidence of successful submission. The portal’s accepted-submission record still identifies the older draft.

Because the connection is working again at 11:26 am, the student should use the remaining time to retry the upload, check for a confirmation, and inspect the submitted file where the portal permits.

If the final PDF is accepted, they should retain the submission confirmation and a copy of that exact PDF.

If the portal continues failing, they should promptly contact the school using its prescribed technical-failure or assessment procedure. They should retain the error information, attempted submission times, and records of their communication.

The tempting response is to send an email and assume it counts. However, the school’s stated submission rule doesn’t permit that without authorisation.

Nor should the student assume that the upload problem guarantees an extension.

The backup helps preserve the work and makes repeated attempts possible. The school’s rules determine what happens if a valid submission cannot be completed.

Question 4

A student completes a Design and Technology HSC major project involving a physical prototype, CAD drawings, and a development portfolio.

The completed project has already been handed in by the official completion deadline.

Before marking, the physical prototype is damaged while stored at school.

The student has:

• A current backup of the CAD files.
• Dated photographs showing the intact prototype before hand-in.
• A complete development portfolio.
• A verified digital copy of the final documentation.

The student suggests manufacturing a replacement after the deadline and submitting it instead. Another student claims that the photographs automatically guarantee the original project will receive full credit.

Evaluate both suggestions. Explain the appropriate next actions and the roles of the student, school, and NESA.

Solution 4

Neither suggestion is justified. The student should not independently remake the submitted project after the official completion deadline, and the photographs do not guarantee a particular mark.

The CAD files, photographs, and portfolio are valuable evidence, but they do not automatically replace the physical work that was submitted.

For an HSC practical exam component, the student must comply with the relevant completion, submission, and certification requirements. Producing a replacement after the deadline without appropriate authorisation could conflict with those requirements.

The student should notify their supervising teacher immediately and provide the available evidence of the project’s earlier condition and development.

The school should then follow NESA’s applicable damaged-project procedures. For Design and Technology, NESA’s published practical-exam guidance requires the school to notify the relevant NESA support team when a project is damaged before submission; the precise procedure depends on when and how damage occurs.

In this scenario, the work was already handed in, so the school should establish the circumstances and obtain the correct NESA instructions rather than assuming that a before-submission procedure automatically applies.

Whether the work remains markable, and what action is permitted, must be determined through the relevant process.

The misleading assumption in the first suggestion is that a digital backup gives the student permission to replace assessed physical work whenever necessary.

The misleading assumption in the second is that evidence of an intact project is equivalent to a guaranteed assessment outcome.

The useful role of the backups is to preserve authentic development evidence and help the school explain what existed before the damage.

Question 5

A school assessment is due at 3:00 pm.

The submission rules state that:

• Only a single PDF uploaded through the school portal counts as a submission.
• Students may upload replacement files before the deadline.
• Each successfully accepted replacement becomes the active submission, replacing the previously accepted file.
• The portal allows students to download the currently accepted file to verify its contents.

The assessment requires a data table, a labelled graph, and a written conclusion.

A student has the following files and submission history.

The student still has the complete v08.pdf, both successful-upload confirmations, and the offline backup. There is no automatic extension or authorised alternative submission channel in the stated rules.

Answer all parts:

(a) Which version is the active submission at the deadline? Explain why the two earlier confirmations and the progress bar don’t change your conclusion.

(b) Has the student’s backup system failed? Has the submission process failed to deliver the intended complete assessment? Distinguish these two questions.

(c) What should the student do after discovering the problem at 3:01 pm?

(d) Identify two different checks which, together, could have prevented this situation. Explain why neither check alone is sufficient.

Solution 5

(a) v09.pdf is the active submission at the deadline.

The school accepts the most recent successfully received replacement file.

v08.pdf was successfully submitted at 2:47 pm, but v09.pdf replaced it at 2:56 pm.

The later attempt to resubmit v08.pdf has no confirmed acceptance. The progress bar reaching 100% does not establish that the replacement reached the school’s system successfully.

At 3:01 pm, the portal identifies v09.pdf as the active submission, and the downloaded file confirms its contents.

The earlier receipt for v08.pdf proves that it was previously accepted. It does not prove that it remained the active submission after v09.pdf replaced it.

This is the central trap: evidence that a file was successfully submitted at one time isn’t necessarily evidence that it remains the file currently submitted.

(b) The backup system has preserved the complete assessment, but it has not ensured that the complete version is the active submission.

The offline copy of v08.pdf is intact and has already been verified.

That means the student can recover a complete, accurate version of the assessment despite the faulty later export.

The content-recovery system has worked for v08.

However, the active submitted file is v09.pdf, which is missing required material.

The student has therefore failed to ensure that the intended complete assessment is the version accepted at the deadline.

These outcomes are not contradictory.

A student can have excellent backups and still submit the wrong file. Equally, a student can successfully submit a file and later lose every editable version.

Backup integrity and submission integrity must be checked separately.

(c) The student should preserve the evidence and immediately follow the school’s procedure for reporting the submission problem.

At 3:01 pm, the deadline has passed.

The student should retain:

• The complete v08.pdf and its offline backup.
• Both successful-submission confirmations.
• Evidence of the unconfirmed final upload attempt.
• The downloaded active v09.pdf.
• Relevant evidence showing when the missing graph was discovered and when the school was contacted.

They should promptly inform the designated teacher or school contact, explain the situation accurately, and follow any applicable school process.

They should not edit or fabricate evidence, assume the older successful upload has become active again, or claim that an unconfirmed upload was accepted.

Whether the school permits any further action depends on the applicable rules and its consideration of the circumstances.

The evidence may help establish what happened, but it doesn’t automatically establish entitlement to a changed submission or mark.

(d) The two necessary checks are a file-content check and a submission-state check.

The first check is to open and inspect each new submission export before uploading it.

Had the student opened v09.pdf at 2:54 pm, they would have discovered the missing graph before replacing the complete v08.pdf.

They could then have retained the accepted v08.pdf while investigating the export problem.

The second check is to verify which exact file the portal has accepted after uploading.

An upload confirmation establishes that a submission was received, but it doesn’t establish that the file contains the intended work unless the uploaded contents are checked.

In this scenario, the portal allows students to download the active submission. That provides a direct way to compare the accepted file with the intended PDF.

Neither check alone provides full protection.

Checking the PDF before uploading proves its contents are correct at that moment, but not that the correct file was successfully received.

Checking the portal after uploading identifies the active submission, but a successfully received file can still be incomplete.

The student needed both checks because the two systems can fail independently.

The deeper principle is that the newest version, the best version, and the accepted version are three different things. They coincide only when you deliberately verify them.

Once you have a reliable backup routine, the next useful habit is to treat each submission as a frozen release: preserve the exact exported file, its verified source version, and any available submission confirmation together. That gives you a clear record of what you made, what you could recover, and what was actually handed in.