If every conversation starts with the same explanation about how you want a summary presented, that preference may belong in standing instructions. Memory is not the place to store an invoice balance or authorize every future purchase. The distinction is practical: an instruction guides the work, while a record establishes what happened and its current state.
Remember a working preference, not a changing figure
A stable preference describes a way of working that remains useful when customers, dates, or amounts change. For example, identify the dates used when comparing periods, or show the amount and supporting document when explaining a change. Write a behavior someone can recognize in the answer. An instruction should make sense to a colleague before you expect it to guide the assistant.
Customer River owes CRC 95,000 is different: the next receipt can change that fact. Saving it as a standing instruction introduces an old figure into later conversations. Obtain debt from current records and reserve memory for the review method: identify the customer and period before summarizing receivables. The method can remain stable while each balance is retrieved again.
Hypothetical example: one report, two audiences
A fictional company wants expense summaries to identify the periods and distinguish a currency change from a percentage change. Finance needs detail, while management wants a short explanation. Its instruction might say: when explaining expense changes, name the comparison periods and separate the amount from the percentage. It does not need to invent results or decide which expenses have been approved.
Test with illustrative amounts of CRC 200,000 in one period and CRC 250,000 in another. The difference is CRC 50,000; using 200,000 as the base, the increase is 25%. Check whether the answer identifies the base, names both periods, and distinguishes CRC 50,000 from 50%. Correct formatting does not make an incorrect calculation reliable.
In another conversation, management asks for only the amount and supporting documents for a quick review. The standing instruction should not fight that specific request. Tario allows a user to ask for a different presentation within a conversation. No preference can override permissions, approvals, or applicable rules. Requesting a shorter answer changes presentation, not authority to perform an operation.
Write an instruction you can test
Anthropic's documentation recommends clear, explicit instructions naming the required format or constraints. That is prompting guidance, not a guarantee that every saved preference applies perfectly or a description of Tario's accounting controls. Be more useful is difficult to test. Name the observable behavior that you expect to see in the answer instead.
- For comparisons, identify the dates of both periods before presenting the result.
- If a required draft detail is missing, ask rather than assume it.
- When summarizing unpaid documents, distinguish issue dates from due dates.
- When citing a file, identify the version consulted when that information is available.
These are examples of preferences, not performance guarantees. Choose those relevant to your team and verify their effect. Avoid collecting near-duplicate instructions. If one demands very short answers and another requires every document to be listed every time, adding a third does not fix the conflict. Review the purpose and retain a coherent preference.
Saving organization memory in Tario
Tario's help places Organization memory in Settings under Automation, on the AI automations tab. You can add an instruction with a title and text, edit it, or delete it. A title should identify its purpose without opening the record: period comparison says more than important rule. Instructions are stored for that company and guide its team's work.
You can also ask in chat to remember a preference. Tario prepares a proposal; saving it requires approval from someone with configuration permissions. Saying remember this does not itself establish that the memory was saved. Inspect the card and approval outcome. If it remains pending, do not assume that colleagues' conversations already receive the instruction.
The service supports up to 30 instructions and up to 500 characters per instruction. Those are limits, not a target to fill. The context sent to the assistant is also bounded, so a long collection does not guarantee that every instruction is included in each request. Prioritize a small set of necessary preferences and verify important ones in a test conversation.
What should not become a standing instruction
Do not store passwords, tokens, current balances, or open-ended authorization such as approve every expense from this vendor. Preferences should not replace a contract, catalog, or customer record. Update the relevant record when a commercial agreement changes. Mentioning an operational fact in memory does not make it true or keep the document that established it synchronized.
Preferences should not prescribe fiscal treatment either. This article proposes no tax or document-issuance rules. If you want consistent handling of fiscal questions, guide presentation and review without demanding predetermined results. Memory can request identification of supporting evidence; it should not insist that an event always receive the same treatment without examining its actual data.
Test, revise, and remove obsolete preferences
Before sharing an instruction with the team, compare a query without it and one with it in an authorized test environment. Keep the question and data constant so you can recognize the change. Altering memory, period, and customer simultaneously makes the cause unclear. Keep the test question to repeat when the preference is revised later.
After editing or deleting an instruction, start a new conversation to check the result. An older conversation can still contain the previous preference in its history. That historical reference does not establish that deletion failed. Also check whether another instruction with the same purpose remains and may still influence the answer.
Assign someone to review memories when working procedures change. The comparison preference may remain useful, while a reference to an abandoned report format may not. Record reasons for changes in your internal procedure without creating another memory to narrate each edit. A colleague should be able to understand the intended behavior and test it with a specific question.