Defined implementation
Make SharePoint and Teams files easier to find.
Reorganize the agreed SharePoint sites and Teams, correct permissions and name their owners. Set rules for creating and retiring workspaces, then test the structure with users.
PricePrice fixed after a short scope call.
DeliveryThe proposal names the start date, the change windows and the completion date before anything is agreed.
What you receive · illustrative sample
Give every workspace a purpose and an owner.
Illustrative SharePoint and Teams decision register. Content moves, permissions and retention changes require owner approval.
| Workspace | Agreed action | Acceptance check |
|---|---|---|
| Active project team | Retain with named owner and review date | Membership and sharing checked |
| Completed project site | Archive under agreed retention rules | Owner can retrieve required files |
| Duplicate document library | Merge only approved content | Links, permissions and exceptions recorded |
Meet the person responsible for delivery.
Alwatheq Zboun leads the agreed work. A sample shows the format; the statement of work defines your deliverable and acceptance checks.
Engagement context
When this engagement applies.
There are more Teams than people, half of them abandoned, and nobody can find the final version of anything.
Scope considerations
- A named site and Team list, agreed up front
- Tested with real users before sign-off
- Workflow automation quoted separately
The defined work
Engagement scope.
- 01
Every site and Team in the agreed scope is inventoried and carries a keep, merge or archive decision with a named owner.
- 02
The target structure is built: the categories, naming and metadata that replace a folder tree nobody can navigate.
- 03
Content is moved into the new structure for the areas in scope, and the merged or archived Teams are actioned rather than recommended.
- 04
Permissions are corrected to match who should actually have access, including the guest and company-wide sharing that accumulated.
- 05
Lifecycle rules are applied — creation, naming, expiry and review — so the clutter does not rebuild the week after handover.
- 06
Real users run their real work through the new structure, and what fails in that test is fixed before sign-off.
Acceptance
Completion has an agreed standard.
Every Team and site in scope carries an actioned keep, merge or archive decision
The target structure is built and the in-scope content sits inside it
Permissions match the agreed access model, verified from real accounts
Lifecycle and naming rules are applied and documented
Each area has a named content owner who has accepted it
Real users have run their own work through the structure and the defects found are closed
Commercial basis
Price, scope and timing are considered together.
Engagement price
Price fixed after a short scope call.
The price is agreed in writing before any work starts and before anyone is given access. The call itself costs nothing. What moves the number:
What determines the scope
- Number of SharePoint sites and Teams in scope
- Volume of content to be restructured or moved
- Number of distinct permission groups and guest relationships to unwind
- Whether content migration is included or handled separately
- Whether the tenant has retention or compliance requirements affecting archival
Delivery calendar
The proposal names the start date, the change windows and the completion date before anything is agreed.
How engagements workScope & responsibilities
The full engagement boundary.
Review the exclusions, required client participation, change controls and operational handover for this engagement.
Exclusions
- Workflow or approval automation — that is One Workflow Automation Build
- Migration from a third-party platform, which is a Safe Migration engagement
- A full Purview classification or records-management programme
- Help desk and end-user support
- Ongoing content governance after handover
Client responsibilities
- Approve the site and Team list before any archival
- Nominate a content owner for each area
- Provide the users who will run the real-work test
- Own end-user communications and training
- Confirm retention and compliance requirements before anything is archived
Change and rollback method
- Nothing is deleted. Archival is reversible for an agreed retention window, and the window is stated before the first Team is touched.
- Permission changes run in batches verified from a real account in the affected group, so a correction that locks out a working team is caught the same day.
Operational record and handover
- The Teams and sites register, with the decision made on each
- The target structure: categories, naming, and the metadata that replaces the folder tree
- The permission map across the sites and Teams in scope, before and after
- The naming and lifecycle rules as applied
- The named content owners, and their acceptance
Before you commit
A clear first step.
You stay in control.
Start with the problem and the result you need. The initial fit conversation is free and does not require access to your systems.
Check client feedback on Upwork ↗Prefer to contract through Upwork? Contact Alwatheq there. Existing Upwork engagements continue through Upwork.
Who will actually do the work?
Alwatheq Zboun leads the scope, technical work and handover. If a specialist collaborator is needed, their role is agreed with you before work starts. Your proposal names the responsibilities and delivery windows.
What happens before you get access?
We agree the scope, fee and completion checks in writing. Access uses named accounts and only the permissions the work requires. Approved access is reviewed and removed at handover.
How do we know the change worked?
Your scope defines the pilot, test cases and acceptance checks. Results and exceptions are recorded. Recovery options and their limits are agreed before production changes; a failed check is addressed before the next approved stage.
Will we need an ongoing retainer?
A defined project can end at handover. Your team receives the agreed configuration records, runbook and walkthrough. Any limited support period is written into the proposal; ongoing support or additional work is a separate agreement.
Discuss this engagement
Put the scope in context.
Describe the problem, systems and deadline. Alwatheq will review the fit and the scope questions before preparing a written proposal.
Get the Cleanup Priced in Writing