Created with AI.
Use this routine when taking responsibility for a work package. Make expectations, progress and exceptions understandable to the project manager and colleagues, using Project Operations where relevant.
Continue in the business-area learning path
Describe the outcome and how the recipient will verify it. Agree assumptions, boundaries and acceptance ownership. An activity such as 'work on the report' is not a sufficient deliverable.
Record: recipient / deliverable / acceptance criteria / dependencies / deadline. Ask the recipient to confirm that the criteria demonstrate the need is met.
Break uncertain work into smaller parts and record estimate assumptions. Check dependencies and capacity before promising a date. Include verification and documentation as work.
Create an initial estimate and identify what investigation would improve it. A justified range can be more useful than one unsupported number.
Update what is ready, what remains and what blocks you. Record actual work following project routines and update remaining effort separately. Time spent does not show how close the deliverable is to completion.
Use: completed / remaining / risk / decision needed. Avoid reporting '90 percent' for several weeks without explanation.
When a customer asks for something new, assess the impact and raise it with the project manager. Distinguish clarification within agreed work from changed scope. Do not commit the project to extra work or dates without authority.
Practice case: A new export needs six hours and displaces testing. Present alternatives and consequences to the project manager; do not hide the effort under the original task.
Demonstrate the result against criteria. Explain usage, limitations and open items. Agree acceptance and ownership of further work. Remaining risks must accompany the deliverable.
A useful handover lets a colleague use or verify the result without you present. Ask them to test the explanation and correct gaps.
The working routines and fictional examples above are ProsessPilotene learning material. Use the official product documentation below for product context; availability depends on your organisation's setup.
Ask a question or share what helped you.
Use this routine when taking responsibility for a work package. Make expectations, progress and exceptions understandable to the project manager and colleagues, using Project Operations where relevant.

Published 9/10/2026
OpenAI’s Data agent could investigate company data and build shareable interactive dashboards. Access controls and source trails needed to follow analysis and action through the workflow.
Read more
Published 9/5/2026 · Event 6/2/2026
DynUG brought the Dynamics 365, Power Platform and Fabric communities together in Oslo.
Read more
Published 8/31/2026
Power BI reports and semantic models became grounding in Copilot Chat and Cowork. Shared chats, synced notebooks and Planner status connected analysis with collaboration.
Read more
Published 7/31/2026
Copilot Notebooks and Cowork gained more ways to share project context. Agent metrics and cost controls expanded in the admin centre.
Read more
Published 6/30/2026
Copilot administrators gained central controls for consumption-based cost. Purview controls extended to Cowork, and agent metrics could connect with organisational context.
Read more
Published 5/29/2026
Federated connectors could retrieve live SaaS data through MCP. Copilot Notebooks gathered project context while Word and Teams gained collaboration features.
Read more