# How do I write a Resource and set the project's currency?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Press "Main menu", choose "Plan", press "＋ New", choose "Development Resource", type a tag \(its short name\), press "Create", type the currency in "Unit".

## Before you start

You need to be [signed in to GilbApp](http://support.gilb.com/help/how-do-i-sign-in-to-gilbapp) on a computer, with a vault you can write to, such as [your own vault](http://support.gilb.com/help/how-do-i-create-my-first-vault). 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 "Plan".

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

   A panel headed "GO TO" opens; "Plan" reads "Your Kai-Zen plan: Functions, Values, Development Resources and Solutions." You can also press the "Plan" button on the card of a vault \(the place where a person or a group keeps their records\) in "Vaults". The "Plan" screen lists your plan records and has the views "Grid", "Graph", "Both" and "Card".

   ![GilbApp with the "GO TO" panel open, and "Plan" under "YOUR SECTIONS" outlined in orange.](http://support.gilb.com/help/media/19263b830249232b.png)
   What you see: In the GO TO panel that opens from "Main menu" at the top left, look under YOUR SECTIONS on the left. The outlined row is "Plan", with the line "Your Kai-Zen plan: Functions, Values, Development Resources and Solutions." Press it to open the Plan screen.
2. Press "＋ New".

   Press "＋ New" at the top right of the "Plan" screen. With no record selected, the type dialog opens at once.

   If a record is selected, "New" first offers five choices: "Create a record and link it to" the selected record, "Link" the selected record "to a record that already exists", "Create a record on its own", "Create a virtual folder" and "Upload a file". Choose "Create a record on its own". A new Development Resource needs nothing else; the others make a record joined to the selected one, link two records that already exist, make a virtual folder or upload a file. In "Plan", the "GO TO" panel also has "New plan record", which does the same.

   ![The "Plan" screen with the list of plan records and no record selected, with the "＋ New" button at the top right outlined in orange.](http://support.gilb.com/help/media/8656fb734fb9d694.png)
   What you see: Look at the top right of the Plan screen, just left of the Details pane. The outlined button is "＋ New". Press it; with no record selected a dialog headed "New function" opens with its "TYPE" list.
3. Under "TYPE", choose "Development Resource".

   In the list under "TYPE", choose "Development Resource". A Development Resource is something the work uses up, such as money, time or people.

   The dialog opens headed "New function" with "Function" chosen; after you choose "Development Resource" it is headed "New development resource". The chosen type then shows under "TYPE" with a "DEFINITION" read from GilbVeda, the shared list of terms; it can be long, and you need not read it. "×" beside the type brings the list back. A search box above the "TYPE" list narrows it as you type, and "Close" at the top of the dialog closes it like "Cancel"; you need neither. "↗" at the end of a row shows what GilbVeda says about that type; you do not need it. "Cancel" closes the dialog without making anything. Where it shows "Back" instead, "Back" returns you to the five choices.

   ![The new-record dialog headed "New function" with the list under "TYPE", with the "Development Resource" option outlined in orange.](http://support.gilb.com/help/media/1a5d7aa823142ad2.png)
   What you see: In the "New function" dialog, the list under "TYPE" is scrolled to show "Development Resource", marked "t:Resource" at the right. That row is outlined. Click it.
4. Type a tag in "TAG" and press "Create".

   Type a tag in "TAG", check "CREATE IN", and press "Create". A tag is the short name of a plan record: an area, a dot and a keyword, such as Cost.Monthly.

   The box shows "Area.Keyword, e.g. Usability.Learn" until you type. With the tag empty the screen says "Give it a Tag first: a Plan card is named by its Tag." Under "CREATE IN", choose the vault where it will live; vaults you can only read say "read only, you cannot create there". If the tag is already used in that vault, the screen says "is already used in this vault. Pick another." If the vault is not the one you are viewing, the dialog stays open and says the record was made there, "not in the vault you are viewing. It is not drawn here.", with an "Open it" button.

   ![The dialog headed "New development resource" with the type's "DEFINITION" and a made-up tag typed under "TAG", and the "Create" button at the bottom right outlined in orange.](http://support.gilb.com/help/media/5931b5de18890c6a.png)
   What you see: The dialog is now headed "New development resource", with "Development Resource" and its "DEFINITION" under "TYPE". "TAG" holds your tag. At the bottom right, the outlined button is "Create". Press it.
5. Under "Scale", type the currency in "Unit".

   Under "Scale", in the "Unit" box that shows "e.g. minutes", type the currency the project counts money in, such as €. The "Scale" is the ruler the Resource is counted on, and the "Unit" is what you count in; for time, type hours instead.

   After "Create", the new Development Resource opens in edit mode: "Done" is at the top right of the card and the card says "Editing. Changes save as you leave a field." There is no Save button. If you come back later, click the Development Resource in the list and press "Edit". Then type the "Rate", which is per what \(the box shows "e.g. per \[Task\]"\), such as per month, and the "Context", where counting starts and stops \("from: …; until: …"\). "Better" already shows "Lower is better", as the method wants for a cost. A "Source" box can name who said it. "Endpoint", "Qualifiers" and "Illustration" are optional; Deeper, below the steps, says what they are. None is needed to save.

   ![The new Development Resource card in edit mode with the empty "Scale" boxes and "Lower is better" under "Better", and the "Unit" box showing "e.g. minutes" outlined in orange.](http://support.gilb.com/help/media/f4c1552d086e9a3c.png)
   What you see: On the new card, the line under "RESOURCE" shows "Level: Business". In the "Scale" part, the outlined box under "Unit" shows "e.g. minutes". Type your currency there, for example €. "Better" shows "Lower is better".
6. Under "Levels", type a number in "Status", "Tolerable" and "Budget".

   Under "Levels", type a number in the box on each of the "Status", "Tolerable" and "Budget" rows. "Status" is what is used up so far, and "Budget" is the most you plan to use.

   "Tolerable" is the overspend limit; with "Lower is better", "Budget" is no higher than "Tolerable". Example, in € per month: "Status" 4500, "Tolerable" 6000, "Budget" 5000. Each row also has a date box \(when the number holds\), a "Condition, Enter" box \(a condition for it; press Enter to add it\), a "Source" box \(who said it\), "Note, e.g. estimate", "⧉" \(copies the row's qualifiers to a new level\) and "×" \(removes the row\); all are optional. A row with nothing in it is not saved. Outside edit mode a blank line shows "Add value"; press it first. Give each one plain number: until then, a Solution's cost here shows "No % yet:" and "needs one Status, one Tolerable and one Budget." "+ Level" and the buttons beside it add more levels; Deeper says how.

   ![The Development Resource card scrolled to "Levels", with rows "Status", "Tolerable" and "Budget", and the number box on the "Status" row outlined in orange.](http://support.gilb.com/help/media/7657be0058c10128.png)
   What you see: Scroll down to "Levels". The rows start with "Status", "Tolerable" and "Budget", and the buttons beside "+ Level" include "Budget". The outlined box is the number box on the "Status" row. Type a number there, then on the "Tolerable" and "Budget" rows.
7. Under "Resource Owner", search and select the owner.

   Under "Resource Owner", type in the box that shows "Search stakeholders" and select the person or project that controls the resource. Only stakeholders are listed: people, groups or systems that care whether a Value goes up or down.

   If none matches, the screen says "No stakeholder record matches."; press "+ New stakeholder" to make one without leaving the card. The owner then also shows under "Stakeholder", marked "RESOURCE OWNER". After you choose one, an "acts for" line with a "Search records" box can name whom the owner acts for; optional. A red round \(−\) beside the name removes it. The line is optional for saving.

   ![The Development Resource card scrolled to "Resource Owner", with its "Search stakeholders" box outlined in orange.](http://support.gilb.com/help/media/f57fa08051ed0eac.png)
   What you see: Scroll down past "Meter" to "Resource Owner". Its outlined box reads "Search stakeholders"; the box under "Stakeholder" further down is a different one. Type part of the owner's name and select them.
8. Press "Done" when you have finished.

   Press "Done" at the top right of the card. What you typed is already saved.

   To say how much of the Resource a Solution will use, search and select the Resource under the Solution's "Impacts" and type the amount: [the answer on writing a Solution in your plan](http://support.gilb.com/help/how-do-i-write-a-solution-in-my-plan) shows how. The Resource's own "Impacts" line then lists that Solution and the amount, with a line that says how much it uses as "% of Budget" and "% of Tolerable".

   ![The Development Resource card in edit mode with "Done" at the top right of the card outlined in orange.](http://support.gilb.com/help/media/0c4e0a27a653c277.png)
   What you see: The card is scrolled to the top; the "Illustration" shows "Tolerable", "Budget" and "Status" on its arrow. At the top right, beside the box with the tag, the outlined word is "Done". Press it when you have finished.

## Deeper

Also asked:

What is a "Development Resource"? What building your project uses up, such as money, time or people; GilbApp's menu calls it "What it costs: time, money, people." Its "Budget" is the most of it you plan to use.

Only the tag is needed to create a Development Resource. Every other line on the card is optional.

The tag is the Development Resource's name. It cannot be left empty, and a tag already used in the same vault is refused.

A new Development Resource shows the level "Business" until you choose another on the "Level" in the line under the card's header. The levels you can choose are the project's own, "Business", "Stakeholder", "Product" and "Solution" by default. In the Kai-Zen method, "Business" holds all of the project's Development Resources, such as money, time or people: at least the total budget and the running cost per month.

In GilbApp, the currency is the "Unit" of each Development Resource that counts money; the plan has no other currency setting. A cost written in another unit is not converted: in the plan table, which sets Values against Solutions, it shows "Units differ" and gets no %.

When Kai-Zen writes the plan with you, money is in euro \(€\) unless the project uses another currency, which Kai-Zen takes from the project's country in the project's files. It asks you to confirm the currency in its one round of questions at the start, and records your answer in the project; [the answer on answering Kai-Zen's questions](http://support.gilb.com/help/how-do-i-answer-kai-zens-questions) shows how to reply. Its agents also set "Status", "Tolerable" and "Budget" themselves, marked as their estimates; [the answer on what happens if the AI estimates a level you set](http://support.gilb.com/help/what-if-the-ai-estimates-a-level-i-set) explains them.

Count each cost once, as the Kai-Zen method says. If a Value already includes a cost, such as net profit, estimate a Solution's effect on that Value before the cost, and put the cost only on the Development Resource. If two Solutions need the same part, make that part its own Solution and count its cost there, once. Count only what is still to spend: what is spent is already in the "Status", and the share a Solution uses is worked out of "Budget" minus "Status". When "Status" reaches "Budget", a cost's line starts "Budget used up".

To add another level, such as "Past" \(an earlier number kept as history\) or "Wish" \(a number someone says they would like\), press the button with that word beside "+ Level" under "Levels". The buttons are "Past", "Status", "Tolerable", "Budget" and "Wish", then "Other word…". "+ Level" opens a menu of the same kinds, but in GilbApp today choosing from it can end edit mode, so press the button. A "Goal" typed on a Development Resource becomes "Budget".

The card has more lines, all optional. Under "Meter", press "+ Meter" and type how the amount used is found, such as reading the project account. Also optional: "Endpoint" says between which two things the "Scale" measures \("Subject" and "Reference"\); "Qualifiers" narrow when or where a number holds \("+ Qualifier"\). "Illustration" draws the levels as an "Arrow" or a "Timeline"; you type nothing there, and "⤢" opens it full screen. "Stakeholder" names others who care how much is used, and "Authority" a person with the power to decide about it. More lines are hidden until you add them: press "+ Add Information" at the foot of the card, or the "+" beside "Done", and choose one. "Type" is the kind of thing the Resource is about, chosen from the types in GilbVeda, the shared list of terms. "Ambition Level" is an optional list of short parts, written like a Function's "Description". "Impacts" are the Solutions that use the Resource. None is needed to save.

In "Plan", the "GO TO" panel also has "Development Resources" \("What it costs: time, money, people."\), which lists only them.

This answer is written for a computer screen.

Source: GilbApp af0f04ee838a4d55887d2ff1f72edd49a4ff7ca0 \(https://gilb.com/app/version.json, built 2026-11-09.522Z, read 2026-11-09\). Steps 1, 2 and 4 and the shared sentences: identical to \(gilbAppMenuRows.ts:158-176; NewRecordButton.tsx:89; CreateModeChooser.tsx:101-138; ConnectedCreateDialog.tsx:319, :1210, :1831-1843; VaultTargetSelect.tsx:88-92, :124; TypeChooser.tsx:247-262, :361-398, :509-521; cardMode.tsx:233-305\). Development Resource: planKinds.ts:5-14 \(type list, label\), :48-51 \(menu item\), :53-71 \(Value card with Budget, Business, Resource Owner\), :160-181 \(VALUE\_LINES, RESOURCE\_LINES: Illustration, Scale, Endpoint, Qualifiers, Levels, Meter, Resource Owner, Stakeholder, Ambition Level, Authority, Type, Impacts\), :202-213 \(Business shown until chosen\); planLevelPair.ts:57-66 \(counted at Business when none stored\); recordTypes.ts:436-445 \("New development resource", Tag placeholder\); gilbAppMenuRows.ts:172-173 \("Development Resources", "What it costs: time, money, people."\). Scale: PlanValueLines.tsx:102-106 \("Lower is better"\), :862-889 \(Unit "e.g. minutes", Rate "e.g. per \[Task\]", Context "from: …; until: …", Better\); planValue.ts:147-153, :1532 \(a Resource defaults to lower\). Levels: planValue.ts:1650-1665 \(blank Status, Tolerable, Budget rows; buttons Past, Status, Tolerable, Budget, Wish\), :582-585 \(Goal on a Resource is Budget\), :67; PlanValueLines.tsx:2041-2066 \(blank rows not written; a typed number stamps the person as source\), :2131-2161, :2185, :2291 \("Add value"\), :2478-2590 \(row boxes, "Note, e.g. estimate", ⧉, ×\). Resource Owner: PlanFunctionForm.tsx:1661-1684; PlanStakeholders.tsx:595-960 \("Search stakeholders", "No stakeholder record matches.", "+ New stakeholder", AuthorityChip "acts for" / "Search records"\), :243-244, :393-397 \(owner marked under Stakeholder, uppercase\). Hidden-until-added lines: PlanFunctionForm.tsx:1060-1067, :1472-1479, :2067; CardGroup.tsx:175. Costs: valueLimits.ts:131-176 \("No % yet: &lt;tag\> needs one Status, one Tolerable and one Budget.", "% of Budget", "% of Tolerable", "Budget used up"\); valuePercent.ts:128-172 \(% Budget = amount / \(Budget - Status\)\); planTable.ts:288-291 \("Units differ", no %\); PlanUnitsFix.tsx:1-2 \(number not converted\); no currency control in src. Standards \(2026-11-09\): Kai-Zen.WriteResource \(Level: Business by default\), Kai-Zen.ResourceRules \(ValueRules, Owner, Budget, Estimate, Better\), Kai-Zen.ResourceTemplate \(example Cost.Monthly, € per month, Status 4 500, Tolerable 6 000, Budget 5 000\), Kai-Zen.BusinessLevelRules.Resources and .Currency, Kai-Zen.ProjectTemplate \(Currency line\), Kai-Zen.New.Setup \(currency asked in the one round, stored in the project\), Kai-Zen.VDTRules.Percent, .CountOnce, .Shared, .Remaining; Kai-Zen.ValueRules.Estimate. GilbVeda \(public read 2026-11-09\): t:Resource, t:Budget, t:ResourceOwnerOf, t:Tolerable, t:Estimate present; no t:Currency. Linked, not repeated: the Solution answer \(Impacts\), the answer on answering Kai-Zen's questions, the answer on what happens if the AI estimates a level you set. GilbApp 49467c2b \(https://gilb.com/app/version.json, read 14 November 2026\): src/shell/gilbAppMenuRows.ts:172 \("Development Resources", "What it costs: time, money, people."\). Live answer: What are the levels of a plan \(Business, Stakeholder, Product\)?
