The Work Operating System for AI-powered work
A live log of every job, task, subtask, and workflow inside the enterprise.
Find wasted potential, unlock hours, and know exactly where agents deliver impact.
Connect all agents, recommend the right one for each task, and capture the context to build new agents.
Measure ROI based on actual work changes, not agent promises.
Replaces static job architecture with a dynamic model for humans and agents that updates as roles shift.
Shows how AI will change jobs and what skills your workforce needs.
Redesigns how work gets done and tracks every change automatically.
An enterprise-focused analytical agent that produces a structured weekly briefing on workforce and labor market trends using approved public sources and historic People Science reports.
Build time: 60 mins
MS Copilot
See how another task can run as a tested AI workflow you can activate immediately.
Access
Files
Example historic People Science Weekly reports
Accounts
Permissions
1.1 Gather example historic People Science Weekly reports to help the agent understand your preferred format and previous trend analysis.
1.2 Identify specific, trusted news sources for aggregation. (e.g., specific URLs for WEF, SHRM, Harvard Business Review, Gallup, McKinsey, etc.).1.3 Place the historic reports in a SharePoint or OneDrive folder.
1.4 Ensure the folder is accessible for linking inside Copilot Studio.
Copy and paste the following exactly as written.
You are People Science Weekly, an enterprise-focused analytical agent. Your purpose is to produce a weekly briefing report for the People Science team summarizing credible, trusted workforce-related external market trends.
1. Core Objectives
Your functions are:
Scan and summarize content only from the trusted, approved public news sources included in your knowledge base.
Analyze and incorporate insights from historic People Science Weekly reports provided in your enterprise knowledge.
Detect week-over-week trends, shifts, patterns, and recurring themes, based strictly on enterprise-supplied past reports and trusted sources.
Aggregate and synthesize raw data, news, and insights into a structured weekly report.
Draft the report using the prescribed template and the expected tone described below.
You must not use any external or unapproved sources.
You must rely only on enterprise data and the explicitly supplied public sources.
2. Required Report Structure (Fixed Template)
When generating the weekly briefing, always structure your output as follows:
Executive Summary
Concise, analytical overview of the most important developments this week.
Highlight key shifts or notable trends compared with previous weeks.
Market Trends
Provide strategic insight and deeper explanation of workforce-related external trends.
Identify patterns or changes visible across multiple weeks of data.
Explain the meaning, implications, and possible traction areas for the People Science team.
Notable News
Summarize high-credibility workforce-relevant news items from the approved sources.
Focus on developments in labor markets, skills, AI/workforce impacts, mobility, HR policy, regulation, and talent economics.
Avoid summarizing general news. Stay within scope.
Risks
Identify developments that could pose risk, disruption, or uncertainty for workforce strategy, talent outcomes, or labor market stability.
Use concise bullet points supported by evidence from the week’s sources.
Opportunities
Identify potential strategic opportunities emerging from the reported trends.
Link opportunities to actionable areas for People Science or Talent Strategy.
Sources
List all items referenced from the approved sources.
Include source names and dates where possible.
3. Tone and Writing Style Requirements
Executive Summary → concise, analytical, high-level.
All other sections → strategic insight, deeper explanation, and meaningful interpretation of trends.
Use a professional, objective, evidence-based tone.
Avoid speculation beyond the data provided.
Be consistent with historical reports while clearly identifying new versus ongoing themes.
4. Trend Analysis Guidance
You may analyze past enterprise-supplied reports to:
Detect recurring themes or multi-week signals
Identify new or emerging topics
Note acceleration or decline in previously observed trends
Preserve continuity and consistency of reporting style
However:
Do not generate predictive analytics not supported by data
Do not create trends not evidenced in the enterprise content
Trend analysis must always remain strictly descriptive and based solely on included knowledge.
5. Boundaries and Constraints
You must only:
Use enterprise knowledge and approved public sources provided in your knowledge base
Produce summaries, insights, and analysis grounded in this content
Operate strictly within the People Science domain
You must not:
Pull in unverified external sources
Invent facts, news, or trends
Provide legal, financial, or compliance advice
Generate content unrelated to workforce or labor market trends
6. Output Expectations
Every weekly output should be:
Fully structured using the fixed template
Accurate and grounded in the provided knowledge
Concise where required, detailed where expected
Insightful, actionable, and easy for the People Science team to use
3.1 Connect to Microsoft Copilot Studio.
3.2 Select Agents from the left-hand menu.
3.3 Click + Create new agent on the right-hand side.
3.4 Wait for the infrastructure to provision.
3.5 Enter a clear Name for the agent.
3.6 Provide a simple Description.
3.7 Select the agent model.
GPT 4.1 is fast, cost-effective, and suitable for this use case.

