SHAREPOINT PROJECT-SITE RESTORE ACCEPTANCE WORKSHEET
North Star | NS-C500-004 | Version 1 | Updated 2026-09-06
Companion: https://northstarit.ca/blog/sharepoint-project-site-restore-verification/

STATUS: Unexecuted procedure template. No tenant or customer recovery is claimed.
Use a disposable, approved synthetic site for rehearsals. Do not delete a live
project to test this worksheet. Store completed records in a restricted location;
reference approved evidence without copying sensitive documents or credentials.

1. AUTHORITY AND SCOPE
Incident/rehearsal reference:
Business owner / approver reference:
Authorised operator / role:
Acceptance testers / intended roles:
Approval reference and approved actions:
Site URL and recorded site identifier:
Site type: ordinary / Microsoft 365 group-connected / private channel /
           shared channel / other (requires a reviewed procedure):
Group / team / channel references, if relevant:
Deletion timestamp and time zone:
First report timestamp:
Required content date / known baseline:
Required time to resume the agreed project task:
Recovery mechanism: deleted-site restore / channel recovery / other:
Mechanism scope, exclusions and verified eligibility:
Incident response or preservation constraints and decision owner:

2. RECOVERY WINDOW AND SITE-TYPE DECISION
Current vendor guidance checked by / on:
Site recovery eligibility and deadline:
Group-resource eligibility and deadline, if applicable:
Channel eligibility, lifecycle and permission authority, if applicable:
Selected documented restoration route and approver:
Missing information / escalation owner:
Do not assume the site recovery window also covers group or channel resources.
Do not treat recycle-bin recovery, version history or retention as an independent
backup. Do not permanently delete a remaining site to free its URL during this
procedure. Resolve unclear eligibility before taking further recovery actions.

3. SYNTHETIC BASELINE (CREATE BEFORE AN APPROVED REHEARSAL)
Use invented project content and approved test accounts only.
A. Project-summary.txt
   Suggested marker: PROJECT-DEMO / REV-02 / SYNTHETIC ONLY
   Expected path / content / relevant version:
B. Estimate.csv
   Suggested content:
   item,quantity,unit_cost
   sample-a,2,10
   sample-b,3,5
   sample-c,1,20
   Expected path / metadata / relevant version:
C. Decisions list
   Suggested entries: D-01 Scope reviewed; D-02 Estimate accepted
   Expected list path, values and permissions:
D. Restricted library
   Synthetic-only document / direct link:
   Approved reader/editor roles:
   Excluded role that must receive access denial:
E. Dependencies
   Agreed cross-file link:
   Teams Files/tab route (if applicable):
   Integration / safe test mode / approved scope:
F. Identity expectations
   Project editor: may read and save in approved test area
   Reviewer: may read; edit must be denied
   Excluded account: no access to the restricted test material
   Approved exceptions or sharing links:

4. RESTORATION RECORD
Reviewed procedure reference:
Action started / time zone:
Exact selected site or channel:
Observed completion time / status / error reference:
Operator evidence location:
Unexpected behaviour / escalation reference:
No acceptance is implied by this section alone.

5. ACCEPTANCE CHECKS
For each test record: expected result; actual result; tester role; timestamp;
restricted evidence link; outcome; exception owner and due date.
Outcomes: PASS / FAIL / UNVERIFIED / NOT APPLICABLE (give reason).

T1 WORKSPACE ROUTE
Editor opens expected site, page and library. If applicable, repeat through the
actual Teams Files/tab route. A working direct URL does not prove channel recovery.
Expected:
Actual / evidence / role / time:
Outcome / exception owner / due:

T2 CONTENT AND BASELINE
Open summary and compare revision marker. Open all three estimate rows. Inspect
the two Decisions entries and agreed metadata/versions. Count alone is insufficient.
Expected:
Actual / evidence / role / time:
Outcome / exception owner / due:

T3 ALLOWED WORK AND READ-ONLY BOUNDARY
Editor saves and reopens a labelled synthetic test document in the approved area.
Reviewer opens an approved file; attempted edit is denied as intended.
Expected:
Actual / evidence / role / time:
Outcome / exception owner / due:

T4 EXCLUDED ACCOUNT
Using its own approved session, excluded account opens the restricted library and
a recorded synthetic file link. Both must behave according to the approved denial.
Expected:
Actual / evidence / role / time:
Outcome / exception owner / due:

T5 DEPENDENCIES
Follow the agreed cross-file link. Check each required tab and integration.
Use controlled automation tests only; no real messages or production mutations.
List every dependency not tested as UNVERIFIED.
Expected:
Actual / evidence / role / time:
Outcome / exception owner / due:

T6 BUSINESS TASK
Project owner checks the synthetic estimate and records a sample decision, or
performs another approved representative task using recovered material.
Expected useful result / target time:
Actual result / completion time / evidence:
Outcome / exception owner / due:

6. ACCEPTANCE AND FOLLOW-UP
Decision: accepted for tested scope / limited operation / not accepted
Accepted scope and remaining limitations:
Business approver / timestamp / evidence reference:
If limited: workaround, authorised scope, expiry/review time:
Unresolved failures / unverified items / owners / due dates:
Retest plan and recorded result:
Temporary recovery access reviewed / removed by / when:
Synthetic artefact cleanup approval and completion:
Completed worksheet and evidence stored at:

A passing record covers only the scenarios and evidence actually checked. It is
not a legal guarantee or proof that every component, permission or external
service has recovered. Preserve unknowns; do not fill in assumed PASS results.

PRIMARY SOURCES (checked 2026-09-06; recheck when using)
https://learn.microsoft.com/en-us/sharepoint/restore-deleted-site-collection
https://learn.microsoft.com/en-us/sharepoint/sharepoint-admin-role
https://learn.microsoft.com/en-us/microsoftteams/private-channels
https://learn.microsoft.com/en-us/microsoftteams/shared-channels