FAQ

Short answers to the questions that come up most often about workspaces, gates, plans and integrations.

Workspace and accounts

Can I move a project between workspaces?

No. Everything belongs to exactly one team workspace, and there is no transfer. If a colleague signed up separately by mistake, the fix is to recreate the work in the right workspace and abandon the duplicate — ideally before much has been built in it.

Can I restrict who sees a project?

No. Anyone in the workspace can see every project in it. cadence. has two roles — admin and user — and no per-project permissions. Work that must be invisible to the rest of the team needs its own workspace. See team and roles.

Someone left. What happens to their work?

Their tasks, comments and approvals stay exactly as they are — removing a person does not rewrite history. Reassign their open tasks, and revoke any API keys they created, since keys attribute actions to their creator.

Phases and gates

Can I complete a phase with criteria outstanding?

Not while any criterion is incomplete. That is the one hard rule in the product. If a criterion is met but with a caveat, mark it conditionally passed — it unblocks the gate while keeping the caveat attached to the phase. See gate criteria.

Can I un-complete a phase?

Not in one action. You can set the status back manually, but the next phase has already started and keeps its start timestamp. Read the blocking list before completing.

Do I have to use gates on every project?

A phase with no criteria completes freely, so you can run a project as plain phases. But that is most of the reason to use cadence. at all — if none of your projects have decision points, a simpler tool will serve you better.

Why is this phase amber when everything looks fine?

Amber means at risk, and the reasons are on the hover: unmet gate criteria, overdue tasks, critical work with nobody on it, or more work left than the deadline allows. The signal reads the data rather than the room, so it flags the two tasks nobody has looked at since the last standup. See gate readiness.

Can I change how gate readiness is scored?

No, by design. The weights and thresholds are identical for every project in every workspace, so a score means the same thing across the portfolio. A tuneable risk score is a score that gets tuned until everything is green.

Can phases run in parallel?

Not as a first-class concept. Phases are an ordered sequence and one is current at a time. Parallel workstreams are modelled as tasks within a phase, which is usually what teams mean anyway.

Tasks

Why is a completed task not moving the gate?

Because tasks do not control progression — criteria do. If finishing a task genuinely is a gate condition, add it as a criterion too. See core concepts.

Can a task have more than one assignee?

No. One task, one owner. Work that genuinely needs two owners is two tasks.

What is the difference between a dependency and a blocked status?

A dependency is a planned constraint; blocked means work has actually stopped. A task can have dependencies and be perfectly on track, and a task with no dependencies can be blocked by something outside cadence. entirely. See dependencies.

Templates

Does editing a template change existing projects?

No. Projects are copies, taken at creation. Edit a template freely — nothing in flight moves. See templates are copies, not links.

Why did my template's tasks come out worded differently?

Because the project had a description. cadence. rewrites template task titles and descriptions to fit the specific project, preserving order and count. Create the project without a description if you want the template's exact wording.

Plans and billing

What do I lose on the free plan?

Nothing in the methodology — phases, gates, criteria, dependencies, templates, tags, portfolio dashboards and the AI features all work. Free is capped at 2 templates, 10 projects and 5 members, and has no REST API, webhooks, MCP or agents. See plans and limits.

FAQ