Save laboratory coursework before leaving the computer room

Identify where the application saves

At the start of the session, inspect the default save location and ask whether it persists after sign-out or restart. Distinguish a local temporary folder from your university storage. Do not assume that a familiar documents label means the same location on a laboratory computer and your own laptop.

Create a harmless test file in the approved destination and reopen it. If the course uses an instrument or specialist application, ask whether it generates supporting folders or metadata alongside the main file. A successful single-file save may not capture the complete project needed to continue analysis later.

Keep the session output identifiable

Use the course's naming convention or an agreed name containing enough context to distinguish the session and exercise. Record relevant settings, software version and any permitted sample identifiers in the appropriate notes. Avoid embedding sensitive personal information in file names. The result should remain interpretable after you leave the room.

Keep original outputs separate from later transformations where the module requires it. If a test failed or a reading is incomplete, label the state accurately rather than presenting it as a finished result. A clear note about what happened is more useful than a plausible file name that conceals an unfinished practical step.

Export what the next task needs

Check the assignment instructions for required native files, tables, figures and report outputs. Save the editable project as well as a permitted export where needed. If the software uses linked inputs, include them through its documented packaging or saving process. Ask before copying any shared or restricted instrument data.

Open the export while the laboratory application is still available. Inspect units, labels, file size and the expected number of records or pages. If the output is empty or incomplete, resolve it before leaving. Reopening the original software later may require another booking or staff assistance that could have been avoided by this check.

Transfer through the approved route

Use the university's authorised storage or permitted removable device. Check that the transfer has finished and that the destination contains the intended files. For cloud storage, read the sync or upload state rather than assuming a dragged file has already arrived. Keep the source available until the destination is verified.

If removable storage is permitted, use the system's appropriate ejection process and collect the device. Do not plug an unknown found drive into lab equipment to solve a missing-storage problem. If your intended method is unavailable, ask the demonstrator or IT team for the authorised alternative rather than improvising a public sharing link.

Leave a usable next step

Write a brief note of what is complete, what remains and which file is the starting point for the next session. Open a representative destination file from an authorised device or service where practical. Confirm you can access it without the local lab session. This is the final check that the work has actually travelled with you.

Sign out and leave the computer according to room instructions, taking your own accessories. Buy storage only if the course permits it and the workflow demonstrates a recurring need. The essential habit is a verified closing sequence that preserves the result and its context before the laboratory session ends.

Your next steps

• Check whether local storage persists.
• Identify all native and supporting files.
• Open the required export before leaving.
• Verify the approved destination and sign out properly.

Keep planning

• Choose a USB-C hub for moving between campus and your room
• Pack a first-night kit for your university room
• Set up a useful study desk in a tiny student room
• Build a student laundry routine without a tumble dryer