Handover Pro
Menu

How it works

From the first scan to a sealed record, in eight stages.

Everyone opens the same SharePoint page. Handover Pro shows each person only their part, and the top of the Overview always says what to do next.

Book a demo Start a free trial

The Overview

Always clear what happens next.

Each handover has one Overview: its stages, its dates, who is taking over and what is waiting on whom. The person handing over and the people taking over see only Interview, Document, Sign-off, Acceptance and Seal.

  • A handover date, plus a return date or the end of an overlap for people staying
  • Share and remind: Teams messages, calendar deadlines and a handover meeting with an agenda
  • A coverage score that shows how complete the record is
The Overview of a handover: Priya Shah is leaving the Atlas CRM rollout, 14 of 20 interview questions are answered and the next step is shown at the top.

Coordinator

Map

The sites, lists and folders you choose are scanned. Names, owners, dates and permissions are read; file contents are not.

  • Choose sites, libraries, lists and folders, including other sites the coordinator can open.
  • Reads names, owners, dates and permissions. File contents are not read.
  • A 20,000-item site takes a few minutes, and you can stop a scan and resume it later.
  • Anything the scan could not read is listed, so the handover is never called complete by mistake.

Coordinator

Gaps

Anything that would be lost or left exposed is listed, from files only the person has edited to sites where they are the only owner. Each gap gets a decision.

  • Files only the person has edited or can open, and files checked out to them.
  • Sharing links on items they created, and their place in SharePoint groups.
  • Sites where they are the only owner, and their site collection admin rights.
  • Each gap gets a decision: hand it to someone, keep it, retire it, or fix it outside Handover Pro.
The Gaps tab: files only Priya has edited, files checked out to her, a site where she is the only owner and sharing links, each with a decision.

Person handing over

Interview

Questions about the gaps and the work, answered by the person handing over in their own words, over as many sittings as they need.

  • Questions about real files and sites from the gaps, plus questions for the kind of handover.
  • Answered in their own words, over as many sittings as they need, before their last day.
  • They see your privacy notice first, and can say "I don't know" or "not relevant to me".
  • The coordinator can record answers for them, for example after a call.
An interview question about a specific file, answered in Priya's own words, with options to say she does not know or that it is not relevant.

Coordinator

Document

A handover document drafted from everything above. Every statement shows where it came from, or says plainly that something is missing.

  • Drafted from the map, the decisions and the answers.
  • Every statement shows where it came from, or says plainly that something is missing.
  • Sent for approval as a frozen copy whose fingerprint is recorded before anyone approves it.
The handover document: every statement cites a register item or an interview answer, and a missing fact is flagged.

Person handing over

Sign-off

The person handing over signs the approved document, or comments on it instead.

  • The person handing over signs the approved document in the app.
  • They can comment on it instead of signing, and the coordinator sees why.
  • A sign-off names the exact version signed. If the document changes, it no longer applies.

Coordinator and approver

Access plan

The access changes are planned, approved, applied and checked. Access is always added for the new owner before it is removed from anyone.

  • A plan you can read before anything changes, built from the gap decisions and the kind of handover.
  • The approver, if you name one, approves this exact version of the plan.
  • Access is added for the people taking over before it is removed from anyone, then every change is checked.
  • Until sealing, any change can be rolled back, except check-ins and discarded check-outs, which you confirm separately.
The access plan: additions for the people taking over come before removals, each change can be undone, and the plan was approved before it was applied.

People taking over

Acceptance

The people taking over read the document and accept what is handed to them.

  • Each person taking over reads the document and accepts their part.
  • If they expected to take over something that is not named, they add a comment instead.

Coordinator

Seal

A package with every record and a certificate is sealed. The handover becomes read only, and anyone can check it later.

  • A package with the document, the answers, the access changes, the sign-offs and a PDF certificate.
  • Evidence copies of files only the person knew about, within the limits you set.
  • A manifest of fingerprints, plus README and SHA256SUMS files, so anyone can check it with standard tools.
  • The handover becomes read only. Search the handover later to find an answer.
The sealed package certificate: sign-offs, acceptance, the coverage score and the fingerprint of the package manifest.

Who does what

Five roles, each with a clear part.

  • CoordinatorRuns the handover from start to finish. An owner of the site.
  • Person handing overAnswers the interview, checks the document and signs it.
  • People taking overRead the document and accept what is handed to them, or cover while someone is away.
  • ApproverOptional. Approves the access plan and the document before anything changes.
  • Site ownersSee every handover in the site and can step in if the coordinator is away.

After sealing

Cover and overlaps end on purpose, not by accident.

For people who are staying there is an optional second date: the return date for cover, or the end of the overlap for a role change, work or client.

  • On that day the handover is flagged on the Handovers page and its Overview
  • Access is taken away only when someone presses End the cover or End the overlap
  • Ending a cover puts access back as it was before it started
  • Each removal is checked first, so the new owner never loses access they rely on

Help built in

Nobody needs training to take part.

A Help panel on every page explains what it is for and what to do there, for your part only.

  • A guided tour of each page that points at its parts
  • A card for each person listing their part in order
  • Works from the keyboard and with screen readers

Install

Up and running in an afternoon.

Handover Pro is a SharePoint Framework web part. It needs no admin consent, no Azure app registration and no Microsoft Graph permissions.

What it can and cannot see

  1. Upload the package to your tenant app catalog, or to one site collection's app catalog.
  2. Add the Handover Pro web part to a page in the site you will run handovers from. It also works as a Teams tab.
  3. Press Set up this site as a site owner. It creates the hidden lists and the Handovers library.
  4. Enter your licence key in Settings, or start with a free 14-day trial key from the shop.

Make the next handover the one nobody has to chase.

See Handover Pro on a real SharePoint site in 30 minutes, or try it free for 14 days on your own.

Book a demo Start a free trial