Working hours per week
Last updated: July 20, 2026
Configure the working hours per week on each project in order to get increase the accuracy of your forecasting. The default value will be 40-hrs per week, but if your projects operate on a 50 or 60 hr work week, you can easily make that change on the project or account wide.
Key capabilities:
Set a custom hours-per-week value on any individual project
Configure an account-wide default that all new projects inherit
See accurate role counts, cost projections, and workforce spend across all forecasting surfaces
Override the account default on a per-project basis at any time
Eligibility/Prerequisites
This feature is available to all accounts. However, the below permissions are required in order to manage the fields:
Manage Settings: Required to edit the account-wide default
Manage Projects: Required to edit the working hours per week on a specific project
How to Use
Set the Account-Wide Default
Navigate to Settings in the top navigation
Select Projects from the left panel
Go to System Fields
Locate Hours Per Week and edit the default value
Save your changes
Note: Updating the account-wide default will impact all projects currently using the default value. Projects with a custom override are not affected.
Set Hours Per Week on a Specific Project
Open the project profile
Navigate to the Details tab
Locate the Forecast & Budget section
Edit the Working Hours Per Week field
Save your changes
The project-level value overrides the account-wide default for that project only.
What Changes
Once the working hours per week is updated on a project, the following surfaces recalculate automatically:
Surface | What changes |
|---|---|
Project → Forecast → Estimated demand | Role counts use the project's configured hours/week instead of 40 |
Project → Forecast → Planned demand | Salary role hours reflect the correct hours/week |
Project → Spend | Salary role cost per interval recalculates based on configured hours/week |
Reports → Workforce Spend | Account-level spend rolls up using each project's hours/week |
Reports → Estimation Gap | Estimated demand is calculated using each project's hours/week |
Common Workflows
Projects on a 50- or 60-hour schedule: If your contract specifies a non-standard work week, set the working hours per week on the project to match. Role counts in the Forecast tab and cost projections in the Spend tab will immediately reflect the correct baseline.
Consistent schedule across your portfolio: Set an account-wide default in Settings to reduce per-project setup. All new projects will inherit the value automatically, and you can still override it on individual projects where the schedule differs.
Mid-project schedule change: If the working hours per week changes after a project is underway, update the field on the project. All intervals — including historical ones — will recalculate using the new value.
Common Questions
Q: What was Bridgit using before this feature?
All projects used a hardcoded 40-hour work week for every calculation. This is still the default, and existing projects will continue to use 40 hours unless explicitly changed.
Q: Does this affect hourly roles?
No. Hourly roles already define working hours through their working schedule, so the working hours per week setting does not apply to them.
Q: If I update the account-wide default, does it change my existing projects?
It will update all projects currently using the account default. Projects where you've set a custom override will not be affected.
Q: Can hours per week be set differently by phase or role type?
Not at this time. The setting applies at the project level. Phase-level overrides and role-type-specific hours are being considered for future releases.
Q: Where can I see what hours per week a project is using?
The Working Hours Per Week field is visible on the Details tab of any project under the Forecast & Budget section.