Project Budget Settings
Configure and monitor your project's financial settings. Set budgets, define hourly rates for team members, review budget alerts, and customize work schedules that affect burn rate calculations.
Overview
Budget Settings is a Pro feature organized into four sub-tabs accessible from the project settings navigation:
- Allocation: View developer time allocation and costs
- Rates: Configure custom hourly rates per team member
- Alerts: Monitor budget threshold notifications
- Settings: Configure budget values and work schedule
Allocation Tab
Displays a table showing how each team member's time contributes to the project budget.
Developer Allocation Table
Each row shows a developer with the following columns:
- Developer: Name and avatar, with a "Custom" badge if they have a custom hourly rate
- Total Hours: All hours tracked by this developer
- Billable: Hours marked as billable to the client
- Non-Billable: Internal hours not charged to client
- Rate: The developer's hourly rate (default or custom)
- Cost: Total cost calculated from hours × rate
- %: Percentage of total budget consumed by this developer
Footer Totals
The table footer displays:
- Total number of team members
- Combined billable hours across all developers
- Combined non-billable hours
- Total cost for the project
Rates Tab
Manage individual hourly rates for team members. Custom rates override the project's default rate.
Adding a Custom Rate
- Click the Add Rate button in the header
- Select a team member from the dropdown
- Enter their custom hourly rate
- The rate applies to all future time calculations
Rate Display
The header shows the default rate configured in Settings. Team members without custom rates use this default.
Removing a Rate
Click the remove button next to any custom rate to delete it. The team member reverts to using the project's default rate.
Alerts Tab
View system-generated notifications when the budget approaches or exceeds thresholds.
Alert Types
- Warning (amber indicator): Budget has reached the warning threshold percentage
- Critical (red indicator): Budget has exceeded the critical threshold
Alert Information
Each alert displays:
- Alert type with colored indicator
- Threshold percentage that triggered the alert
- Date and time when the alert was triggered
Alerts are generated automatically by the system based on the thresholds configured in Settings.
Settings Tab
Configure the core budget parameters and project work schedule.
Budget Type
Choose between two calculation modes:
Fixed Value Mode
- Enter a total budget amount directly
- The system tracks spending against this fixed amount
Hours × Rate Mode
- Enter an hourly rate and estimated hours
- The system calculates total budget automatically
- Shows calculated budget based on your inputs
Threshold and Controls
- Warning Threshold: Percentage at which warning alerts trigger (default: 70%)
- Auto Block: When enabled, blocks time tracking when budget is exceeded
Work Schedule
Override the workspace default work schedule for this specific project:
Use Workspace Default
- Project uses the workspace's configured working days and hours
- Displays current workspace schedule for reference
Override for This Project
- Toggle to enable project-specific schedule
- Configure working days by clicking day buttons (Mon-Sun)
- Set hours per day for burn rate calculations
- Add project-specific holidays that exclude certain dates from calculations
Saving Changes
Click the Save button in the header to apply all settings changes at once.
How Budget Tracking Works
- Team members log time against project tasks
- Each time entry calculates cost using the member's rate (custom or default)
- Costs accumulate against the project budget
- When thresholds are reached, alerts are generated
- If auto-block is enabled, time tracking stops when budget is exceeded
Requirements
This feature requires a Pro subscription.
Related Features
- Time Tracking - Log hours against tasks
- Billable Time - Review billable hours and costs
- Project Settings - Other project configurations
Budget Planning Best Practices
Estimating Project Budgets
When setting up a new project budget:
- Review historical data: Check similar past projects for actual costs
- Factor in uncertainty: Add 15-20% buffer for unexpected work
- Consider team composition: Different rates affect total budget significantly
- Account for overhead: Meetings, code reviews, and communication take time
Budget Calculation Methods
Choose the right approach for your situation:
| Method | Best For | Pros | Cons |
|---|---|---|---|
| Fixed Value | Firm fixed-price contracts | Simple, clear limit | Less flexible |
| Hours × Rate | Time & materials | Accurate tracking | More complex |
Setting Thresholds
Configure meaningful alert thresholds:
| Phase | Suggested Threshold | Action |
|---|---|---|
| Early warning | 50% | Review progress vs budget burn |
| Warning | 70% (default) | Assess remaining scope |
| Critical | 90% | Escalate, potential overrun |
Managing Team Rates
When to Use Custom Rates
Apply custom rates when:
- Team members have different experience levels
- Contract resources have negotiated rates
- Certain specialists command premium pricing
- Projects have unique billing arrangements
Rate Hierarchy
GitScrum applies rates in this order:
- Custom project rate (if configured for member)
- Default project rate (from Settings tab)
- Workspace default (if no project rate set)
Auditing Rates
Regularly review rates to ensure accuracy:
- Check all custom rates quarterly
- Update for salary changes or role promotions
- Remove rates for departed team members
- Document reasons for rate variations
Budget Alerts Management
Alert Response Protocol
When alerts trigger:
Warning Alert (70%)
- Review remaining tasks vs remaining budget
- Assess if original estimate was accurate
- Identify any scope creep
- Communicate status to stakeholders
- Adjust plan if needed
Critical Alert (90%)
- Pause new work if necessary
- Prioritize remaining budget for critical tasks
- Escalate to project sponsor
- Prepare budget extension request if needed
- Document lessons learned
Preventing Alert Fatigue
If alerts trigger too frequently:
- Review if thresholds are set appropriately
- Check if initial budgets are realistic
- Consider if auto-block is appropriate for your workflow
- Address root causes of budget overruns
Work Schedule Impact on Budgets
How Schedules Affect Calculations
Work schedules influence:
- Burn rate projections: Hours per day × days per week
- Capacity planning: Available hours for the project
- Holiday exclusions: Days not counted in estimates
Project-Specific Schedule Scenarios
| Scenario | Configuration |
|---|---|
| Standard office project | Use workspace defaults |
| Client in different timezone | Override with client hours |
| Weekend support included | Add Saturday/Sunday to working days |
| Reduced hours project | Lower hours per day |
Holiday Management
Add project-specific holidays for:
- Client-specific holidays (different country)
- Planned team absences
- Company-wide events not in workspace calendar
- Project-specific milestones (no work days)
Reporting and Analysis
Budget Health Indicators
Monitor these metrics regularly:
| Metric | Healthy | Warning | Critical |
|---|---|---|---|
| Burn rate vs plan | Within 10% | 10-25% variance | >25% variance |
| Hours remaining | >30% of budget | 10-30% | <10% |
| Cost per task | Consistent | Increasing | Highly variable |
Exporting Budget Data
For external reporting:
- Screenshot or copy the Allocation table
- Export time tracking reports for detailed breakdown
- Use API for automated reporting integration
Troubleshooting Budget Issues
Budget Shows $0
If budget displays zero:
- Navigate to Settings tab
- Ensure budget value or hours × rate is configured
- Click Save to apply settings
- Refresh the page
Rates Not Applying
If time isn't calculating correctly:
- Verify custom rate is saved (check Rates tab)
- Confirm default rate is set in Settings
- Check if time entry is marked billable vs non-billable
- Review time entry timestamps vs rate effective date
Alerts Not Triggering
If expected alerts don't appear:
- Verify thresholds are set (not 0%)
- Check that budget is configured
- Ensure time has been logged against the project
- Refresh the Alerts tab
Auto-Block Considerations
When to Enable Auto-Block
Use auto-block for:
- Strict fixed-price contracts
- Budget caps that cannot be exceeded
- Projects requiring explicit approval for overages
When to Disable Auto-Block
Disable when:
- Budgets are estimates rather than limits
- Team needs flexibility to complete critical work
- Approval process handles overages separately
Team Communication
If auto-block is enabled:
- Notify team of the policy
- Explain how to request budget extension
- Provide alternative tracking for blocked time
- Monitor for blocked entries requiring action