Dynamics 365 Project Operations: Create Draft Time Entries from Assignments and Bookings

Instead of forcing project staff to start from an empty, uncontextualized time-entry grid—or making them pull from an import menu after the fact—the Enhanced Team Member experience shifts the starting point of time reporting to the views where employees actually inspect their weekly work. When a team member selects a given week from their staffed projects or assigned tasks and triggers time logging, Dynamics 365 Project Operations prepopulates draft time entries based on those booked or assigned hours.

For project managers, billing analysts, and Dynamics 365 administrators, this is a very practical workflow refinement. It bridges the gap between resource scheduling and actual time tracking while keeping the mandatory review-and-approval guardrails intact.

Why Contextual Time Logging Matters in Project Operations​

To appreciate why moving a "Log time" button into the assignment and booking views matters, it helps to look at how Dynamics 365 Project Operations handles resource data under the hood. In Microsoft's Time overview documentation on Microsoft Learn, time entries are defined not merely as attendance records, but as the core mechanism for recording the actual time a resource consumes. Those entries drive downstream calculations for both internal cost and customer-facing sales prices as tasks progress, and they link directly into contract lines for billable work. They also alert resource managers to schedule variances, absences, or out-of-office periods on the schedule board.

Historically, Dynamics 365 Project Operations (and its predecessor, Project Service Automation) allowed users to open the Time Entries grid and import data from bookings, assignments, or Exchange calendars. However, as Microsoft Learn's documentation on weekly time entry customization notes, that import workflow requires users to start inside the time grid, specify a date range, and explicitly select which bookings to copy into draft entries.

Starting from a blank grid forces the user to work backward: you open the time sheet first, then go hunting for the project and task records you were supposed to be working on. If you are creating an entry manually for a task you weren't even formally assigned to, you have to dig into the Project Task lookup dialog, click Change View, and switch to the All Active Project Tasks view just to find the right line item.

By allowing users to initiate time entry creation directly from the new Projects and Assignments views inside the Project Operations Team Member app, Microsoft flips the workflow around. Staff members review their scheduled work for the week first, verify their tasks, and push those expected hours straight into the time entry grid as drafts.

How the Enhanced Team Member Workflow Operates​

According to Microsoft Learn's preview documentation for the Enhanced Team Member experience, the feature applies to both Project Operations Integrated with ERP and Project Operations Core deployments. Once an administrator enables the feature, two new navigation items—Assignments and Projects (alongside Bookings)—appear under the My Work section exclusively within the Project Operations Team Member web app.

The new workflow provides two primary paths for generating weekly time sheets:

1. Logging Time from Task Assignments​

1. Open the Project Operations Team Member app.
2. Navigate to My Work and select Assignments.
3. Navigate to and select the specific week for which you need to record time.
4. Select Log time.
5. Project Operations automatically generates draft time entries for that week based on your Task Assignment hours for the selected period, displaying a confirmation dialog that shows the total number of hours logged.
6. Navigate to Time Entries, select the corresponding week, review the prepopulated draft entries, make any necessary adjustments, and submit them for approval.

2. Logging Time from Project Bookings​

1. Open the Project Operations Team Member app.
2. Navigate to My Work and select Projects.
3. Select the target week for time reporting.
4. Select Log time.
5. The system generates draft time entries for that week based on your Booked Project capacity for the period, again presenting a confirmation dialog with the number of hours logged.
6. Go to Time Entries for that same week to inspect the draft records and submit them to your project approver.

Time-Phased Views and Private Task Checklists​

The time-logging shortcut is part of a broader upgrade to how team members view their workload. Within the Team Member app, users can inspect active bookings and task assignments across past, current, or upcoming weeks. By switching from the standard My Bookings view to My Time Phased Bookings (or My Time Phased Assignments under Assignments), users can group their staffed hours by Daily, Weekly, or Monthly horizons—with Weekly set as the default—and toggle a time icon to show or hide staffed hours for each time slice.

Furthermore, clicking a project task hyperlink inside the Assignments view opens a side pane with two tabs: My Check-list and Notes. Team members can break complex tasks down into personal milestone checklist items (which dynamically update an Overall Progress bar at the bottom of the pane) and attach notes with files up to 5 MB in formats including PDF, TXT, DOC, DOCX, XLS, XLSX, CSV, PPT, PPTX, PNG, JPG, and JPEG. Microsoft Learn explicitly notes that these checklist items and notes are strictly private to the individual user; neither peers nor project managers can view them.

