Can You Use SharePoint as an LMS? What Works, What Breaks, and When to Move

TL;DR: You can use SharePoint as a training library, and thousands of Australian organisations sensibly do. What SharePoint and a tracker spreadsheet cannot do is prove that training is current. They record that something happened once. Regulators and auditors ask whether it is still valid today, for this person, in this role.

Key takeaways

• SharePoint stores and versions documents well. It has no native concept of an expiry date, a renewal cycle, or a competency that lapses, and Microsoft publishes no documentation describing one.
• Microsoft's own documentation states that Viva Learning metrics "aren't designed to enable evaluation, tracking, automated decision making, profiling, or monitoring", that all reports are anonymous, and that data is stored for six months. It is a discovery layer, not a compliance record.
• SharePoint Online's list view threshold is 5,000 items and Microsoft states it "can't be changed". A 500-person organisation with eight mandatory courses generates 4,000 completion records per cycle, so views begin failing in the second year of keeping history.
• Training records sit outside the Fair Work seven year employee records rule. The retention periods that do apply come from WHS regulations and are hazard specific: two years for confined spaces training, five years after the work ends for asbestos and silica.
• On a documented worked estimate, a 500-person organisation spends roughly 22 hours a month maintaining a manual training tracker. That is a real cost, but it is not the main reason teams move. The main reason is that they cannot answer an auditor's question at all.

Can you use SharePoint as an LMS?

SharePoint can serve as a training content library, an intranet for policies, and a place to store completion evidence you have gathered elsewhere. It is not a learning management system, because it has no native mechanism for enrolment, expiry, renewal, or per-person compliance status. It records documents, not currency.

That distinction is the whole argument, and it is narrower than the usual pitch. This is not a piece about why Microsoft 365 is the wrong place to run your business. Most Australian mid-market organisations live in Microsoft 365, are happy there, and should stay. Teams, SharePoint and Outlook are where work actually happens, and any learning tool that fights that loses.

It is worth naming who has written on this topic so far. The best-known guides to using SharePoint as an LMS are published by SharePoint tooling vendors and by LMS vendors, and each one reaches the conclusion its business model requires. What is missing is a specific account of where the line falls. That line is not "SharePoint is bad". It is the difference between a record of an event and a statement of current status.

A folder called "WHS Induction 2025" containing 480 signed PDFs is a record of an event. "Every one of the 62 people who operate a forklift at the Dandenong site holds a current licence and completed refresher training in the last 12 months, and here is the evidence for each" is a statement of current status. The first is a filing problem, which SharePoint solves elegantly. The second is a state machine with dates, dependencies and exceptions, which SharePoint does not model.

What do SharePoint and a training tracker spreadsheet genuinely do well?

SharePoint is a strong content and policy repository: it versions files, controls access by group, publishes pages, indexes content for search, and integrates with Teams so people find material where they already work. A tracker spreadsheet is fast, free, flexible, and understood by everyone. For a small training programme, both are the right answer.

Be specific about the strengths, because they are real and any honest comparison has to concede them.

Document versioning is genuinely good. Microsoft's default version history setting for new document libraries is 500 major versions with no expiration, and version history shows "when an item or file was changed and who changed it". If your problem is "which version of the manual handling procedure was live in March", SharePoint answers it better than most dedicated learning platforms do.

Permissions are mature. Audience targeting, group-based access and site-level controls mean you can publish a policy to one division and not another without buying anything extra.

Search works. SharePoint's enterprise search indexes the content of documents, not just their titles. For a knowledge library, that matters more than most learning features.

The spreadsheet is honest about what it is. A tracker spreadsheet with columns for name, course, completion date and expiry date is a completely reasonable first system. Every organisation starts there. The failure mode is not that it is unsophisticated. The failure mode is that it silently stops being true, and nothing in the file tells you when that happened.

