Consequent collapses decades of ambiguity in favor of declarative clarity. A next-generation tool built on precision, uniformity, and shared understanding.
We have aimed to eliminate hidden meanings and implicit assumptions. Primarily by eliminating some of the more rarely used, complex constraint types, and reducing the divergent behaviors of dependencies (e.g. into a parent task versus into an activity), we have removed many avenues of mistakes and counterproductive complexity. Every concept is explicit, auditable, and communicable.
We have removed start dates. Altogether. Action starts on the project start date, and the schedule is calculated from either a dependency constraint, or an optional SNET.
"Finish No Later Than" can be used everywhere as safeguards, but are non-blocking. The engine will highlight and enumerate any violations, so you can adjust the plan.
The hour is the fundamental unit of measurement. Anything less is noise. Consequent has no fractions. Everything is expressed in days and hours (or weeks, months, years, of course). No more fractions and "0.999" remainders.
Projects can be configured to disallow lag completely, enforcing explicit temporal activities. There are strong opinions on this, and we decided to allow teams to express their world view.
Built for engineering-minded project managers and teams who demand deterministic scheduling and the clarity of always-explicit constraints.
Consequent is a functional solver with a fluid, ultra-fast engine and user interface. Instead of blocking updates, it will highlight and explain why your constraints are violated, allowing you to manage the plan as circumstances evolve.
Microsoft Project hides logic behind "intelligent" heuristics. Consequent exposes it. Build meaningful schedules that are clean and auditable, without the black-box magic.
Stop fighting with "Start No Earlier Than" violations. Consequent is built for engineers who think in clear dependencies and calculated critical paths.
Rigid waterfall tools break under agile iterations. Consequent acts as the stable backbone for fluid development cycles, adapting without breaking.
We're returning to valuable traditions while collapsing subtle ambiguities. With adjustments in nomenclature, data models, and a reduction in concepts rather than more complex capabilities, we believe we can meaningfully improve the project management experience.
We have seen a growing emphasis on determinism, completeness, and functional orientation in software engineering. We develop Consequent with a strong focus on these principles, and believe they also inform how the product is designed to be used.
Task groups can be predecessors but not successors. Tasks can be both. Simple, logical, and impossible to misinterpret.
We are providing options for increased clarity. For example, lags can be disallowed, requiring plan segments for wait periods, for example. Slightly more verbose, but more explicit, and we've attempted to compensante with an ultra-fluid UI to facilidade aggregations. But if your team likes lags, you can turn them on in Settings! You'll just have to enter descriptions!
The Gantt chart is a useful tool for visualizing dependencies and critical paths. We're innovating with a whole-screen presentation, breaking the decades-old pattern of the split screen.
Join teams who value precision, clarity, and semantic uniformity in their planning process.