Accurate forecasting is not guesswork. It is the result of pulling the right data into one place, refreshing it on a steady rhythm, and turning it into clear decisions every week. Below is a practical guide to the data that matters most, with light Birdview PSA examples to show how it works in real teams.
📚 Read more: Resource forecasting in project management
Start with real calendars
Your forecast is only as good as your working time. Connect company calendars so regional holidays, working hours, and Paid Time Off (PTO) approvals flow into capacity automatically. When calendars drive the plan, “surprise” shortages stop appearing in the very week you planned to deliver.
Tip: Review next month‘s calendar by role every Friday and slide soft allocations by 2 to 5 days if you see a conflict.
Use HR and skills data
Pull roles, seniority, skills, locations, and internal cost rates from your HR system. Keep a simple skills matrix and certification flags current. This helps you assign the right hours to the right skills and protects margin by matching task complexity to cost.
In Birdview, roles and skills live in profiles, which makes staffing by placeholder fast and consistent.
Convert the sales pipeline into early demand
Do not wait for contracts to start planning. Take deals from your CRM and model provisional demand using their chance to close. If a deal is at 60 percent, plan about 60 percent of the hours in the likely window. As the probability moves up or down, your soft allocations move, not your live schedule. Sales and delivery now look at the same future and adjust together.
Ground estimates in historical actuals
Timesheets and approved expenses show how long work really takes by role and by task type. Use these patterns instead of gut feel. Tie delivery data to Estimate to Complete (ETC) and Estimate at Completion (EAC) so forecasts refresh as time is approved. Drift becomes visible when it starts, not at the month’s end.
In Birdview: approved time updates utilization and refreshes ETC and EAC at task, project, and portfolio levels.
Bring in live project schedules
Top-down hours are not enough. Pull current start and finish windows, dependencies, and milestone risk from each plan. Plan by role first, then assign names when availability is confirmed. This keeps early forecasting separate from hard commitments and makes promises credible.
Example: “Senior architect, 24 hours in week 12” becomes “Alex, 3 hours per day Tue–Thu” once dates are firm.
Include vendor and contractor capacity
If partners carry part of the load, their calendars, notice periods, rate cards, and blackout dates are part of your supply. Track confirmed weeks and lead times the same way you track internal PTO. Late visibility here is one of the fastest ways to lose margin.
Tip: Store vendor capacity as roles with caps per week to avoid silent overbooking.
Add policy guardrails
Set healthy utilization ranges by role so no one sits idle or gets overloaded. Include rules for overtime, onboarding time for new hires, and maximum parallel work. Guardrails make small weekly corrections easy and avoid end-of-month fire drills.
In Birdview: workload views show daily and weekly loads so you can shift a few hours rather than rebuild a plan.
Track uncertainty on purpose
Give each allocation a simple confidence tag: high, medium, or low. Review three horizons every week: 2-4 weeks, 30-60 days, and 90 days. Model a base, fast, and slow path and test each against capacity. You will spot single-role bottlenecks before they become emergencies.
Example: if architects go red in week 10, slide placeholder demand by three days and retest. Small moves now prevent overtime later.
How this looks in Birdview PSA
Birdview brings these sources together without heavy lifting. Calendars feed working hours and holidays into capacity. Roles and skills sync from profiles, and placeholders let you plan by role before names are known. CRM deals can become provisional projects with soft allocations. Capacity and workload views show supply versus demand by role and person. Approved time updates, Estimate to Complete (ETC), and Estimate at Completion (EAC), so finance, PMs, and resource leads act on one version of the truth. Change requests, baselines, and snapshots keep the story auditable. If clients need status, a client portal, and scheduled reports, remove manual slide work.
Bottom line
Great forecasts mix real calendars, trusted HR and skills data, probability-weighted pipeline, historical actuals, live schedules, and vendor capacity, all tied to PSA financials. When these sources refresh on a routine rhythm, forecasting becomes calm, staffing gets faster, and margins stay healthy.