There is also a cost argument in SharePoint's favour that is fair to acknowledge. If you already pay for Microsoft 365, the marginal cost of a SharePoint training site is close to zero. Any comparison that ignores that is not being straight with the reader. The right question is not "is SharePoint free" but "what does the gap cost you, and when does that exceed the licence fee". We put numbers on both further down.

Does Microsoft Viva Learning close the gap?

No, and Microsoft's documentation is unusually clear about why. Viva Learning aggregates and surfaces learning content inside Teams. Its reporting is explicitly not built for compliance monitoring: Microsoft states that "Viva Learning metrics aren't designed to enable evaluation, tracking, automated decision making, profiling, or monitoring", that "all reports are anonymous", and that data is retained for six months.

Any article about running training in Microsoft 365 that ignores Viva Learning is not credible to a Microsoft 365 buyer, so here is the honest read on it.

What Viva Learning does well is discovery. Microsoft describes it as a place where "your team can discover, share, recommend, and learn from content libraries provided by both your organization and partners without leaving Microsoft Teams". If your problem is that nobody can find your learning content, Viva Learning is a good answer.

What it does not do is act as the system of record. Three details from Microsoft's own documentation settle it:

1. Assignments come from an LMS, not from Viva. Microsoft's setup documentation instructs admins to "enable learner record synch to enable assignments and course completion records to sync from the learning management system (LMS) to Viva Learning". The architecture assumes an LMS already exists upstream.
2. Progress tracking is source-dependent and partly manual. Microsoft states that "assignments in progress are only shown when the source shares the progress information to Viva Learning. Other learning content requires the progress to be updated manually."
3. Reporting is anonymous by design. Microsoft states that Viva Learning "doesn't collect any personally identifiable information" and that reports cannot be linked to a user or device. A compliance report that cannot name a person is not a compliance report.

There is no Microsoft documentation describing recurring certifications, expiry dates, renewal reminders or assignment due dates in Viva Learning. That is not a criticism of the product. It is simply not what the product is for.

Two more things a Microsoft 365 buyer should factor in. First, the useful parts are licensed separately: Microsoft states that "creating a learning path requires a premium license for Viva Learning or Viva Suite", the same applies to academies, and Microsoft's product page lists Viva Learning at USD $4.00 per user per month and Viva Suite at USD $12.00 per user per month on an annual commitment. So the "we already own it" argument weakens once you need learning paths.

Second, plan for platform change. Viva Learning itself is not retired and carries no deprecation notice. But Microsoft has retired neighbouring modules on published timelines: Viva Topics "has been retired as of February 22, 2025", and Microsoft published that "Viva Goals will be retired on December 31, 2025". If your compliance evidence lives inside a module of a suite, module strategy becomes your compliance strategy.

What are the five things that break when you track employee training in Excel and SharePoint at scale?

Five specific mechanisms fail as volume grows: expiry has no owner, versioning cannot prove acknowledgement, evidence is not linked to the record, delegation to managers is unsafe, and reporting has to be rebuilt by hand every month. Each one is a documented limitation, not a matter of taste.

1. Expiry has no owner

Neither SharePoint nor Excel has a native concept of "this completion expires and a new one becomes due". You can build one: a calculated column, a Power Automate flow, a conditional format that turns a cell amber at 30 days. Teams do this, and it works until it quietly does not.

Microsoft documents exactly how it stops working. A cloud flow "that isn't triggered within a 90 day period might be turned off", with owners notified 30 days beforehand, and flows owned by users without premium licences are subject to this. A flow "that has a trigger or actions that fail continuously is turned off" after 14 days, as is one that is consistently throttled. And flow run history is retained for 30 days, calculated from a run's start time.

Read that last one again, because it is the sharp edge. The evidence that you sent the reminder is deleted after 30 days. If an incident happens in November and the question is whether the worker was notified in June that their ticket had lapsed, the flow history is gone.

2. Versioning cannot prove acknowledgement

SharePoint version history is a record of writes, not reads. Microsoft's documentation describes it as showing when a file "was changed and who changed it". Nothing in it records that a named person read a specific version of a policy on a specific date.

