The buyer decision
Judge capacity product fit for working schedules and project states, excluding generic vendor ranking and leave administration.
Criteria & methodologyA capacity product should represent the buyer’s actual availability and project states. A schedule that assumes everyone works identical hours can give a misleading view of the commitments the team can accept.
Paused work also needs a clear meaning. Removing a project from an active list is not automatically the same action as removing its allocations or retaining its history.
Turn the requirement into observable behavior
| Requirement | Evidence to request |
|---|---|
| Part-time participant | Intended working days and hours |
| Temporary availability change | Defined effect on displayed capacity |
| Paused project | Meaning of existing and future commitments |
| Completed work retained | Historical record remains understandable |
| Project reactivated | Deliberate restoration of relevant planning state |
These criteria are an editorial framework, not a benchmark or assurance that a product predicts delivery.
A useful documented distinction
Float’s capacity product page describes full-time and part-time working schedules. Treat broader outcome language as supplier claims and inspect the proposed configuration.
Its archive documentation distinguishes archiving from deletion. Archived projects retain read-only history and existing allocations remain visible on the Schedule. Do not assume archiving automatically removes all planned demand.
That example shows why a buyer should ask about project-state semantics rather than check a box labeled Archive.
Evaluate the display under changed conditions
Use a fictional part-time participant with commitments on several projects. Ask the supplier to show availability and explain how working hours enter the view.
Pause one project without deleting it. Inspect the remaining allocations and what the schedule communicates to the planner. If an allocation should no longer represent a commitment, ask how the intended process changes it.
Reactivate the project and compare current commitments with retained history. Record the actual behavior and edition. The publication has not carried out this scenario.
Accept a product only with an understandable model
The requirement is not that every state updates automatically. A documented manual decision can be proportionate if the planner understands it and can maintain the records.
Choose the product or configuration that represents the actual working schedule and project state. Keep unresolved semantics visible in the decision rather than treating a complete-looking calendar as proof.
Browse the Resource Planning hub and Float–Runn comparison for related product choices.