Project or resource manager
Plan dates around dependencies and real team capacity
FlowOS shows planning evidence; it does not silently rewrite a manager’s schedule. Capacity compares planned effort with working shifts. Timeline dependencies prevent impossible order. Calendar combines deadlines with approved shared sources.
Before you start
- A private project with estimated tasks.
- Working shifts and project membership defined.
#Review capacity as a warning system
- Define recurring shifts for project members.
- Estimate tasks and create allocations.
- Open the capacity view and inspect overload warnings.
- Resolve conflicts by changing scope, owner, effort, or dates with the manager.
#Add only valid same-project dependencies
Use finish-to-start relationships when one task truly cannot begin before another ends. Keep the graph acyclic. FlowOS rejects a successor scheduled before its predecessor finishes; it does not automatically move every downstream date.
#Use calendars as a shared view, not a second source of truth
Configure business hours and approved shared calendar sources. Imported events are overlays; task dates remain governed by task and timeline controls. Check provider sync status before relying on an external event.
#Common mistakes
- Treating a warning as automatic resource leveling.
- Creating cross-project or circular dependencies.
- Assuming an imported calendar event changes task ownership.
#Verify the result
- Shifts and allocations use the same planning period.
- Dependency order is valid and acyclic.
- Overload decisions are recorded.
- External calendar sync status is visible.