There are partial workarounds and it is worth being precise about what each one actually captures. The SharePoint Viewers feature shows who has viewed a file or page, but not which version they viewed. Request sign-off creates a "Sign-off status" column recording pending, approved or rejected, which is an approval decision by an approver, not comprehension by a learner. Microsoft 365 audit logging captures file access events, but audit retention under Audit (Standard) is 180 days for records generated on or after 17 October 2023, extending to one year for SharePoint and OneDrive under Audit (Premium) and up to 10 years only with an E5 licence plus the retention add-on. Most annual compliance cycles are longer than 180 days.

This matters more than it sounds, because Australian regulators have explicitly addressed tick-box acknowledgement. The Commonwealth Managing Psychosocial Hazards at Work Code of Practice 2024 states at section 5.5 that "it is not sufficient to simply tell a worker about the procedure and ask them to acknowledge they understand and can perform it". A read receipt on a PDF is precisely the thing that code says is not enough.

3. Evidence sits somewhere else

The completion record lives in a spreadsheet row. The certificate PDF lives in someone's email, or in a SharePoint folder, or in a photo on a supervisor's phone. The assessment result lives in Microsoft Forms. Nothing binds them together, so producing "the evidence for this person for this course" is a retrieval exercise across three systems.

The Forms layer has a specific and under-appreciated failure. Microsoft states that "if a user account has been deleted from your tenant (Microsoft Entra ID), all account-related data will be deleted 30 days after the user has been deleted", and that ownership can only be transferred within that 30 day window. If the L&D coordinator who built your induction quizzes leaves and their account is deleted, the quiz results go with it. Merely disabling the account is safe; deleting it is not.

Forms also makes attribution optional rather than guaranteed. The response setting "anyone with the link can respond" produces anonymous submissions. A quiz configured that way generates evidence that cannot be tied to a person, and nothing warns you at the point of use.

4. Delegation to managers is unsafe

The people who know whether a worker is competent are their supervisors, so the system has to let supervisors update records. In a spreadsheet, that means giving edit rights to the file, which means anyone can overwrite anything, including a date that later matters.

Excel's co-authoring model makes this worse in ways Microsoft documents plainly. Merge conflicts arise from network interruptions and "conflicting changes made by co-authors", and Microsoft's guidance states that "not all changes might be successfully merged". Unmerged changes are stashed in a local backup file for seven days on the machine that made them, which means the missing data is on someone's laptop rather than in the file. Separately, if one person opens the workbook in a version of Excel that does not support co-authoring, Microsoft notes that "if just one person does this, then everyone else will get the 'locked' error".

Per-person permissions in a SharePoint list are the more disciplined approach, but they have their own ceiling. Microsoft's published limits set unique permissions at a supported limit of 50,000 and a recommended limit of 5,000 per list or library, and note that above 100,000 items you can no longer break or re-inherit permissions on the list itself.

5. Reporting has to be rebuilt every month

This is the 5,000 item wall, and it is arithmetic rather than opinion. SharePoint Online's list view threshold is 5,000 items, and Microsoft states plainly that "for SharePoint, the List View Threshold limit can't be changed, and is in place to allow users on shared tenants to always have good performance on queries".

The list itself can hold far more: Microsoft's documentation allows up to 30 million items. What breaks is the views, sorts, filters and grouping, which is to say the reporting. Warnings appear on the List Settings page once a list exceeds 3,000 items. Views that display 12 or more people, lookup or managed metadata columns can trigger threshold errors on their own, and a training tracker is exactly the kind of list that wants a person column, a course lookup, a status choice and a manager lookup in the same view.

Do the sum for a realistic mid-market case. A 500-person organisation with eight mandatory items per person holds 4,000 live completion records. Keep a second year of history for audit purposes and you are at 8,000, past the threshold. At 250 people with the same eight items, you cross 5,000 in the third year. There is no configuration change available to you, because Microsoft has stated the limit is fixed in SharePoint Online.

What does an auditor ask for that a SharePoint folder cannot produce?