Section Summary: The Enhanced Team Member experience lets users push draft hours into the Time Entries grid directly from either their weekly task assignments or their booked project capacity, while adding time-phased workload views and private task checklists.

Prerequisites and Step-by-Step Admin Enablement​

This capability is not turned on automatically for end users; it must be enabled by a system administrator. Before attempting to turn it on, administrators must verify that their Microsoft Dynamics 365 Project Operations environment is updated to version 4.166.0.X or later. Microsoft's documentation states that the feature is unavailable in earlier builds.

To enable the Enhanced Team Member experience in a supported environment, follow these steps as documented on Microsoft Learn:

1. Sign in to Dynamics 365 Project Operations with a System Administrator security role.
2. In the left navigation pane, switch the area switcher to Settings.
3. Under the General section, select Parameters.
4. When the list of organization units appears, double-click (or double-tap) the Organization Units row on a column that is not a hyperlink.
5. On the Project Parameters page, locate the Feature Control field and select Feature Control.
6. Select Enable Enhanced Team Member experience feature, and then click OK. (Note: If the option reads "Disable Enhanced Team Member experience feature," the capability is already active in your environment.)

Customizing the Grids in Power Apps​

For organizations that track custom metadata on bookings or resource assignments, administrators can tailor the columns that team members see before they click "Log time." According to Microsoft Learn, the grids are powered by standard Dataverse views that can be modified through Microsoft Power Apps:

• To customize the Bookings grid, update the My Bookings view located inside the Bookable Resource Booking table.
• To customize the Assignments grid, update the My Assignments view located inside the Resource Assignment table.

Section Summary: Administrators need Project Operations version 4.166.0.X or newer to activate the feature under Project Parameters > Feature Control, and they can customize the underlying grid columns via Power Apps.

Roadmap Timeline Discrepancies: What IT Planners Need to Know​

If you are trying to pin down when this feature moves from preview to General Availability (GA), you will notice a discrepancy between Microsoft's tracking portals—a fairly common quirk when enterprise features span both Dynamics 365 release waves and the unified Microsoft 365 roadmap.

While the archived 2026 Release Wave 1 plan on Microsoft Learn listed an October 2026 general availability target, the live AI at Work roadmap entry (ID 576763) lists the feature status as In development with a General Availability target of March 2027. Because the Release Wave 1 page carries an October 2026 archive notice directing administrators to the live roadmap for current plans, IT leaders should treat March 2027 as the current GA target while recognizing that the preview bits are already documented for environments running build 4.166.0.X or later.

Critical Governance and Billing Considerations​

From an enterprise IT and project accounting standpoint, any feature that automates time entry creation deserves a balanced look. Why? Because a resource booking or a task assignment is a record of intent, not a record of execution.

Just because a senior systems engineer was booked for 20 hours on Project Alpha and assigned 20 hours of migration tasks on Project Beta does not mean the week played out that way. Production outages happen, client meetings get rescheduled, and priorities shift mid-week.

Fortunately, Microsoft designed this workflow to generate Draft time entries rather than submitting them automatically. Users are still required to navigate to the Time Entries grid, inspect the generated hours for the corresponding week, adjust the durations to match actual work performed, and manually submit the entries for manager approval.

However, Microsoft's public documentation leaves a few operational questions unanswered that administrators should test in a sandbox environment before rolling the feature out to production users:

• Overlap between Bookings and Assignments: Since users can click Log time from both the Assignments view (which pulls from task assignment hours) and the Projects view (which pulls from booked project capacity), what happens if an employee clicks Log time in both places for the same week? Administrators should verify how the system handles potential duplicate drafts when a user has both a hard resource booking and specific task assignments on the same project.
• Mid-Week Re-Logging: If a user generates draft entries on Wednesday and clicks Log time again on Friday after a project manager updates their task assignments, teams will need to verify whether the system overwrites existing drafts, appends only the delta, or creates duplicate lines.
• Human Complacency: The biggest risk with prepopulated time sheets isn't software bugs; it's human nature. When a system auto-fills 40 hours of plausible-looking project tasks, busy employees may be tempted to rubber-stamp the drafts and hit submit without adjusting for actual variance. Project managers and finance teams must reinforce the policy that prepopulated drafts are a starting template, not an excuse to skip reviewing actual billable hours.

If your organization is running Dynamics 365 Project Operations on version 4.166.0.X or later, spinning up this preview in a test environment is a smart move. It takes the tedious data-entry work out of Friday afternoons while keeping human judgment—and project manager approval—firmly in the loop.