# Why does my plan need Constraints?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Constraints are limits your plan must keep, such as a budget, a date or a law; the plan drops every way that breaks one.

## Deeper

A constraint is a requirement that restricts a system, with a penalty or a loss if it is not respected. In your plan it is something the app must do, or a way it must be built, because a person you name requires it, such as you as the owner: a "Function Constraint" or a "Solution Constraint". That person is its "Authority".

What they do for your app: they put your limits in the plan, and when the ways of building are compared, every way that breaks one is out. Limits on money, time and how good things must be are constraints too, written as numbers: the worst number you can live with on a Value, a goal for how well your app must do something, and the "Budget" on what the work may use. The answer [How do I write a Resource and set the project's currency?](http://support.gilb.com/help/how-do-i-write-a-resource-and-set-the-projects-currency) shows money.

Use as few as you can. Each one shuts out other ways of doing the work, so a constraint is written only when a real, named person requires it, not a role or a group.

A made-up example, a booking app for a small bike-repair shop: customers' phone numbers must never be shown to other customers, required by you as the owner, is a Function Constraint. Payments must go through the card machine the shop already has, also required by you, is a Solution Constraint.

Every plan for software holds one constraint from the start: reuse the app's existing code, buttons and ways of doing things, and build something new only when nothing fits. You, the owner, are its "Authority".

How many? As few as possible. Tell Kai-Zen, the planning agent, your limits in your own words: money, time, rules you must follow, and anything the app must or must not use. Kai-Zen writes each limit where it belongs, a constraint only where a named person requires it.

To write one yourself, see the answer [How do I write a Constraint in my plan?](http://support.gilb.com/help/how-do-i-write-a-constraint-in-my-plan) The answer [How do I release a Constraint?](http://support.gilb.com/help/how-do-i-release-a-constraint) shows what to do when a limit no longer applies, and [Do I have to follow rules such as GDPR or app store rules from the start?](http://support.gilb.com/help/do-i-have-to-follow-rules-such-as-gdpr-or-app-store-rules-from-the-start) covers laws.

This answer is written for a computer screen.

Source: Kai-Zen standards: Kai-Zen.ConstraintRules \(Kinds, MustDo, Authority, Avoid, Options, Reuse, Level\); Kai-Zen.New.Setup. GilbVeda t:Constraint. Live help pages, shared: What is a Constraint? \("A constraint is a requirement that restricts a system, with a penalty or a loss if it is not respected."\); How do I write a Constraint in my plan? \("Function Constraint", "Solution Constraint", "Authority" must be a person, not a role or a group; avoid constraints where you can; the worst number you can live with\); How do I write a Resource and set the project's currency? \("Budget"\); How do I describe my idea so the AI understands it? \(limits: money, time, rules, must or must not use\); How do I release a Constraint?; Do I have to follow rules such as GDPR or app store rules from the start?.
