Forecast vs. systems@work

Forecast is well suited for tracking schedules, especially if it is only being controlled by a single department. When it comes to using Forecast in a larger ecosystem with more "cooks in the kitchen" it would be helpful to have the software more easily integrated with other software.

Incentivized

• Assign and allocate resources.
• Identify lean departments and identify areas to increase headcount.
• Manage agile teams.
• Identify bottlenecks in departments or resourcing.

Incentivized

• Not as intuitive as its companion software, Harvest. This software takes longer to learn when on-boarding new staff. It is also difficult to view time notes without needing to physically open them up. This could be improved by expanding the "on hover" functionality. Personally, having spent as little time in workflow software is really important, as it gives me more time to code.
• Because we use this software to plan schedules, items often fall through the cracks. I would like to see some more sophisticated syncing with not only Harvest but also with Asana.
• Lack of integration with Asana. It would be nice to pull data from forecast and display it in Asana. This would be helpful for understanding how much time I have to spend on a project rather than bounce back and forth between web apps.

Incentivized

I have not needed support for Forecast.

Incentivized

I have not used any other scheduling software other than Forecast. The company selected Forecast because it is used in conjunction with Harvest. The pair of web apps can be used to pull detailed data. This is very important to our agency, and making data-driven decisions is exceptionally important to our agency mission.

Incentivized

• Allow departments to run efficiently.
• Quickly identify whether departments need to hire.
• Easily visualize project gaps in resources.

Incentivized