In a new walkthrough, Pragmatic Works demonstrates how Copilot in SharePoint can create a full project management site from a plain-language prompt. The presenter, Devin Knight, guides viewers through planning, reviewing, building, and editing a site that contains libraries, lists, pages, and dashboards. Consequently, the video shows both the speed gains and the hands-on checks needed when AI generates an organizational solution.
First, the clip frames the problem: creating a project hub usually takes many manual steps such as defining lists, columns, views, and pages. Then, it highlights an alternative where users describe their needs and let the AI propose a structure. As a result, the demo aims to help business users and site owners decide if a Copilot-assisted approach fits their workflows.
Moreover, the video includes timestamps for each phase of the process, from planning at 02:32 to publishing at 14:09. This makes it easy to follow specific moments like the build plan review and final edits. Therefore, the presentation balances a practical demo with clear signposts for viewers who want to replicate the steps.
The demo begins by explaining what a project-management hub should contain, such as templates, executive reports, meeting notes, and PMO documents. Next, Devin Knight uses the Create sites with AI experience to translate a natural-language prompt into a proposed site plan. He then inspects generated lists, libraries, columns, and views, showing how the draft maps to typical project needs.
After reviewing the plan, the presenter asks Copilot for refinements, including additional views and clearer page narratives. Then, the build process runs and the video displays the steps that occurred behind the scenes. Finally, the presenter edits the homepage with Copilot to improve wording, remove placeholders, add quick links, and create a team section before publishing.
This sequence illustrates a loop of prompt, review, refine, and build, which highlights the interactive nature of the feature. Therefore, users are not locked into the first proposal and can iterate until the site meets project needs. In sum, the demo provides a hands-on model for turning a concept into a working SharePoint solution.
The video emphasizes that Copilot can create structured SharePoint artifacts such as task lists, milestone trackers, risk and issue registers, decision logs, and document libraries. In addition, it generates custom columns, views, navigation, and sample content so teams can start using the site quickly. This structured output supports filtering, governance, and reuse across Microsoft 365 services.
Moreover, the experience leans on natural-language configuration and a proposed plan that users can review in chat before construction. Consequently, the tool reduces manual setup while keeping owners in control of naming, metadata, and site scope. As a result, teams can move faster without giving up the ability to refine and correct the design.
Also, the video shows Copilot’s ability to explain build steps and reveal what it created, which helps with transparency. Therefore, administrators can audit the resulting lists and pages and make governance decisions based on a clear record. This combination of speed and visibility aims to lower the barrier for non-developers to build functional SharePoint solutions.
While the AI-assisted approach speeds site creation, it introduces tradeoffs between speed and precision. For example, autogenerated metadata or sample data may not match an organization’s taxonomy or compliance rules, which means manual cleanup is often required. Therefore, teams must balance the convenience of a quick build with the effort to align the site to governance and security policies.
Another challenge is that Copilot can misinterpret ambiguous prompts, leading to irrelevant lists or views that require rework. Moreover, tenant-level rollout variations and staged availability mean features may differ across organizations, which complicates planning. Thus, organizations should expect an iterative process and plan for validation in non-production environments.
Finally, permissions and integration with other systems may still need manual configuration, especially for complex workflows or Power Platform integrations. As a result, IT and governance teams should stay involved during initial builds to enforce access rules and data handling practices. In short, Copilot accelerates creation but does not remove the need for oversight and thoughtful design.
To get the most from the tool, the video suggests writing clear prompts, answering Copilot’s clarifying questions, and reviewing the proposed plan before building. Moreover, testing the generated site in a sandbox and then iterating reduces the risk of deploying an incomplete structure to a production audience. Therefore, a staged approach helps teams validate content, permissions, and metadata.
In addition, reviewers should use the build review feature shown in the demo to understand what was created and then refine column names, views, and page narratives. This human-in-the-loop step is essential for governance and user adoption because it aligns the site to real project needs. Consequently, teams can combine AI speed with human judgment to create useful and maintainable project hubs.
Overall, the Pragmatic Works walkthrough provides a practical look at how Copilot in SharePoint can reduce routine setup while still demanding thoughtful review. Therefore, organizations should weigh faster delivery against customization and governance needs as they adopt AI-assisted site creation. In this way, the video helps decision makers and practitioners understand both the promise and the limits of the new approach.
SharePoint project management site, Copilot for SharePoint, Build project site SharePoint, SharePoint project management with Copilot, Microsoft Copilot SharePoint integration, SharePoint project tracker, Create project site in SharePoint, Project management templates SharePoint