Skip to main content

Check In / Check Out

Check In / Check Out is SharePoint's built-in file locking feature: checking a file out locks it for exclusive editing, and checking it back in publishes your changes and creates a new version. It works on demand on any file, or can be required for an entire document library, and site owners can always release files someone forgot to check in. Because a checked-out file blocks co-authoring, the feature fits controlled, one-editor-at-a-time documents rather than everyday collaboration.
Related Features
Co-Authoring, System Columns, Version History, Versioning Settings

Common Use Cases

  • Controlled document editing: ensure only one person edits a document at a time
  • Policy and compliance documents: prevent unauthorized or accidental changes to approved content
  • Draft-heavy documents: work on content privately before making it visible to others
  • Formal review processes: keep incomplete changes hidden until ready for review
  • Legacy document management workflows: support processes built around exclusive file ownership
  • Training and procedural documentation: avoid conflicting edits on critical files

Benefits

  • Exclusive editing control: prevents simultaneous edits and content conflicts
  • Clear ownership visibility: shows who currently has a file checked out
  • Draft protection: changes are not visible until the file is checked in
  • Version history integration: each check-in creates a new version with comments
  • Configurable behavior: can be optional or required at the document library level
  • Administrative override: Site Owners can check in or discard check-outs on behalf of users
  • Audit-friendly process: supports structured change management scenarios

How It Works

  • Check out: locks the file for exclusive editing; colleagues can still open and read the last checked-in version, they just cannot edit it
  • Check in: publishes your private edits, prompts for an optional comment that lands in version history, and creates a new version
  • Discard check out: abandons everything you changed since checking out and reverts the file to the last checked-in version
  • On demand or required: check out can be used on any individual file, or made mandatory for an entire library
  • Owner override: site owners can check in, or take over, files that have no checked-in version or that someone left locked

Limits and Nuances

  • Co-authoring stops: check out and real-time co-authoring are mutually exclusive; the moment a file is checked out, collaboration on it ends
  • Wrong fit for collaboration: requiring check out on an everyday collaboration library switches off co-authoring for every Office file in it
  • Invisible uploads: in a require-checkout library, a newly uploaded file starts checked out to the uploader and stays invisible to everyone else until its first check-in; this is the familiar my-colleague-cannot-see-my-file mystery
  • Existing files stay visible: checking out does not hide a file; others still see and can read the last checked-in version
  • Discard is permanent: discarding a check out loses every change made since check-out, with no undo
  • Forgotten locks happen: files can sit locked for months when someone forgets, goes on leave, or exits the organization; a site owner can always release them
  • Non-Office files never co-author: for PDFs and CAD drawings, check out is the realistic editing control
  • Library-level setting and training: requiring check out is off by default and applies to a whole library (not per folder, file type, or site), so turn it on only after users reliably understand how to check files back in

Common Questions About Check In / Check Out

What does checking out a file in SharePoint actually do?

Checking out locks a file for exclusive editing. Colleagues can still open and read the last checked-in version, but they cannot edit it until you check the file back in. Your changes stay private while the file is checked out – when you check in, SharePoint publishes them, prompts you for an optional comment, and records a new version in version history.

Why can’t my colleagues see the file I just uploaded?

This is the familiar check-out surprise. When a library requires check out, every newly uploaded file starts checked out to the person who uploaded it – and a file with no checked-in version is invisible to everyone else. The fix is simply to check the file in. Until you do, only you and the site owners can see it.

Does check out work with co-authoring?

No – they are mutually exclusive. The moment a file is checked out, only one person can edit it, so real-time co-authoring stops. That is why requiring check out is not recommended on libraries meant for everyday collaboration. Choose co-authoring for Office documents teams edit together, and reserve check out for files that need controlled, one-at-a-time updates.

What happens if someone leaves with files still checked out?

Files do not stay locked forever. A site owner can take control of any checked-out file – checking it in on the person’s behalf or discarding the check-out entirely. This matters when someone goes on leave or exits the organization mid-edit. It is a routine governance task in the document libraries Greg Zelfond designs and builds for clients.

Should I require check out on my document library?

Usually no. Modern SharePoint favors co-authoring, and requiring check out switches that off for the whole library. It earns its place in specific cases: policy and compliance documents that demand controlled, one-editor-at-a-time changes, or libraries full of non-Office files like PDFs and CAD drawings, which cannot be co-authored anyway. Decide per library – the setting is not one-size-fits-all.

Does checking out a file create a new version?

Not by itself – the version is created when you check the file back in. Each check-in adds a new entry to version history, along with the optional comment you type, which makes check-in comments a lightweight audit trail of what changed and why. Checking a file out and then discarding the check-out leaves version history untouched.