Activity details and P6 fields
Edit an activity in the Activity Details pane, from General and Status through resources, relationships, activity codes, notebook, steps and user-defined fields, with P6 duration-type rules and edits that export to XER and P6 XML.
On this page
Select an activity in the Planner and the Activity Details pane opens below the table, as it does in P6. Every field is a native part of the plan: you edit it in the app, it’s kept in the saved version, and it’s written back when you export to XER or P6 XML.
The tabs
The tabs are General, Status, Resources, Predecessors, Successors, Relationships, Codes, Notebook, Steps, Feedback, WPs & Docs, Expenses, UDFs and Discussion. Use Customize tabs to reorder or hide them (at least one stays visible). Drag the pane’s edge to resize it. The tab setup, height and open state are saved in your layout.
| Tab | What you can edit |
|---|---|
| General | Activity name, WBS, activity type, duration type, % complete type (duration, physical or units), calendar, and the primary and secondary constraints with their dates. The activity ID is read-only. |
| Status | Original and remaining duration, actual start and finish, duration % complete, physical % complete and units % complete. |
| Resources | Resource assignments: budgeted and remaining units, units per day, budgeted and remaining cost, whether the rate is an override or the resource’s price, lag and remaining lag in hours, and Drives dates (P6’s Drive Activity Dates). Assign resource and Remove. |
| Predecessors, Successors, Relationships | Add a relationship by activity ID, type and lag in days, change type and lag, or delete it. The driving and critical flags come from the last calculation. |
| Codes | Assign activity code values. |
| Notebook | One note per topic. Bodies are up to 20,000 characters. |
| Steps | Weighted steps with name, weight, complete flag, % complete and notes, up to 500 per activity. |
| Feedback | Two fields, as in P6: Notes to Resources (instructions for the people assigned) and Feedback (what the resources and field team report back), plus a New flag for unread feedback. Both stay separate from notebook topics. |
| WPs & Docs | Links to project documents and drawings the work uses, plus every other item linked to the activity that you can see. See WPs & Docs. |
| Expenses | Costs that aren’t resource assignments, such as permits, hire charges or fees. See Expenses. |
| UDFs | Values for each user-defined field. |
| Discussion | Threaded comments with @mentions and private notes. See Working together on a schedule. |
Every field edit is one undoable draft step (Ctrl+Z, Ctrl+Y). Nothing is saved until you save and recalculate, which creates a new version. The exceptions are WPs & Docs links and Discussion, which are saved as you make them and aren’t part of the draft.
In a plan of more than 2,000 activities, a notebook longer than 1,024 characters loads when you open its activity in the pane, so you may see Loading activity details… for a moment. Before you edit codes, UDFs or notebook topics across the whole plan, choose Load activity notebooks. See Large schedules.
Duration types
When you change units, units per day or duration on an assignment, the Planner recalculates the other values with P6’s rules for the activity’s duration type:
- Fixed Duration and Units/Time
- Fixed Duration and Units
- Fixed Units
- Fixed Units/Time
The same rules apply when you edit an assignment in the Assignments view, which lists every assignment in the plan in one table and also sets each assignment’s curve. A curve shapes how the assignment’s units and cost spread over time in Resource Usage; it never changes units, cost or duration.
The engine itself doesn’t read duration type: in P6 it decides what’s recalculated when you edit, not how dates are scheduled. The stored results of those edits, such as remaining units per time, are what the calculation reads, in P6 and here.
Resource-dependent activities are different. Each driving assignment is scheduled on its own resource’s calendar, for its units divided by its units per hour (the remaining units and remaining rate once it has started). The activity starts with its earliest assignment and finishes with its latest, whether the assignments share one calendar or not.
Units % complete is actual units over at-completion units, summed across labor and nonlabor assignments. It comes in from XER and P6 XML, is kept with the activity and goes back out on export. Enter it on the Status tab or in the Units % Complete grid column (Status category) of an activity in progress: each labor and nonlabor assignment keeps its at-completion units, its actual units become that share and its remaining units the rest, and its remaining units per time follow so its remaining duration holds. Remaining duration is left alone. P6 does the same: you set the remaining duration or an expected finish yourself. An activity that hasn’t started takes no units % complete until you give it an actual start.
Assignment lag delays an assignment’s start by that many hours on its resource’s calendar. Before the activity starts, the remaining lag follows the lag; once it has started, edit the remaining lag, and a change to the lag leaves the remaining lag where it was. Clear Drives dates for an assignment that shouldn’t set the activity’s dates. With no assignment driving, the activity keeps its own calendar and duration. All three are also columns of the Assignments view, and all three go back out on XER and P6 XML export. See units percent complete and duration type.
Activity codes and UDFs
Manage the dictionaries under Activity codes, UDFs and notebook topics:
- Activity code types have a scope (Project, Global or EPS) and hierarchical values with a description up to 60 characters, a parent and a colour. Assign them one at a time on the Codes tab, or in bulk from the grid’s code columns.
- User-defined fields can be Text, Integer, Number, Cost, Start date, Finish date, Indicator (red, yellow, green or blue) or Code list.
- Notebook topics come from the plan, from an imported file, and a default Notes topic.
Codes and UDFs become columns, filter parameters and Group & Sort keys.
Steps
The Steps tab shows the activity’s weighted completion. If the project setting Activity percent complete based on activity steps is on, editing steps sets the activity’s physical % complete for you.
WPs & Docs
WPs & Docs ties the activity to the documents and drawings the work depends on: a method statement, a specification section, a shop drawing. Choose Document or Drawing, search by name, number or title, and Link. Unlink removes one. A linked item that has been superseded is marked Obsolete.
- A link is a reference. It never gates the activity, blocks it or records progress, unlike a submittal or RFI link.
- Linking needs Schedule edit and view access to Documents or Drawings. Each item shows only if you may open it there: a document you can’t see under its folder’s permissions simply isn’t listed.
- The tab also lists the other items linked to the activity that you can see, such as submittals, RFIs and daily-log evidence.
- Links belong to the saved activity. They take effect at once, without a save, and unsaved draft edits don’t change them. A new activity needs saving before it can be linked.
Expenses
Expenses are P6 activity expenses: costs on an activity that aren’t resource assignments. Each has an Expense Item name, a Cost Account, an Accrual Type (Start of Activity, End of Activity or Uniform), Budgeted, Actual and Remaining Cost, and optionally a vendor, document number, units, price per unit and description. Up to 500 per activity.
At Completion is Actual plus Remaining. Before the activity starts, changing the budget resets Remaining to it; changing Actual leaves Remaining at Budgeted minus Actual. Each change is one undo step.
Expenses count in the activity’s Total Cost columns, Group & Sort totals and the WBS window, and in its earned value (BAC, actual cost and estimate to complete), as in P6. An expense without an amount counts as zero. The cost dashboard reports them in an expenses block, by cost account and activity and spread over time by accrual type, in its API response and CSV export. They’re reported beside the Budget-based budget at completion, never added to it, because the same cost may already be in the ledger. See Resources and costs.
What exports, and how
| You edit | XER | P6 XML |
|---|---|---|
| Code types, values and assignments | Yes | Yes |
| UDF definitions and values | Yes | Yes |
| Steps | Yes (TASKPROC) |
Yes (ActivityStep) |
| Notes to Resources | Yes (TASKNOTE) |
Yes (NotesToResources) |
| Feedback and the New flag | Yes (TASKFDBK, rev_fdbk_flag) |
Yes (Feedback, IsNewFeedback) |
| Expenses, with their cost accounts and expense categories | Yes (PROJCOST) |
Yes (ActivityExpense) |
| Notebook topics and notes | Yes, one memo per topic entry | Yes, one note per entry |
| Resource assignments (units, units per time, rate, cost) | Yes | Yes |
| Duration type and % complete type | Yes | Yes |
Mistake: Expecting a duration-type change to move dates
In the app: Duration type changes what recalculates when you edit units or duration. Dates move only through duration, logic and calendars.
Mistake: Typing physical % complete on an activity with steps
In the app: With step-based % complete on, update the steps instead. Step edits set physical % complete.
Mistake: Using a code-list UDF as a reporting key for an owner on P6 who wants XER
In the app: Use an activity code. Codes keep their values and hierarchy through XER and P6 XML.
Mistake: Putting instructions for the crew in Feedback
In the app: Use Notes to Resources for instructions and Feedback for what comes back. P6 keeps them in separate tables.
Related
Keep exploring
Related across os.construction
- DocsP6 compatibility: settings, import, export and what round-tripsHow closely os.construction matches Primavera P6. Which scheduling settings the engine honours, which P6 calculated fields it works out, what crosses an XER or P6 XML file in both directions, the measured agreement with P6's own dates and costs, and the limits that remain.
- DocsViews and layouts: filters, Group & Sort, columns, Network and Trace LogicOpen and save P6-style layouts for yourself, the project or the company, export and import them as files, build filters with nested All/Any criteria and highlight mode, group and sort to five levels with totals, choose from 45 core columns plus baseline, cost, units and earned value columns, draw a progress line, read the logic in the Activity Network, Trace Logic and Assignments views, and roll the plan up in the WBS window.
- GlossaryAssignments ViewA schedule view with one row per resource assignment across all activities, showing units, costs, rates, dates and curves, for reviewing and editing resource loading in bulk.
- GlossaryActivity CodeA user-defined classification, such as area, trade, phase or responsibility, assigned to schedule activities so they can be filtered, grouped and reported.
- BlogHow to create a work breakdown structure for a construction projectA work breakdown structure splits the whole scope of a job into pieces you can schedule, budget and measure. Choose the split that matches how the job will be built, decompose to work packages one party can own, check the 100% rule, write a WBS dictionary, then tie the WBS to cost codes and schedule activities. Here is the method and a worked example for a three-story office building.
- BlogEarned value vs percent complete: one measures progress, the other tells you what it meansPercent complete says how much of the work is done. Earned value turns that progress into the budgeted value of the work done, so it can be compared with the plan and with what was spent. Here is how the two relate, when to use each, a worked example and the mistakes that make every job look on budget.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →