01
The Blueprint
The detailed guide for this solution. Use the copy-and-paste Copilot Chat prompts or the manual SharePoint fallback steps.
Back to all blueprints
Trusted delivery knowledge
Give project teams one practical home for decisions, delivery status and the work that must not get lost.
This blueprint helps you build or reset a project management hub so project information is not trapped in personal folders, chats and duplicated status packs.
This blueprint is for you if…
- Project teams juggling disconnected files, meeting notes, risks and status reports
- PMOs that need a repeatable workspace pattern without a heavyweight platform rollout
- Delivery leads who need decisions, actions and handovers to stay findable
- Teams wanting a Copilot-ready source for project context without exposing unreviewed content
What changes when it is working
- A reusable home for project status, plans, decisions, risks and key artefacts
- Clear boundaries between project working content, approved records and closed-project knowledge
- Views that make the right information visible to sponsors, delivery teams and project owners
- A simple, repeatable project workspace pattern that can scale across programmes
What is inside the package
Three downloads. One complete way to work.
Your purchase includes the Project Management Hub, a short How to Use Your Blueprint visual guide and the Simply SharePoint Best Practice Guide. The detailed Blueprint shows what to create in SharePoint, how to use Copilot Chat and how to continue manually if Copilot is not available.
02
How to Use Your Blueprint
A short visual guide to the Simply SharePoint method, the two routes, checkpoints and what to do when Copilot is unavailable.
03
Simply SharePoint Best Practice Guide
The practical foundations for trusted sources, natural-language naming, useful metadata, ownership, lifecycle and governance.
Inside the product-specific Blueprint
One detailed guide, taking you through the components in order.
These are sections of the single detailed Blueprint—not separate workbooks, template packs or pre-built sites.
01
Complete project hub component plan
The exact components you create: working documents, templates and guidance, closed records and handover, plus decisions, risks, issues, actions and status reports.
02
Component-by-component Copilot Chat prompts
Prompts to create each library, list, metadata field, view and formatting rule from inside the relevant SharePoint component.
03
Checkpoints after every component
Short checklists after each library and list so you confirm columns, views, formatting and access settings before moving on.
04
New project workspace sequence
Start with the SharePoint site, create the project components in order, add pages and navigation, then test the handover route.
05
Existing project clean-up route
A staged inventory, review and decision sequence for duplicate files, unclear records and content that needs handover or archive.
06
Manual fallback, testing and launch
Manual SharePoint steps if Copilot is unavailable, plus launch, status and close-out checks.
Two routes inside every blueprint
Start fresh—or make an existing workspace trustworthy.
You do not need to throw away what already exists. The Blueprint gives you a safe sequence for a clean configuration and a separate route for cleaning up content already in use.
Route A
Build from scratch
01
Define the project container
Confirm the outcome, project audience, trusted source boundaries and what belongs in the workspace.
02
Set the delivery model
Use the blueprint to create a consistent plan, decision, risk, issue and action pattern.
03
Build useful views
Configure lists, library views, page sections and navigation around how each role actually works.
04
Launch the routine
Validate ownership, status cadence, project closure and the handover path.
Route B
Clean up what exists
01
Map the current mess
Inventory folders, duplicated packs, informal records and project content with no obvious owner.
02
Choose the source
Decide what becomes the trusted project record and what stays reference material or retires.
03
Apply a reviewed model
Use Copilot to suggest classification and views; the project owner confirms the final tags and status.
04
Handover clearly
Make the live project, current decisions and closure material visible without a scavenger hunt.
Where Copilot helps
Use prompts to accelerate the configuration, not to skip the thinking.
- Draft a reviewed project-site plan, library structure, lists and columns
- Summarise selected project artefacts and find candidates for decision, risk or handover review
- Suggest metadata tags and views for a defined project information model
- Help create repeatable launch, status and close-out material from trusted sources
What remains human
The decisions that make a solution trustworthy.
- A project workspace is a defined container, not an unrestricted dumping ground.
- Owners decide what counts as a record, decision or current delivery status.
- Use natural-language file titles so project knowledge remains useful after the project team changes.
- Close and hand over deliberately so lessons learned remain reusable.
Copilot in SharePoint is required. The person following this Blueprint needs access to Copilot in SharePoint and the target workspace must meet your organisation’s licensing, tenant availability, permissions and content-governance requirements. Advanced work at scale may use Copilot Credits. If a Copilot capability is unavailable, the manual SharePoint route in the detailed Blueprint keeps the configuration moving.
Ready when you are
Get the Project Management Hub package.
Get the detailed Blueprint, the How to Use Your Blueprint visual guide and the Simply SharePoint Best Practice Guide—then create or clean up your Copilot-ready workspace at your own pace.