SharePoint checkout: why saving a file doesn't release your changes

Saving a checked-out SharePoint document keeps your work; Check in releases that work to the library. If a colleague still sees the old text after you saved, return to the document library and look for the checkout indicator. The checkout may still be yours.

The next step depends on where your changes are and whether you want to keep them. Check in to release saved changes. Discard check out to keep the last checked-in content instead. If an unwanted change has already been checked in, use Version history to consider restoring a retained earlier version.

What saving leaves unfinished

Consider an illustrative file, Dispatch-instructions.docx. Its checked-in text says the dispatch cutoff is 4 p.m. and the contact is Warehouse desk. Maya checks it out, changes the cutoff to 3 p.m., and saves twice.

Colleagues with normal access still see the checked-in 4 p.m. text, and they cannot edit the original while Maya holds the checkout. The two saves do not, by themselves, release her changes. They also do not establish that SharePoint created a separate version for each save.

Maya checks the file in with the optional comment, “Cutoff 4 p.m. to 3 p.m.; contact unchanged”. Colleagues can then see the checked-in 3 p.m. text, and editing access resumes. This example assumes a library tracking major versions only, with no content approval requirement. A library’s minor versions or approval process can affect which version readers see; that visibility question is separate from whether a file is checked out.

Point in the edit	Maya’s saved text	Last checked-in text	Another editor’s access to the original
Before checkout	Cutoff 4 p.m.	Cutoff 4 p.m.	Available with normal editing permission
Checked out, saved twice	Cutoff 3 p.m.	Cutoff 4 p.m.	Reserved by Maya’s checkout
Finished copy checked in	Cutoff 3 p.m.	Cutoff 3 p.m.	Editing resumes for authorized colleagues

Maya can now give the next editor an exact handoff: “The 3 p.m. cutoff is checked in. The Warehouse desk contact line is unchanged; you can edit that next.” This names the released content and the remaining change. “I’ve saved it” would leave the colleague guessing which copy is ready.

Check in changes you want to keep

Open the document library itself. If the file appears in a view embedded on another page, follow the library title to its full view. Select the file, open More and choose Check in. You can add a comment describing the change. If you are checking in several files together, be aware that a batch check-in uses shared settings and a shared comment; check files in separately when they need different explanations. A cutoff instruction and a contact list can both be ready, but “Cutoff moved to 3 p.m.” would be an inaccurate comment for the contact-only edit.

For work done offline or in a local copy, upload the finished file before checking it in. Checking in first does not bring changes that are still only on your computer into SharePoint. This order matters when a colleague is waiting for your latest edits: confirm that the copy you intend to share has been uploaded, then check it in.

Some libraries require checkout before editing; others allow checkout as an option. The More menu offers Check out, Check in, and Discard check out where those actions apply. In the classic experience, these commands are on the Files ribbon tab. For a new controlled edit, select Check out before opening and editing the file, save or upload the finished copy, then return to the library for Check in. Saving ends neither the checkout nor the handoff.

Discard an edit before check-in

Suppose Maya changes the cutoff from 3 p.m. to 2 p.m. by mistake but has not checked that change in. If she might need any part of her work, she should preserve a separate local copy first. She can then use More > Discard check out.

Discarding releases the checkout and leaves the last checked-in 3 p.m. content in place. It does not create a new check-in version for the mistaken edit. If the same checkout also contains a useful contact correction, that correction needs to be preserved separately before discarding. A command aimed at the mistaken cutoff acts on the checkout, including its other changes.

Discard applies to the current checkout. It cannot undo a change that someone has already checked in.

Correct a change that was checked in

If the mistaken 2 p.m. text has already been checked in, open Version history. If the earlier 3 p.m. version is still retained, use that entry’s menu, choose Restore, and confirm with OK. SharePoint makes a copy of the older content the latest version; it does not remove the older history entry.

Compare the versions before restoring. For example, the colleague may have changed Warehouse desk to Dispatch coordinator after the cutoff error. The older 3 p.m. version still contains Warehouse desk. Restoring it would recover the intended cutoff and also replace the newer contact correction. Decide whether to reapply that contact line after restoration. Version history is useful for returning to retained content, but it does not merge changes or recover work that was never uploaded, saved to SharePoint, or retained as a version. How many versions remain available depends on the library; do not assume a particular version count.

When someone else holds the checkout

Hover over the file in the library to identify who has it checked out, then coordinate with that person before changing its state. They may have saved work that colleagues cannot yet see, including changes made offline. An authorized override exists, but it should not be treated as evidence that their unfinished work is safe to discard.

A specific message gives the owner a clear choice:

Dispatch-instructions.docx is checked out to you. We need to correct the contact field, but I won’t override it while you may have local edits. Please check in your saved copy, or tell us the changes can be discarded. If you are editing offline, upload the finished copy before checking in.

To track a longer handoff, open the companion checkout history CSV in Excel or another spreadsheet. Filter it by case, then replace the example rows with the file’s real checkout owner, last checked-in content, local-work status, action, and result. The eight data rows include completed check-in, discard and restore histories and one reusable blank row. Keep editor_content distinct from last_checked_in_content, and record an actual observed version reference in your own history. The populated examples are illustrative; they were not exported from a SharePoint tenant.

For a joint editing session, Microsoft recommends leaving the document checked in so coauthors can work together. A library that requires checkout needs a different collaboration arrangement; an individual editor cannot make coauthoring work by repeatedly saving a checked-out file.

Sources and scope: Microsoft documents checkout, check-in, and discard, versioning, and restoring a previous version. Service instructions were checked on October 7, 2026. The cases are illustrative; no SharePoint tenant actions were performed.