Esc

↑↓ move↵ openIndex · Pagefind
Scheduling / Resources and costs: assignments, resource usage, cost loading, Budget reconciliation, leveling and workforce capacity

Resources and costs: assignments, resource usage, cost loading, Budget reconciliation, leveling and workforce capacity

Work through every resource assignment in one table, see a resource's usage over time against its limit, retain cost-loaded schedule reports, reconcile activity cost to Budget lines, review leveling proposals, map schedule resources to people, crews and equipment, and check daily workforce capacity.

On this page

Time is half of a schedule; the work and money behind it are the other half. In the Planner, the Assignments view and Resource Usage let you edit and inspect resource loading as you plan. The panels further down turn a saved version’s resource and cost loading into retained reports: immutable records with their inputs, engine revision and input digest. You can show what the schedule implied on a given day. None of the reports changes the plan, the field schedule, the Budget or the books.

Assignments view

Choose Assignments as the Planner’s display mode to see every resource assignment in the plan as one table, like P6’s Assignments window. You can group by resource, role, activity or activity code with totals, sort on up to four keys, and edit units, units per day, price per unit, costs and the curve in place. Edits follow the activity’s duration type and are one undo step each. See Assignments view.

Resource usage

Resource Usage on the Planner toolbar opens P6’s Resource Usage Profile and Spreadsheet under the view.

  • Which resources: by default, the resources assigned to the selected activity, following your selection. Untick Resources of the selected activity to pick resources yourself. With several, Show charts them combined or one at a time.
  • Profile draws budgeted and remaining units or cost per interval as bars, with cumulative curves on the right axis and, for units, the resource’s limit as a dashed line. Spreadsheet shows the same figures as a table, with the limit and each interval’s peak day.
  • Interval: day, week (starting Monday) or month, set here rather than by the Gantt timescale.
  • Over-allocation: an interval is marked in the risk colour when, on any of its days, remaining units exceed the resource’s max units per time. The limit is the resource’s maximum per day (from max units per day, else max capacity, else max units per hour × calendar hours, using any dated limits) times its working days in the interval.

How the numbers are spread:

  • Dates come from the last calculation: the actual start if there is one, else the early start, to the early finish. Assignments without calculated dates are listed as not phased. With unsaved edits, the pane says so; save and calculate to phase edited dates.
  • Budgeted units and cost spread over the whole span. Remaining units and cost spread from the later of the start and the data date to the finish. Completed activities have no remaining.
  • Values spread over the working days of the activity calendar, evenly by default. An assignment’s curve (Linear, Bell Shaped, Front Loaded, Back Loaded, Triangular, Trapezoidal, Early Peak, Late Peak, Double Peak, Three Step, or a curve carried in from the plan) weights each working day, and the intervals still add up to the assignment’s totals. Curves change only the timing, never units, cost or duration.

The pane’s display, measure, interval and resource choice are saved in the layout. It shows at most 1,000 intervals. Resource Usage reads the draft you’re editing; it doesn’t create a retained report. For retained, versioned demand reports, use Resource histograms.

Cost reports

A cost report runs the engine’s cost loading on a saved version. You choose daily, weekly or monthly buckets. It returns:

  • Time-phased cost curves by period.
  • Cost-loaded earned value, with each assignment’s cost and effective rate.
  • Expenses, with amounts kept as exact decimal strings.
  • Qualifications saying what the numbers rest on.

The qualifications are part of the result. If actuals are missing, an earned-value actual cost proxy may be used, and it’s labelled. If coverage is incomplete, CPI and forecasts are withheld. Mixed currencies are never converted; they’re marked as not comparable. Planned value uses the current schedule, because there’s no approved cost baseline yet.

In the Planner, create a report from a saved version, browse 25 periods a page, and reopen any report later without recalculating it. Downloads include the full JSON.

Earned value and period performance

The Planner’s Earned Value columns show BAC, planned value, earned value, actual cost, variances, CPI, SPI, CVI, SVI, TCPI, ETC, EAC and VAC per activity, in cost and in labor units, with the project baseline as the planned value basis. Costs include activity expenses, as P6’s do. Financial periods and Store Period Performance keep each period’s actuals, earned value and planned value as an immutable record, which feeds the Period performance section of Schedule › Resources & cost › Costs & EVM and the Planner’s Actual This Period columns. See Period performance and earned value.

Activity expenses

Activity expenses, the P6 costs that aren’t resource assignments, are edited on the Activity Details Expenses tab and carried through XER and P6 XML. The cost dashboard (GET /cost-dashboard and its CSV export) reports them in a separate expenses block: totals, each cost account, each activity, and planned and forecast cost by period. A Start of Activity expense falls on the start day, End of Activity on the finish day, and Uniform spreads over the activity’s working days. Planned cost follows the planned value span, and remaining cost is forecast over the remaining calculated span after the data date.

Expenses are reported beside the ledger-based budget at completion, never added to it, because an expense the Budget also carries would otherwise count twice. Activities with expenses but no calculated dates are listed as undated.

Cost accounts and cost codes

