# How do I write entry and exit conditions?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Press "Main menu", choose "Standards", choose the process, type the condition, press "Add entry condition" or "Add exit condition", type its tag, press "Save".

## Before you start

You need to be signed in to GilbApp on a computer, with a process in a vault you can write to, such as [your own vault](http://support.gilb.com/help/how-do-i-create-my-first-vault); [the answer on writing a new standard](http://support.gilb.com/help/how-do-i-write-a-new-standard) shows how to make one. The pictures show a made-up person on a test site; your screen shows your own name and address.

## Steps

1. Press "Main menu" at the top left and choose "Standards".

   Press "Main menu", next to your profile picture at the top left, and under "YOUR SECTIONS" choose "Standards". The button shows the name of the section you are in, such as "Vaults".

   A panel headed "GO TO" opens; "Standards" reads "Processes, rules, templates and checklists." "Standards" opens on the vault you picked in "Vaults", or on your own vault if you picked none; a vault is the place where a person or a group keeps their records. It opens on the tab "Processes", with "Process" chosen in the row under the tabs. A process is a standard that holds work: entry conditions, steps in order, and exit conditions; a standard is a written procedure, rule set, form or other guide that people and agents follow as they work. On the right, "VAULT" changes the vault, "STANDARDS GROUP" shows only the standards of one group, and "+ New group", shown only where you may write in the vault, makes a group; you need none of them here.

   ![GilbApp with the "GO TO" panel open, with "Standards" under "YOUR SECTIONS" outlined in orange.](http://support.gilb.com/help/media/2f7771842dd46b46.png)
   What you see: The panel headed "GO TO" covers the screen. In the left column under "YOUR SECTIONS", the row "Standards" with the line "Processes, rules, templates and checklists." is outlined. Press it to open the Standards screen.
2. Choose the process in the list.

   Click the process's row in the list. The process opens in the middle, with the cards "Entry conditions", the steps and "Exit conditions", from top to bottom.

   Each row shows the process's name and, under it, the last part of its address. If the list is long, type a word of the name in the box under "SEARCH PROCESSES". "ProcessCard", beside "Process", lists process cards, and "+ New Process" makes a new process; [the answer on writing a new standard](http://support.gilb.com/help/how-do-i-write-a-new-standard) shows it. The other tabs, such as "Rules", hold other kinds of standard, and "ⓘ" beside the heading says what a process is. "← All processes", at the top of an open process, brings the list back.

   ![The Standards screen on the tab Processes, with the row of the process Open the bakery outlined in orange.](http://support.gilb.com/help/media/7b57e69e8d3215cb.png)
   What you see: In the middle, in the list of processes, the row Open the bakery is outlined. Press it to open the process with its cards "Entry conditions", "Steps" and "Exit conditions".
3. Type the condition in "NEW ENTRY CONDITION" and press "Add entry condition".

   Under "Entry conditions", type what must be true before the process may start in the box that shows "What must hold before this process opens", and press "Add entry condition". GilbApp adds the condition at the end of the list and opens "Edit entry condition" on the right.

   Return in the box does the same as the button. The button is grey while the box is empty and reads "Adding…" while it works. The new condition shows "tag not assigned" and "MANUAL"; "MANUAL" means a person decides whether it holds, and GilbApp never tests it. If GilbApp cannot add it, a red box above the process says "The entry condition is not confirmed." and why; for someone who may only read the vault the reason starts "You do not have write access to this record."

   ![The process Open the bakery open with Two bakers are in. typed under New entry condition and the button "Add entry condition" outlined in orange.](http://support.gilb.com/help/media/e9a1e64c1bfae745.png)
   What you see: In the card "Entry conditions", the box under "NEW ENTRY CONDITION" holds Two bakers are in. The outlined button "Add entry condition" is to its right. Press it to add the condition.
4. Type a tag in "TAG" and press "Save".

   In "Edit entry condition", type the condition's tag in "TAG", such as Bakery.Open.Entry.Staffed, and press "Save". A tag is the condition's short name, unique in the vault: the process's tag, then Entry, then one keyword, joined by dots.

   "TITLE" holds a short name shown in bold before the text, and "TEXT" the condition itself; you may change either here. "HANDS OFF TO", "ADD A LINK" and "LOOK UP" link the condition to another standard; [the answer on linking standards with hand-offs](http://support.gilb.com/help/how-do-i-link-standards-with-hand-offs) shows how. "Save" closes the pane, and the condition shows its tag. "Cancel" or "✕" closes it without what you changed here; the condition stays. A saved tag cannot be typed over: "Clear tag" empties it, and after "Save" you may type another. In the Kai-Zen method a tag never changes once it is written, and you look a tag up before you write it, because a vault does not check a condition's tag for you.

   ![The right pane Edit entry condition with Bakery.Open.Entry.Staffed typed in the box under "TAG", which is outlined in orange.](http://support.gilb.com/help/media/7420d776538c3bdb.png)
   What you see: The new condition shows in the card with "tag not assigned" and "MANUAL". On the right, the pane "Edit entry condition" is open; the box under "TAG" holds Bakery.Open.Entry.Staffed and is outlined. Then press "Save" lower in the pane.
5. Type the condition in "NEW EXIT CONDITION" and press "Add exit condition".

   Under "Exit conditions", below the steps, type what must be true before the process may finish in the box that shows "What must hold before it closes", and press "Add exit condition". "Edit exit condition" opens on the right.

   In the Kai-Zen method an exit condition says what is done and hands back, such as: Shop open → hand back to the step that handed off to you; it continues with its next step. The button, its grey state and "Adding…" work as for an entry condition, and a failure says "The exit condition is not confirmed." with the reason.

   ![The card Exit conditions under the steps, with the exit condition typed in the box and the button "Add exit condition" outlined in orange.](http://support.gilb.com/help/media/1fe53f3260052f65.png)
   What you see: Lower on the page, in the card "Exit conditions", the box under "NEW EXIT CONDITION" holds the typed exit text, and the outlined button "Add exit condition" is to its right. Press it. Above, the entry condition now shows its tag.
6. Type its tag in "TAG" and press "Save".

   In "Edit exit condition", type the tag in "TAG", such as Bakery.Open.Exit.ShopOpen, and press "Save". It is the process's tag, then Exit, then one keyword.

   The pane has the same boxes and buttons as in step 4. To change a condition later, click its text in the list: the same pane opens. To change the order of the conditions in a list, drag a condition by its tag, at the left of its row, up or down; GilbApp saves the new order at once.

   ![The right pane Edit exit condition with Bakery.Open.Exit.ShopOpen typed in the box under "TAG", which is outlined in orange.](http://support.gilb.com/help/media/b4fedd5c1381575f.png)
   What you see: On the right, the pane "Edit exit condition" is open. The box under "TAG" holds Bakery.Open.Exit.ShopOpen and is outlined. The new exit condition still shows "tag not assigned" in the card. Press "Save" lower in the pane.
7. To delete a condition, press "🗑 Delete condition".

   Click the condition's text in its list, and in its edit pane press "🗑 Delete condition" at the foot. Nothing is removed yet: GilbApp first asks whether to remove that condition from the entry conditions, or the exit conditions.

   The question also says "Only this condition is removed. The process is not deleted and no other condition is touched." "Keep condition" closes the question and removes nothing.

   ![The right pane Edit entry condition with the button "🗑 Delete condition" at its foot outlined in orange.](http://support.gilb.com/help/media/73326f2785dc73c8.png)
   What you see: The entry condition Two bakers are in. is chosen and its pane "Edit entry condition" is open on the right. At the foot of the pane, under "Cancel" and "Save", the button "Delete condition" with the bin sign is outlined. Press it.
8. Press "Confirm delete".

   Press "Confirm delete". It reads "Removing…" while it works; then the pane closes and the condition is gone from the list.

   If GilbApp cannot confirm the removal, the pane stays open and says why. The question also says the En/Ex numbers, such as En2, are recomputed; GilbApp shows no such numbers, so nothing else in the list changes. GilbApp has no button to bring a deleted condition back; to have it again, add it again.

   ![The right pane with the question whether to remove the condition and the button "Confirm delete" outlined in orange.](http://support.gilb.com/help/media/0de5a5be0818af8d.png)
   What you see: At the foot of the right pane a box asks "Remove Two bakers are in. from the entry conditions?" and says only this condition is removed. The outlined button "Confirm delete" is next to "Keep condition". Press "Confirm delete".

## Deeper

In the Kai-Zen method every process has entry conditions and exit conditions. A process starts only when its entry conditions are true, and it hands back when its exit conditions are true: when another standard handed off to it, that standard goes on with its next step. Every condition gets a tag that is unique in its vault.

A step can show conditions of its own under its text; GilbApp shows them, but lets you add, change and delete only the process's own conditions. The other tabs, such as "Rules" and "Procedures", have no entry or exit conditions to add.

GilbPlatform lets only someone who may write the process add, change or delete its conditions, and refuses anyone else. In the Kai-Zen method whoever holds write access to the vault a standard is kept in may change it, and an agent changes a standard only with the go of such a person.

This answer is written for a computer screen. In a window narrower than 840 pixels, such as a phone, the side panes are hidden and the right pane is "Detail" in the bar at the bottom.

Source: Re-checked 2026-11-11: live GilbApp is now ebd9415e7a90de8c289eaa7bb02f40c8ee80cf79 \(https://gilb.com/app/version.json\) and GilbPlatform 498d29a0dec9a15d167f4b6b5d731382a6bcede0 \(https://id.gilb.com/version\). the diff from af0f04ee to ebd9415e touches no file this page cites \(src/components/process, RightRegion.tsx, gilbAppMenuRows.ts, the standards libs unchanged; processHooks.ts, records.ts and AppShell.tsx change only request headers and a palette note\); the diff from 4d008a55 to 498d29a0 changes sign-in, DPoP and grant slices, not the write gate or deletes. Line numbers above hold at ebd9415e. GilbApp af0f04ee838a4d55887d2ff1f72edd49a4ff7ca0 \(https://gilb.com/app/version.json read 2026-11-10, buildTime 2026-11-09.522Z, dirty false\); code from the unpack \(no checkout\). GilbPlatform 4d008a55367a6e7453920c463a8923df37de62e9 \(https://id.gilb.com/version read 2026-11-10\). Step 1: shell/gilbAppMenuRows.ts:219-231 \("Standards", "Processes, rules, templates and checklists."\); AppShell.tsx:496 \(readVault = selectedVault ?? landingVault\), :658 \(default tab processes\); standardsTabs.ts:9-24 \(tab labels\); standardKinds.ts:108-112 and :206-210 \(kinds Process, ProcessCard; default process\); StandardsControls.tsx \("Vault", "Standards group" in CSS capitals, "+ New group" only with write, AppShell.tsx:529-545\). Step 2: StandardsSection.tsx:427-447 \(row: name, id-tail, arrow\), :547-584 \("Search processes" CSS capitals, "+ New Process"\), :838-841 \("← All processes"\); ProcessViewer.tsx:2029-2059, :2061-2165, :2182-2213 \(Entry conditions, steps, Exit conditions, top to bottom\). Step 3: ProcessViewer.tsx:1547-1617 \("NEW ENTRY CONDITION" CSS capitals, placeholder "What must hold before this process opens", "Add entry condition", Enter submits, disabled while blank, "Adding…"\); processHooks.ts:369-412 and processTypes.ts:562-568 \(appends {op: manual, text}\); StandardsSection.tsx:1147-1155 \(edit pane opens on the new condition\); ProcessViewer.tsx:446-500 \("tag not assigned", chip "manual" CSS capitals, title "A human gate — rendered, never evaluated by the viewer"\); StandardsSection.tsx:408-421 \("The entry condition is not confirmed."\); records.ts:187-200 \("You do not have write access to this record."\); Base routes.ts:822-827 \(write needs a write grant, 403\). Step 4: ConditionEditPane.tsx:186 \("Edit entry condition"\), :203-210 \(✕ Close edit pane\), :213-274 \(Title, Tag, Text in CSS capitals; tag read-only once assigned, "Clear tag"\), :276-289 and HandoffLookup.tsx:286-365 \("Hands off to", "Add a link", "Look up"\), :297-313 \(Cancel, Save, "Saving…"\); RightRegion.tsx:172-180 \(Save and Cancel clear the pane\). Step 5: ProcessViewer.tsx:1559-1603 \("New exit condition", "What must hold before it closes", "Add exit condition"\); StandardsSection.tsx:806-807 \("exit condition"\). Step 6: ProcessViewer.tsx:468-486 and StandardsSection.tsx:994-1015 \(drag the tag pill; one PATCH\). Steps 7-8: ConditionEditPane.tsx:327-378 \("🗑 Delete condition", question, "Only this condition is removed. The process is not deleted and no other condition is touched.", En/Ex sentence, "Keep condition", "Confirm delete", "Removing…"\), :176-184 \(pane closes on success, stays on refusal\); ProcessViewer.tsx:596-600 \(C-COND-POS: no En/Ex numbers drawn\). Deeper: ProcessViewer.tsx:1315-1328 \(step conditions read-only\); RulesTab.tsx:816-818, ProceduresTab.tsx:758, PoliciesTab.tsx:701, ChecklistsTab.tsx:567, TemplatesTab.tsx:557 \(condition writers withheld\); StandardsSection.tsx:1079-1091 and :1130-1134 \(no client gate; GilbPlatform refuses\). Standards \(2026-11-10, all 200\): Agent.Standard.Type.Process \("A Process holds work, with entry conditions, steps, and exit conditions. It starts only when its entry is true, and it hands back when its exit is true."\), .Type.Procedure \("It has no entry or exit conditions."\); GilbPlatform.StandardRules.EntryExit, .HandOff \(child's exit wording\), .Tag, .Owner; Kai-Zen.TagRules.Condition \(&lt;Process\>.Entry.&lt;Keyword\>\), .Unique \("A GilbPlatform vault refuses a copy but does not check conditions"\), .Frozen; GilbPlatform.ChangeStandard Entry.Asked / Exit.Done as live examples. GilbVeda public read 2026-11-10: a:entryCondition, a:exitCondition.
