It's important to name your needs correctly,
since the need's name is the key to re-ordering the right item(s) to cover the need.
Here are guidelines to follow.
| The name of a need is just what you would put on a shopping list. |
| The assets that you use to cover a need should be substitutes for one another, as far as you're concerned. That is, you don't really care which one is chosen to cover the need. |
Price comparisons among these assets would be meaningful when shopping for them. They don't have to be the same thing -- just comparable. For example, you could compare a cake mix to a pre-made cake, or going to a baseball game to going to a soccer game, as long as they meet the same need for you.
For example, suppose one of your needs is ground coffee. First, try to identify a standard top folder (and any standard subfolders) where this need fits. Coffee fits well under "Food >> Beverages", so your complete need name could be:
In other words, the need name may be closely tied to the name of the product(s) purchased to cover the need, without the brand name & packaging, unless that's required.
These naming guidelines apply to any need,
but especially to needs covered by supply-type assets.
Durable assets should also be assigned to a specific need for more detailed reports and better resale support,
or you can simply assign them to the "(no need)" need.