This article helps support agents handle questions about how BigPicture Standard supports resource planning, actual time tracking, workload visualization, and variance monitoring. It is based on a customer scenario where the user wanted to manage planning and execution in BigPicture without relying on external apps unless necessary.

Use this article when: The customer asks whether BigPicture Standard can compare planned workload with actual time spent, show non-uniform workload across a task, display past actuals vs future plan, or flag deviations automatically.

Issue pattern

Customers typically want to achieve all of the following in one workflow:

Plan resource allocation in BigPicture
Log actual time spent on work
Compare planned effort with actuals
Highlight overruns, delays, or schedule slippage
Show historical actual effort differently from future planned effort

In most cases, the key point is to explain the difference between what BigPicture Standard supports natively, what depends on Jira time tracking, and what requires Enterprise or an external time-tracking app.

Support answer summary

Customer need	What to say	Recommended handling

Customer need	What to say	Recommended handling
Non-uniform workload distribution within one task	Manual workload contouring is not available in BigPicture Standard. It is an Enterprise capability.	Recommend splitting work into smaller tasks or sub-tasks that reflect the real effort pattern.
Logging actual time in BigPicture	BigPicture does not include its own built-in time tracking.	Direct the customer to Jira native time tracking or 7pace Timetracker if they need richer time-entry capabilities.
Comparing planned vs actual effort	This is partially supported through Jira estimates, progress, remaining estimate, baselines, and workload views.	Explain the available visual methods and configuration options; do not promise automatic threshold-based alerts in Standard.
Automatic visual alerts for variance	Standard does not provide automatic alert rules for planned vs actual deviations.	Point to visual indicators such as shifted dates, progress differences, baselines, and red over-allocation markers in Resources.
Past actuals vs future planned workload in one view	Standard does not automatically switch past periods to actual logged time while keeping future periods planned.	Clarify that workload remains distributed over the task duration, even for past dates.

How to handle similar tickets

1. Confirm the edition and set expectations early

First verify whether the customer is using BigPicture Standard or Enterprise. This matters because some requested capabilities are edition-specific.

Important: If the customer asks about manual workload contouring inside a single task, explain clearly that this is not available in Standard and avoid suggesting there is a hidden setting for it.

Recommended wording:

In BigPicture Standard, workload is distributed evenly across the task duration. Manual shaping of effort within a task is not available there.

2. Offer the best-practice workaround for uneven effort

When a customer wants a task to carry different amounts of effort across different periods, the best workaround is to split the work into separate tasks or sub-tasks.

Use separate tasks for distinct phases of work
Assign different durations or estimates to each part
Use this approach when effort is front-loaded or back-loaded

Best practice: Recommend task splitting as the default answer for non-linear effort distribution in Standard. It is more accurate than trying to simulate uneven effort through capacity changes alone.

3. Clarify how actual time should be logged

If the customer asks whether actuals can be logged directly in BigPicture, explain that time tracking happens outside BigPicture itself.

Recommended options:

Jira native time tracking for Original Estimate, Remaining Estimate, and Time Spent
7pace Timetracker if the customer wants a more advanced time-tracking workflow with BigPicture integration

If needed, share these links:

4. Explain what “planned vs actual” looks like in Standard

Customers often expect a dedicated planned-versus-actual control panel. In Standard, this is not a single built-in mode. Instead, agents should explain the available signals the customer can use together:

Jira time tracking fields: Original Estimate, Remaining Estimate, Time Spent
Task dates based on estimates: lets estimate changes affect scheduling
Baselines: helps compare current schedule against a saved plan
Resources module: shows workload and over-allocation visually, including red indicators

Useful references:

What support should emphasize: Standard supports visual monitoring of slippage and overload, but not automated variance rules such as “alert me when actual time exceeds plan by X%.”

5. Address the past-vs-future workload question directly

This is the area most likely to create confusion. Customers may expect that once time is logged, past days will show actual effort while future days continue to show planned workload.

In BigPicture Standard, that automatic switch does not happen.

Past workload is still shown according to the task’s scheduled duration and planned effort distribution
Logged time affects progress and Remaining Estimate
If Remaining Estimate changes and task dates are estimate-based, the end date may shift
That shift can change future distribution indirectly, but it does not rewrite past workload as actuals

Avoid overpromising: Do not tell customers that Standard can show historical actual effort and future planned effort in one automatically blended workload view. That capability is not available as described.

Suggested response structure for agents

Confirm the customer’s edition and desired workflow.
State clearly which requested capabilities are not available in Standard.
Offer supported alternatives: task splitting, Jira time tracking, 7pace, baselines, estimate-based scheduling.
Explain that deviation tracking in Standard is visual and configuration-based, not rule-based.
If the customer needs a tailored setup review, suggest a Product Implementation consultation.

Reusable reply points

BigPicture Standard does not support manual workload contouring within a single task.
BigPicture does not provide native time tracking; actuals should be logged in Jira or through 7pace.
Standard can help compare planning and execution indirectly through estimates, progress, baselines, and workload indicators.
Automatic alert rules for plan-vs-actual deviation are not available in Standard.
The Resources module does not automatically display past dates as actual logged effort and future dates as planned workload.

BigPicture Standard: Resource Planning, Time Tracking, and Workload Visualization Support Explained