An auditor rarely asks whether training happened. They ask whether it is current, for a named list of people, in a named role, on a stated date, with the evidence attached and the exceptions explained. That is a query against a live dataset. A folder of PDFs and a spreadsheet cannot answer it without a person manually assembling the answer.

The specific asks that break a manual system:

• "Show me every worker who performs this task and their current training status." This requires the training record to be joined to the current role, which lives in your HRIS, not in the spreadsheet. Anyone who has changed roles since the last reconciliation is wrong in the tracker.
• "Show me the ones who are overdue and what you did about it." This requires an audit trail of notifications, which is the thing Power Automate deletes after 30 days.
• "Show me the version of the procedure this person was trained on." This requires the completion record to reference the content version. SharePoint versions the document, but the spreadsheet row says only "Manual Handling" and a date.
• "Show me who has left and confirm their records are retained." Manual trackers usually delete leavers to keep the numbers clean, which is the opposite of what several retention rules require.
• "Show me the same report as at the end of last financial year." A spreadsheet has one state, the current one. Reconstructing what the position was 14 months ago is generally impossible.

In regulated sectors the ask is written down. Under the strengthened Aged Care Quality Standards, the provider must "deliver funded aged care services to individuals by aged care workers who are skilled and competent in their roles", Action 2.9.6 requires that "all aged care workers regularly receive competency-based training in relation to core matters", and the Commission's guidance on key tasks states plainly: "keep training records for all workers, including contractors. This includes records that show they have completed training and the competency they need to perform their role." Note the word "contractors", who are usually the population a spreadsheet tracks worst.

The NDIS equivalent is in the NDIS (Provider Registration and Practice Standards) Rules 2018, which require that "each participant's support needs are met by workers who are competent in relation to their role, hold relevant qualifications and have relevant expertise and experience to provide person-centred support", with quality indicators covering the maintenance of a system to identify, plan, facilitate, record and evaluate worker training.

Safe Work Australia's guidance for major hazard facilities puts the general principle well: "keeping good records of training provided to workers and visitors is an essential element of an effective training system", and it specifies that records should capture what the training was about, who received it, when it was provided and who provided it. That guide is scoped to major hazard facilities, but the four-field standard travels.

What does Australian law actually require you to keep, and for how long?

Training records sit outside the Fair Work seven year rule. Fair Work requires employers to keep time and wages records for seven years, and the prescribed categories cover pay, hours, overtime, leave, superannuation, flexibility arrangements and termination. Training is not one of them. Training retention comes from WHS regulations instead, and it is hazard specific.

This is worth stating plainly, because the seven year figure gets misapplied constantly. Here is the accurate picture.

Fair Work. The Fair Work Ombudsman states that "employers have to keep time and wages records for 7 years" and that those records must be "readily accessible to a Fair Work Inspector", "legible" and "in English". They also cannot be changed "unless the change is to correct an error", nor be false or misleading. That last clause is the one that should make a spreadsheet owner uncomfortable, because a shared workbook has no reliable way to distinguish a correction from an alteration. The Fair Work Ombudsman publishes infringement notice amounts of up to $1,980 per breach for individuals and up to $9,900 per breach for corporations for record-keeping and pay slip obligations.

Work health and safety. The primary duty in section 19 of the model WHS Act (enacted in the Commonwealth as the Work Health and Safety Act 2011) requires a person conducting a business or undertaking to ensure, so far as is reasonably practicable, "the provision of any information, training, instruction or supervision that is necessary to protect all persons from risks to their health and safety". Regulation 39 of the model WHS Regulations requires that training be "suitable and adequate having regard to the nature of the work carried out by the worker", the nature of the risks and the control measures implemented, and that it be provided in a way that is "readily understandable".

An important honesty point: regulation 39 imposes no record-keeping duty of its own. Records are how you demonstrate you met the duty, not a separate obligation the regulation creates. Do not let anyone tell you regulation 39 requires a training register.