P6 cost accounts arrive with expenses and resource assignments, as a tree. On the Costs page, Cost account mappings maps each account to one of the project’s cost codes, so schedule costs can be read against the Budget.

  1. Review the accounts. Each account in the current schedule is listed with its expense items, assignment count and expense at completion.
  2. Map an account to a cost code. An account you leave unmapped inherits the nearest mapped parent in the cost account tree.
  3. Save, with an optional reason. Each save stores the complete set as the next revision, and is refused if someone saved since you opened it. Earlier revisions stay readable; saving an old one restores it as a new revision. Every save is audited with what was added, removed and changed.

Budget reconciliation by cost code then shows, per cost code, the Budget’s revised budget and direct costs beside the mapped schedule expenses and assignment costs. Each item is counted once, so mapped plus unmapped equals the schedule totals to the cent. Schedule amounts are never added to Budget totals, BAC or ledger actuals, and nothing is posted. Mapping needs Schedule admin and Budget view (API tokens: budget:read).

Budget reconciliation

Budget reports connect schedule cost to the project Budget. You map activities to Budget lines with an allocation percentage, to two decimals. One line can take several activities, and one activity can split across several lines, up to 100%.

  1. Preview the Budget’s current lines and search them by cost code.
  2. Map activities to lines. The preview shows the source total, the mapped total and the unmapped total. Mapped plus unmapped always equals the source to the cent.
  3. Save the report. If the Budget changed since your preview, the save is refused, so a report always matches what you reviewed. Reopening a report never re-reads today’s Budget.

The report reads the Budget’s computed view, where direct costs include approved, pending and revise-and-resubmit items. Projected costs and commitments aren’t posted actuals. You can load a saved report’s mappings as a new draft, but saved mappings aren’t approved, reusable mapping revisions.

Resource histograms

A resource report shows demand per resource by day, week or month. Conflicts are worked out daily before the days are grouped into buckets. Completed work, milestones and currency allowances add no demand. Missing usage is excluded and counted, and missing capacity shows as unchecked, never as zero. Bars are scaled to each resource’s own peak; they aren’t a utilization percentage.

Leveling proposals

Leveling proposes moves that ease over-allocation. Project leveling settings (the default) uses the P6 leveling options from Schedule › Settings, as P6 does:

  • Leveling priorities: up to ten fields, such as activity leveling priority, total float, early start or remaining duration, each ascending or descending. With none, work is leveled in activity ID order, as in P6.
  • Level resources only within activity total float: when on, work never moves past its late start, and conflicts that can’t be solved stay unresolved. When off, work may extend the finish.
  • Preserve minimum float keeps the stated hours of float in reserve when leveling within float.
  • Max percent to over-allocate: when leveling within float, an activity that can’t fit under a resource’s limit is retried with the limit raised by this percentage. Tolerated over-allocations are listed.
  • Level all resources, or only the ones you choose. The others are still counted but never delay work.
  • Preserve scheduled early and late dates: when on, the proposal reports leveled dates beside the scheduled ones. When off, leveled dates replace the early dates and float drops by the delay.

WBS summaries aren’t leveled, and a resource-dependent activity waits only for its driving resources. Choosing Within float or Extend finish in the Planner overrides the float setting for that run.

Every run is a proposal. Nothing is written back to the plan. The review shows each move, proposed date ranges, the finish change, peaks before and after, unresolved conflicts and any peaks that went up. The heuristic is deterministic, but it isn’t guaranteed to find the optimal answer. Apply a change you agree with by editing the plan.

Resource mappings

Map each schedule resource to a Workforce person or crew, an Equipment unit or a project Material, up to 500 entries. The preview flags unmapped resources, one source mapped by several resources, and unit mismatches. Matching labels aren’t treated as verified conversions, and rates and contact details are left out. A saved mapping report is unapproved evidence. It reserves no crew, moves no stock and applies no dates.

Workforce capacity

Check a date window of up to 366 days against the people who will do the work:

  1. Map each schedule resource to one person, with how many minutes one unit of demand means.
  2. Preview daily demand in minutes against each person’s recorded availability. Each day gets one status: person unavailable, capacity unknown, demand exceeds capacity, demand incomplete, allocation review required, or no excess in recorded demand.
  3. Save the review. It’s retained with an audit event, and refused if the underlying data changed since your preview.

Availability is recorded per person in Workforce Planning › People under Daily availability: whole available minutes per day, zero for unavailable, blank for unknown. If several resources map to one person, their demand is combined but their capacity is counted once. Existing allocations are shown as overlap warnings, not subtracted reservations. Shift-level conflicts aren’t detected.

Permissions

Every panel requires Schedule admin. Budget reconciliation also needs Budget view access with both tools enabled. Mappings and workforce capacity also need access to each owning tool (Workforce, Equipment, Materials). API tokens need schedule:read to read and schedule:write to create, plus budget:read for Budget reports.

Limits

  • Resource assignments are edited in the Planner (Activity Details and the Assignments view), but the resource dictionary itself (resources, roles, rates and limits) comes from the plan or the import and isn’t edited in the app.
  • Resource Usage phases over calculated dates only, and doesn’t level or move work.
  • No approved cost baseline, mapping approval or forecast approval.
  • No unit conversion between schedule resources and suite records.
  • Leveling and capacity checks never change dates, reservations or stock.
  • Leveling doesn’t consider other projects’ assignments, even when that P6 option is on; the proposal says so. To level shared resources across projects, use cross-project leveling. The resource list to level isn’t read from or written to P6 files yet.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file