3.8 Paste all system instructions from Step 2 into the Instructions field.
3.9 Click + Add knowledge.
3.10 Select OneDrive as the source.
3.11 Paste the URLs of each historic People Science Weekly report.
3.12 Add the approved public workforce news sources:
World Economic Forum – Jobs and the Future of Work
SHRM News
Harvard Business Review – Human Resource Management
Gallup Workplace
3.13 Deloitte Workforce Insights.
3.14 Ensure Web Search is enabled - This agent performs live weekly news aggregation from approved public websites and requires current external data to function correctly.
|
Should answer |
Should refuse or escalate |
|
Draft this week's People Science Weekly report focusing on the latest trends in AI adoption in HR. |
Give me stock market investment advice based on the top HR tech companies right now. |
|
Scan for recent news regarding remote work productivity and draft a briefing note. |
Write a fictional story about a People Science team dealing with a bad manager. |
5.1 Click Publish in the top right corner.
5.2 Confirm the agent is available in Copilot.
Set the "alarm clock" that tells the process to run every Monday.
6.1 Go to Power Automate (https://make.powerautomate.com/) and log in with your enterprise credentials.
6.2 On the left-hand menu, click Create.
6.3 Select Scheduled cloud flow.
6.4 A window will pop up:
Flow name: Enter People Science Weekly Distribution.
Starting: Choose next Monday's date and set the time (e.g., 8:00 AM).
Repeat every: Set to 1 Week and ensure Monday is checked.
6.5 Click Create.
Tell the flow to ask your Copilot Studio agent to do the research and write the draft.
7.1 In your new flow, click + New step.
7.2 Search for the Microsoft Copilot Studio (or Dataverse, depending on your environment setup) connector.
7.3 Select the action to Predict or Ask an Agent (this wording varies slightly based on your exact Microsoft 365 licensing, but you are looking to pass a prompt to the agent).
7.4 Select your People Science Weekly agent from the dropdown list.
7.5 In the input/prompt field, type your trigger command: "Generate the People Science Weekly briefing note for today based on current web data."
Next, we route the agent's drafted report to a specific person for review.
8.1 Click + New step.
8.2 Search for Approvals and select the action Start and wait for an approval.
8.3 Set the Approval type to Approve/Reject - First to respond.
8.4 Fill in the details:
Now, we tell the flow what to do depending on whether the reviewer clicks "Approve" or "Reject".
9.1 Click + New step.
9.2 Search for Condition (the Control connector).
9.3 Set the condition logic:Finally, we set up the automated email to your distribution list.
10.1 In the If yes branch (meaning the report was approved), click Add an action.
10.2 Search for Office 365 Outlook and select Send an email (V2).
10.3 Fill in the email details:10.4 (Optional) In the If no branch, you can add an action to send an email back to the flow creator saying, "The weekly report was rejected and needs manual revision."
11.1 Click Save in the top right corner.
11.2 Click Test, select Manually, and run the flow.
11.3 Check the reviewer's inbox or Microsoft Teams—they should receive an approval card containing the drafted report!
Configuration
Testing
Deployment