Hazard-specific retention is where the hard periods live. These are the numbers to build your retention policy around:

Regulation numbering follows the model regulations as enacted in the states, and the asbestos and silica retention periods above are as published by SafeWork NSW. Asbestos adds a location requirement that no cloud folder satisfies on its own: SafeWork NSW states that "training records must be readily accessible at the asbestos removal area".

Notice what these periods have in common. Every one of them is anchored to an event in the employment relationship, not to a calendar. "Five years after they finish the work" cannot be enforced by a retention rule on a folder, because the folder does not know when the person stopped doing the work. That information lives in your HRIS.

For context on why this is getting more attention rather than less: Safe Work Australia's Key Work Health and Safety Statistics Australia 2025 reports that 188 workers died from traumatic injuries in 2024, and 146,700 serious workers' compensation claims involving at least one week off work were recorded in 2023-24 on preliminary data. Meanwhile the ABS Work-Related Training and Adult Learning survey for 2024-25, released in April 2026, found work-related training participation fell to 19% from 23% in 2020-21, with 44% of people citing too much work or not enough time as the main barrier. Obligations are rising while participation falls, which puts the pressure squarely on the systems in between.

What does the admin actually cost, in hours per month?

On a transparent worked estimate for a 500-person organisation with eight mandatory items per person, maintaining a manual tracker takes about 22 hours a month, or roughly 260 hours a year. At the ABS average weekly ordinary time earnings figure for May 2026, that is about $14,300 a year in labour. The assumptions are set out below so you can substitute your own.

We do not publish a customer-averaged hours figure, because the honest answer is that it varies enormously with how disciplined the team already is. So this is a model, not a measurement. Every input is either a published figure or a stated assumption.

Published inputs. The ABS reports that 8% of employees changed employer or business in the year to February 2026, which gives 40 new starters a year for a 500-person organisation. Full-time adult average weekly ordinary time earnings were $2,083.70 in May 2026 (seasonally adjusted), which is $54.83 an hour across a 38 hour week, before on-costs.

Assumed inputs. These are our estimates, not measurements. Change them.

The completions figure assumes 4,000 live records refreshed on an annual cycle, so 4,000 divided by 12. If your cycle is two-yearly for some items, halve it. If you have 12 mandatory items rather than eight, scale up.

Now the part that most vendor content skips. An LMS does not take this to zero, and at this size it does not pay for itself on labour alone. Assume automation removes about three quarters of the work and you recover roughly 16 hours a month, or about $10,700 a year. A 500-user SuperPath subscription at AUD $5 per user per month is $30,000 a year. On labour alone, that is not a saving.

Two things change the calculation, and both are more honest than a payback claim.

First, what else the line item replaces. If you currently buy a compliance content subscription separately, that cost is already in your budget and is included in the SuperPath figure, along with authoring and HRIS integrations. Our guide to LMS pricing in Australia sets out how often those are billed as add-ons elsewhere.

Second, and more to the point: nobody buys an LMS to recover coordinator hours. They buy it because there is a question they currently cannot answer. The 22 hours is what the workaround costs while it is working. The reason to move is what happens when it is not.

At what headcount and course count do teams move off SharePoint and Excel?

Two thresholds matter, and only one is about headcount. The technical threshold is arithmetic: employees multiplied by mandatory items multiplied by years of history retained, compared against SharePoint's fixed 5,000 item list view threshold. The operational threshold arrives earlier, usually when a second person needs to maintain the tracker or a course starts expiring.

Work out the technical one directly:

• Records held = employees x mandatory items per person x years of history retained.
• 500 employees, 8 items, 1 year = 4,000 records. Views still work.
• 500 employees, 8 items, 2 years = 8,000 records. Views, sorts and filters start failing.
• 250 employees, 8 items, 3 years = 6,000 records. Same wall, reached later.
• 1,000 employees, 12 items, 1 year = 12,000 records. Already past it on day one.

Roughly, you have 5,000 records to spend, and you spend them faster than you expect because history counts against you and retention rules require you to keep it.

