Account access
Prepare an account recovery plan before deadline week
An account recovery plan is most useful before an account stops working. Coursework access can depend on a phone, an email address and a university identity, so identify those dependencies while you have time to change an outdated detail. You do not need a complicated security document; you need a workable route back to the services you rely on.
Microsoft documents organisation-specific security information for work and school accounts, while Google explains backup codes for its supported two-step verification setup. These examples show why recovery depends on the actual provider and account policy. Follow university instructions for institutional accounts and the relevant service's guidance for personal ones.
We may earn a commission from retailer links. This guide does not claim first-hand product testing. Our editorial approach
List the essential services
Write the names of the services you would need during a deadline week: university email, learning platform, cloud files, library resources and any specialist remote access. Group services that genuinely share one sign-in, but verify that assumption. A separate research system may have its own account even when its page carries the same university logo.
Add your personal email if it acts as a recovery route for other accounts. Keep the list free of passwords and live recovery codes. Its purpose is to identify dependencies and support contacts, not to collect all your secrets into one convenient file that could be exposed or become inaccessible with the account.
Review the methods currently registered
Visit each provider's known security settings while signed in through a trusted route. Check for an old phone number, a lost device or a recovery address you can no longer open. Record which entries need attention. Do not remove a working method until a suitable replacement is added and verified under the provider's process.
For university accounts, use only the methods the institution permits. If an option shown in a general online guide is absent, that may reflect organisational policy. Ask IT for the supported arrangement rather than trying to bypass it. Make any necessary change while the current phone and account remain available.
Store recovery material appropriately
Where a service provides backup codes, read its instructions for generation, storage and replacement. Treat the codes as credentials. Keep them somewhere secure that does not depend solely on the device or account whose loss they are meant to address. Do not place them in a shared coursework folder or send them to a group chat.
Check how the provider invalidates or replaces used or regenerated codes. Keep the current set clearly distinguished from obsolete material using a secure process. Avoid testing recovery by deliberately locking yourself out of the only working account. Use the provider's documented verification steps and seek help if the available route remains unclear.
Save a reachable support route
Find the university IT contact details and any published identity-checking requirements. Keep a non-sensitive copy accessible without university sign-in, if the institution permits it. Note support hours and the route for urgent access problems. A help-page bookmark is insufficient if the page itself requires the account that has failed.
For placement or external project systems, obtain the responsible organisation's support details separately. Do not assume university IT can reset another provider's identity. Ask who should be informed if account access affects an assessment deadline, and retain the course's actual reporting procedure rather than relying on informal advice from another student.
Keep coursework continuity separate
Maintain the approved copies of your work and know where you can continue studying if one device fails. Account recovery and file backup solve related but different problems. A drive containing a document does not restore access to the submission portal, while a recovered login does not recreate an unsaved local draft.
Review the plan when you change a phone, leave a placement or lose access to an email address. Keep the update small: verify the changed dependency and its recovery route. New hardware is only relevant if it addresses a real access requirement; most preparation here consists of correcting settings and retaining trustworthy support information.
Your next steps
- Map the services needed during deadlines.
- Replace outdated methods while access still works.
- Store recovery material securely and separately.
- Keep support details reachable without the affected account.
Sources and further help
Sources were consulted on 5 September 2026. Provider terms and services can change; check your exact booking, product or university service.
Keep planning
- Prepare coursework printing before deadline day
- Change phones without losing access to university accounts
- Prepare university cloud files before your account closes
- Plan a large coursework upload before the deadline