NetSuite Project Resource Coverage for Remaining Work
Review NetSuite resource coverage thresholds, task exclusions, Planned Work prerequisites, and steps to refresh and investigate project indicators.
NetSuite's Project Resource Coverage for Remaining Work checks whether assigned resources have enough available hours to finish remaining planned work before task deadlines. It requires Planned Work and excludes overdue, parent, and summary tasks. Use its thresholds and at-risk task drill-down alongside overdue-task reporting, not as a complete project-health verdict.
What Does Project Resource Coverage Check?
Project Resource Coverage for Remaining Work checks whether each assigned resource has sufficient available hours to complete remaining planned work before the task due date. It provides a capacity check alongside indicators that identify time overruns and already-overdue tasks.
The distinction matters operationally: a task can need attention before its deadline passes. Rather than waiting for an overdue warning, project managers can use the coverage indicator to investigate whether assigned resources have enough time left to finish their work.
Resource coverage is one part of Project Indicators, which also covers planning, billing, profitability, time, and expenses. For broader workspace and allocation context, see project management tools for project managers.
How Are Resource Coverage Statuses Defined?
The indicator compares available hours against remaining planned work. Its documented thresholds are:
| Status | Resource coverage |
|---|---|
| Green | Available hours cover remaining work. |
| Yellow | Available hours cover at least 90% but less than 100% of remaining work. |
| Red | Available hours cover less than 90% of remaining work. |
Exactly 90% coverage is yellow; full coverage is green. These boundaries provide a useful reference when reviewing project tasks.
Two exclusions are important:
- Tasks already past their due date are excluded from resource coverage.
- Parent and summary tasks are excluded from resource coverage, Planned vs. Actual Time Overrun, and Overdue Tasks.
Consequently, a green coverage indicator does not establish that a project has no late work. Review Overdue Tasks separately. Similarly, inspect underlying tasks rather than expecting parent or summary tasks to participate in these calculations.
The documentation does not explain the detailed available-hours calculation or how multiple resource results are aggregated. Avoid assuming a particular calendar, allocation, or aggregation formula when interpreting a result.
Where Can You View and Refresh the Indicator?
The Project Management feature must be enabled. Indicators appear in two places:
- The Project Indicators subtab of a project record.
- The Project Indicators portlet on the project dashboard.
Standard project forms include the subtab. For a custom project form, make the subtab visible through form customization. If a user cannot find it, check the form before treating the missing display as a calculation problem.
Each indicator displays a status and message. Yellow and red statuses include an investigation link in Recommended action; green statuses require no action. For resource coverage, select Project Tasks at risk to review tasks with insufficient resource availability.
Planning, resource, and financial indicators update daily. To request a manual update:
- Open the project record in view mode.
- Select Actions > Update Project Indicators.
- Review the Last Update column for each indicator.
Profitability has a separate refresh requirement. With Advanced Project Profitability, use Recalculate Financial Data to refresh profitability data and its related indicators. Update Project Indicators does not refresh that underlying profitability data.
What Must You Check Before Enabling Planned Work?
Resource coverage and Planned vs. Actual Time Overrun both require Planned Work. To enable it, go to Setup > Company > Setup Tasks > Enable Features. Under Projects, check Planned Work, and click Save.
Do not treat this prerequisite as a display-only setting. Enabling Planned Work recalculates all open projects and their plans. Set finished projects to Closed first; otherwise, percent complete, billing, or revenue recognition could change.
Planned Work keeps the plan fixed as actual time is recorded and supports forward or backward scheduling. Its record changes are:
| Field | Behavior with Planned Work |
|---|---|
| Estimated Work | Becomes Calculated Work. |
| Planned Work | Added to project and task records; task planned work rolls up to the project. |
| Calculated Work | Includes planned work plus extra time tracked outside the plan. |
Time recorded outside the plan changes Calculated Work, not Planned Work. Planned Work changes only through manual entry of hours against the project or task. This distinction helps explain why extra actual time does not automatically increase the plan used for comparison.
Before enabling the feature, also review these dependencies:
- Profitability: Planned time entries remain planned rather than becoming actual entries. With Advanced Project Profitability, ensure custom profitability settings do not have Planned Time enabled on the Settings page, to avoid double-counting committed costs.
- Forecast charges: The documentation warns that if you create Forecast Charges for Actual Time Entries without Planned Work enabled, you will not be able to perform that functionality after enabling the feature. Review any workflow using it beforehand.
- Assignment size: There is a 250-entry limit for any single assignment. Include that limit in your review of assignment setup.
How Does Coverage Differ from Other Project Indicators?
Use resource coverage alongside the other indicators, not as a single project-health verdict. The following thresholds help explain why indicators can show different statuses on the same project.
Planning and schedule checks
| Indicator | Green | Yellow | Red | Investigation link |
|---|---|---|---|---|
| Planned vs. Actual Time Overrun | No positive task overrun after rounding | Rounded overrun of 1%–10% for one or more tasks | Rounded overrun above 10% for one or more tasks | Planned Time Overruns |
| Overdue Tasks | Overdue risk score below 3 | Score of 3–5 | Score above 5 | Overdue Tasks |
Planned vs. Actual Time Overrun compares total actual and planned hours for each task. Its drill-down shows planned and actual time entries for affected tasks and resources. Rounding matters: 0.3% rounds to 0%, producing green; 0.5% rounds to 1%, producing yellow.
Overdue Tasks evaluates incomplete tasks past their due dates and links to their task list. The documentation provides score thresholds but does not explain the risk-score formula.
Profitability and billing checks
| Indicator | Requirement and comparison | Green | Yellow | Red | Investigation link |
|---|---|---|---|---|---|
| Project Margin | Job Costing and Project Budgeting or Advanced Project Profitability; total recognized project revenue compared with total project costs | Margin above 10% | Margin of 0%–10% | Negative margin | Project Profitability Report |
| Actual charges have not been invoiced | Charge-Based Billing; actual charges ready for billing | None older than 14 days | At least one older than 14 days | At least one older than 30 days | Unbilled Charges |
These checks answer different questions from resource coverage: how recognized revenue compares with project costs, and whether actual charges ready for billing remain uninvoiced. Their availability depends on the required features and project setup.
Time and expense checks
| Indicator | Requirement or measure | Green | Yellow | Red | Investigation link |
|---|---|---|---|---|---|
| Expense to approve | Expense Reports required | No unapproved expense lines | 1–4 lines | 5 or more lines | Unapproved Expenses |
| Time not tracked | Actual time recorded against planned time | All planned time recorded | 50%–99% recorded | 0%–49% recorded | Missing actual time |
| Time to approve | Time approval enabled | No unapproved time entries | 1–9 entries | More than 9 entries | Unapproved Time Entries |
Expense investigation opens reports containing unapproved lines for the project. Missing-time investigation opens planned time entries to identify resources with missing actual time. Time approval investigation opens unapproved project time entries.
All three calculations cover project activity from project start through the end of the previous week. Current-week time and expenses are excluded until the following week. Week boundaries follow the company's First Day of Week preference; in OneWorld, a subsidiary preference can override it. This is a relevant configuration check for OneWorld multinational and multicompany environments.
Who This Affects
- Project managers: Review resource coverage together with overdue tasks and time overruns; use the at-risk task drill-down to investigate shortages.
- Administrators: Verify Project Management, Planned Work, custom-form visibility, and the consequences of enabling Planned Work across open projects.
- Resource planners: Examine remaining work and assigned-resource availability before task deadlines, rather than relying only on late-task reporting.
- Finance and billing teams: Review profitability settings, forecast-charge dependencies, and the separate financial recalculation process.
- Time and expense approvers: Interpret approval indicators using the previous-week cutoff rather than expecting current-week entries to appear immediately.
Key Takeaways
- Resource coverage checks assigned-resource availability for remaining planned work before task deadlines.
- Coverage of at least 90% but less than 100% is yellow; below 90% is red. Overdue, parent, and summary tasks are excluded.
- Enable Planned Work carefully: it recalculates open projects and has profitability and forecast-charge implications.
- Use Project Tasks at risk and check Last Update before drawing conclusions from a status.
- Resource coverage complements—not replaces—schedule, profitability, billing, time, and expense indicators.
Frequently Asked Questions (4)
What does a yellow or red resource coverage status mean, and are the thresholds inclusive?
Why might a late or parent task not appear in the resource coverage results?
What features and setup changes are required to use Project Resource Coverage for Remaining Work?
How do I refresh resource coverage and investigate tasks with insufficient availability?
Weekly Update History (1)
Expanded Project Indicators to cover additional indicators introduced in 2026.2, including requirements, status thresholds, and drill-down links.
View Oracle DocsWas this article helpful?
More in Projects
- Project Manager Role in NetSuite 2025.2 for Enhanced Project
The Project Manager role in NetSuite 2025.2 enhances project management with predefined permissions for effective task oversight.
- Project Tasks Import from Microsoft Project in NetSuite
Import project tasks from Microsoft Project into NetSuite for improved project management. Explore the requirements and best practices.
- Indirect Cost Allocations Enhancements for Grants in NetSuite
Indirect cost allocations enhancements for grants in NetSuite 2023.2 streamline invoice management and improve user control.
Also from NetSuite 2026.2
- Bank Matching and Reconciliation Enhancements in NetSuite 2026.2
Bank matching and reconciliation pages in NetSuite 2026.2 receive critical UI enhancements for improved transaction management.
- System Notes Enhancement for Reconciliation in NetSuite 2026.2
System notes enhancement tracks GL transaction events in NetSuite 2026.2, improving reconciliation auditing and review.
- SuiteCloud CLI License Acceptance for Automation
Set SUITECLOUD_CLI_ACCEPT_LICENSE=true to suppress the SuiteCloud CLI license prompt during scripted npm installation.
- NetSuite Next: Readiness, Preview, and Ask Oracle
Eligible administrators can request a NetSuite Next preview, set up Ask Oracle, and prepare data, roles, customizations, and navigation.
Advertising
Reach Projects Professionals
Put your product in front of NetSuite experts who work with Projects every day.
Sponsor This Category