The operational thresholds tend to arrive before the technical one:

1. The first expiring course. A one-off induction is a list. Anything with a renewal cycle is a scheduling problem, and that is a different kind of software.
2. The second maintainer. One person with a system in their head can run a tracker indefinitely. Two people editing the same file need workflow, permissions and an audit trail.
3. The first delegation to line managers. The moment supervisors need to update records, file-level edit rights become untenable.
4. The first external audit, tender or client compliance questionnaire. The first time somebody outside your team specifies the format of the answer, manual assembly stops scaling.
5. The first multi-site rollout. Site-specific requirements multiply the matrix, and matrices are what lists are bad at.
6. The first contractor or volunteer cohort. These people are not in your HRIS the same way employees are, and they are precisely the population regulators ask about.

If two or more of those are true today, you are past the point where the tracker is the cheap option.

How do you migrate to an LMS without losing completion history?

Export the existing tracker as the historical record, import it as completed records with their original completion dates, then let the LMS calculate expiry forward from those dates. The mistake to avoid is treating go-live as day zero, which resets everyone's clock and creates a false compliance gap in your first audit after the move.

A sequence that works:

1. Freeze and export before you clean. Take a dated copy of the tracker exactly as it is and keep it read-only in SharePoint. That file is your evidence of what you believed on the migration date, and you may need it.
2. Reconcile against the HRIS first, not the LMS. Match every row to a current employee record. Whatever does not match is either a leaver, a name change, a contractor or an error, and each needs a decision before import. This step usually takes longer than the import.
3. Import completions with their original dates. Any LMS worth buying accepts a historical completion date rather than stamping the import date. Confirm this in the trial, because it determines whether your renewal schedule is correct on day one.
4. Set the renewal rules and check the exceptions. Run the first compliance report immediately and expect it to look worse than the spreadsheet did. That is the system finding the gaps the spreadsheet was hiding, and it is the point.
5. Attach the evidence you have, and accept that some is gone. Certificates you can find should be linked to their records. For the rest, record what you know and note the source. An honest record with a gap is more defensible than a tidy one that is untrue.
6. Keep the HRIS as the source of truth for people. Employees, roles and org structure sync in from the HRIS. Completion and compliance status write back. This is the part that fixes the reconciliation task from the cost table above, because role changes stop being a manual step.
7. Run both for one cycle, then stop. One parallel cycle proves the renewal maths. Two parallel cycles guarantee the spreadsheet becomes the shadow system again.

The important framing: migrating to an LMS is a migration of learning records, not of people data. You are not replacing your HRIS.

What should you keep in SharePoint after the move?

Keep SharePoint for everything that is a document and nothing that is a status. Policies, procedures, manuals, forms, the intranet, and the versioned source of truth for content all belong in SharePoint. Enrolment, completion, expiry, competency, evidence and reporting move to the LMS. The two are linked, not merged.

A practical split for a Microsoft 365 organisation:

Stays in SharePoint

• Policy and procedure documents, with version history as the authoritative record of what was current when
• The document library the LMS links to, so there is one copy of each procedure rather than a training copy and an operational copy
• Reference material, knowledge base articles and site or role-specific guides
• Records that are genuinely documents rather than states, such as signed contractor agreements
• The frozen pre-migration tracker export

Moves to the LMS

• Assignment and enrolment rules, including automatic assignment on hire or role change
• Completion records, with the content version they relate to
• Expiry dates, renewal cycles and the reminder chain, with a durable audit trail rather than 30 days of flow history
• Assessment results attributed to a named person
• Manager and supervisor views, so delegation does not require file edit rights
• Compliance reporting, including the ability to reproduce the position as at a past date

Stays in Teams

• The place people actually click from. If your learning platform does not surface assigned training inside Teams, adoption suffers regardless of how good the compliance engine is.

If you are choosing between platforms with this split in mind, the criteria that matter are narrower than a generic feature list: does it model expiry natively, does it write completion status back to your HRIS, can it reproduce a historical compliance position, and can a line manager use it without training. SuperPath is built around those four. Automatic assignment on hire and role change runs through workflows driven by your HRIS data, currency and completion sit in reporting, and the Australian compliance library of 15 courses, the AI Course Builder for authoring, premium HRIS integrations, local support and implementation are all included in the AUD $5 per user per month price rather than billed as add-ons.

If you are comparing that against the learning module of an HR suite you already own, which is the other common alternative to a spreadsheet, our ELMO Learning alternatives comparison covers that specific trade-off, and the best all-in-one LMS for Australian businesses guide sets out the wider field.

The conclusion is not that SharePoint failed. It is that you were using a document system to answer a status question, and there was never a version of that which worked.

About the author

Barry Heath is Head of Growth & Partnerships at SuperPath, an Australian all-inclusive learning management system for mid-to-large organisations. He spent seven years on the founding team at Go1, the Australian-founded learning content company, and works with Australian L&D, HR and compliance teams on the practical mechanics of evidencing mandatory training.

Sources

1. Microsoft. "Viva Learning reports." Microsoft Learn, 13 August 2025. https://learn.microsoft.com/en-us/viva/learning/reports
2. Microsoft. "Microsoft Viva Learning overview." Microsoft Learn, 2 May 2025. https://learn.microsoft.com/en-us/viva/learning/overview-viva-learning
3. Microsoft. "Create learning paths in Viva Learning." Microsoft Learn, 14 February 2025. https://learn.microsoft.com/en-us/viva/learning/creating-learning-paths
4. Microsoft. "Enable learner record sync." Microsoft Learn. https://learn.microsoft.com/en-us/viva/learning/sfsf-enable-learning-record-sync
5. Microsoft. "Track progress in Viva Learning." Microsoft Support. https://support.microsoft.com/en-us/topic/track-progress-in-viva-learning-27900fbb-f156-43bd-a341-49d96757055a
6. Microsoft. "Microsoft Viva Learning pricing." Microsoft. https://www.microsoft.com/en-us/microsoft-viva/learning
7. Microsoft. "Changes coming to Microsoft Viva Topics." Microsoft Learn. https://learn.microsoft.com/en-us/microsoft-365/topics/changes-coming-to-topics
8. Microsoft. "Viva Goals retirement." Microsoft Learn. https://learn.microsoft.com/en-us/viva/goals/goals-retirement
9. Microsoft. "List view threshold for large lists and libraries." Microsoft Support, 27 May 2025. https://support.microsoft.com/en-us/sharepoint/lists/data-and-lists/list-view-threshold-for-large-lists-and-libraries
10. Microsoft. "Working with the list view threshold limit for all versions of SharePoint." Microsoft Support. https://support.microsoft.com/en-us/sharepoint/data-and-lists/working-with-the-list-view-threshold-limit-for-all-versions-of-sharepoint
11. Microsoft. "SharePoint limits." Microsoft Learn. https://learn.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits
12. Microsoft. "Set default organization version limits." Microsoft Learn. https://learn.microsoft.com/en-us/sharepoint/set-default-org-version-limits
13. Microsoft. "How versioning works in lists and libraries." Microsoft Support. https://support.microsoft.com/en-us/sharepoint/lists/documents-and-library/how-versioning-works-in-lists-and-libraries
14. Microsoft. "Allow people to see who views their files or pages." Microsoft Support. https://support.microsoft.com/en-us/sharepoint/sites-pages/allow-people-to-see-who-views-their-files-or-pages
15. Microsoft. "Audit log retention policies." Microsoft Learn. https://learn.microsoft.com/en-us/purview/audit-log-retention-policies
16. Microsoft. "Limits of automated, scheduled, and instant flows." Microsoft Learn. https://learn.microsoft.com/en-us/power-automate/limits-and-config
17. Microsoft. "Microsoft Forms admin information." Microsoft Learn. https://learn.microsoft.com/en-us/microsoft-forms/admin-information
18. Microsoft. "Adjust your form or quiz settings in Microsoft Forms." Microsoft Support. https://support.microsoft.com/en-us/office/adjust-your-form-or-quiz-settings-in-microsoft-forms-f255a4ba-e03c-4e12-b880-f7e8b62e0665
19. Microsoft. "How to manage merge conflicts in Excel cloud files." Microsoft Support. https://support.microsoft.com/en-us/excel/how-to-manage-merge-conflicts-in-excel-cloud-files
20. Microsoft. "Collaborate on Excel workbooks at the same time with co-authoring." Microsoft Support. https://support.microsoft.com/en-us/excel/get-started/collaborate-on-excel-workbooks-at-the-same-time-with-co-authoring
21. Fair Work Ombudsman. "Record-keeping." Australian Government. https://www.fairwork.gov.au/pay-and-wages/paying-wages/record-keeping
22. Fair Work Ombudsman. "Infringement notices." Australian Government. https://www.fairwork.gov.au/about-us/compliance-and-enforcement/infringement-notices
23. Australian Government. "Work Health and Safety Act 2011 (Cth), section 19." Federal Register of Legislation. https://www.legislation.gov.au/C2011A00137/latest/text
24. NSW Government. "Work Health and Safety Regulation 2017 (NSW), clause 39." NSW Legislation. https://legislation.nsw.gov.au/view/whole/html/inforce/current/sl-2017-0404
25. Queensland Government. "Work Health and Safety Regulation 2011 (Qld), section 76." Queensland Legislation. https://www.legislation.qld.gov.au/view/whole/html/inforce/current/sl-2011-0240
26. Australian Government. "Managing Psychosocial Hazards at Work Code of Practice 2024, section 5.5." Federal Register of Legislation. https://www.legislation.gov.au/F2024L01380/latest/text
27. SafeWork NSW. "Working as a licensed asbestos removalist." NSW Government. https://www.safework.nsw.gov.au/licences-and-registrations/licences/class-b-asbestos-removal-licence/working-as-a-licensed-asbestos-removalist
28. SafeWork NSW. "Employer training obligations, asbestos." NSW Government. https://www.safework.nsw.gov.au/hazards-a-z/asbestos/training2/employer-training-obligations
29. SafeWork NSW. "Training in crystalline silica." NSW Government. https://www.safework.nsw.gov.au/hazards-a-z/hazardous-chemical/priority-chemicals/crystalline-silica/training-in-crystalline-silica
30. Safe Work Australia. "Guide for Major Hazard Facilities: Information, Training and Instruction for Workers and Other Persons at the Facility." https://www.safeworkaustralia.gov.au/system/files/documents/1702/information_training_instruction.doc
31. Safe Work Australia. "Key Work Health and Safety Statistics Australia 2025." October 2025. https://data.safeworkaustralia.gov.au/sites/default/files/2025-10/Key_Work_Health_and_Safety_Statistics_Australia_2025.pdf
32. Aged Care Quality and Safety Commission. "Outcome 2.9 Human resource management." Australian Government. https://www.agedcarequality.gov.au/strengthened-quality-standards/organisation/human-resource-management
33. Australian Government. "National Disability Insurance Scheme (Provider Registration and Practice Standards) Rules 2018, Schedule 1." Federal Register of Legislation. https://www.legislation.gov.au/F2018L00631/latest/text
34. Australian Bureau of Statistics. "Job mobility continues to decline into 2026." 2026. https://www.abs.gov.au/media-centre/media-releases/job-mobility-continues-decline-2026
35. Australian Bureau of Statistics. "Average Weekly Earnings, Australia, May 2026." https://www.abs.gov.au/statistics/labour/earnings-and-working-conditions/average-weekly-earnings-australia/latest-release
36. Australian Bureau of Statistics. "Work-Related Training and Adult Learning, Australia, 2024-25." Released 9 April 2026. https://www.abs.gov.au/statistics/people/education/work-related-training-and-adult-learning-australia/latest-release