Help centre / Guide 02
Ask like a manager, not a search box.
The best SANDR request sounds less like a clever prompt and more like a clear shift brief: what happened, where it belongs, what matters, and what should exist when she is done.
01 / Guide 02
Use one clear, repeatable brief.
Ordinary chatbot advice says to add more background. In SANDR, much of that background already exists as approved venue history, recurring patterns, reports, tasks, files, and calendar items. Your job is to explain the situation and the result you want, not to paste the whole business into every message.
- Context – where, when, and what changed.
- Goal – the decision or piece of work you need.
- Constraints – time, people, policy, budget, standard, or audience.
- Output – the form you can use next: a handover, questions, owner actions, a comparison, a review agenda.
Friday 08:00–09:00, one barista was off, drinks backed up ten minutes, and two regulars left. Use this venue only. Separate facts from hypotheses, tell me what evidence is missing, and propose one reversible move with an owner and proof.
“Turn these four observations into a five-line handover for the closing manager. Preserve the numbers and mark anything uncertain.”
“Tell me how to fix staffing.” SANDR has to guess the place, the period, the constraint, and the decision you actually face.
02 / Guide 02
Put the thread where the work belongs.
Choose one venue when the question is about one place, and use the whole workspace only for group questions or work that genuinely crosses authorised venues. This choice limits which information SANDR uses.
The message controls let you include or exclude Recurring patterns, Knowledge library, Articles, Venues, Check-ins, Plans & tasks, Files & reports, and Calendar. Leave a source off when it cannot change the answer.
- For a short rewrite you probably need no business history at all.
- For “has this happened before?”, include the venue’s patterns, check-ins, or reports.
- For a meeting plan, include the relevant tasks and calendar – not every file.
- For a cross-venue comparison, confirm your role is authorised for every place involved.
03 / Guide 02
Choose a ceiling, not a status symbol.
Performance sets the maximum capability and credit charge for the next turn. Actual use may be lower than the selected ceiling. The right choice follows consequence, not how impressive the answer should sound.
- Auto – SANDR picks the lightest level that can handle the request.
- Quick · 3 credits – simple questions and light drafting, with no tools.
- Context · 35 credits – work that reads the selected venue background and supports safe actions.
- Deep · 160 credits – complex analysis and multi-step work, with confirmation for consequential actions.
Start with Quick for formatting, clarification, or a short handover. Use Context when venue history changes the decision. Use Deep when the problem is recurring, unclear, expensive, or touches several parts of the business. Auto is a sensible default when you are unsure.
Before Deep work, ask whether the result will change an owner, a decision, a plan, or a material risk response. If not, narrow the question or gather better evidence first.
04 / Guide 02
Treat the answer as a reviewed handover.
SANDR can use approved business history that a generic chatbot does not have, but manager judgement is still the last step. Before acting, check which statements are facts, which are interpretations, what is missing, and whether the answer stayed inside the intended venue and audience.
- Ask what she is assuming, or what would change the recommendation.
- Open the source report, task, or file before a consequential decision.
- Correct weak patterns rather than accepting a polished explanation.
- Review every proposed write before confirming it.
- Turn a useful answer into one owned move with a date and proof, then come back for the result.
Never paste passwords, card details, medical information, or unnecessary employee identifiers. Redact guest and employee details when the work does not require them.
05 / Guide 02
Bring in facts. Take out something usable.
SANDR fits around existing routines without pretending every tool is connected. Bring the relevant facts from a shift log, rota export, email, spreadsheet, photo, or team message, and keep one trusted record in SANDR once the item becomes tracked work.
- Before a meeting – ask for unresolved decisions, overdue proof, and three questions the room must answer.
- After a meeting – paste the agreed facts and ask for owners, dates, what must happen first, and proof.
- At handover – dictate what changed, then ask for a factual five-line brief for the next manager.
- From a spreadsheet – add the relevant extract, name the time window, and ask which change deserves investigation rather than “analyse this”.
- From a message thread – extract the useful business facts. Do not copy a private conversation into a wider venue record without a legitimate reason.
06 / Guide 02
Keep a small library of questions that lead to action.
Turn these notes into a concise handover. Keep facts and numbers exact. Separate unfinished work, owner, deadline, and the next thing to verify.
What are you assuming? Show the strongest evidence for and against this interpretation, and name the smallest new fact that would change it.
Turn this recommendation into one small test we can reverse. Name the owner, first move, timing, what must happen first, completion proof, and result check.
Using this venue’s authorised context, prepare a 20-minute review: movement since last week, blocked work, one decision, and what evidence we need next.
Save the structure, not the exact words. The strongest habit is consistent scoping and review, not prompt theatre.
Keep going
Follow the next thread.
Each guide starts from a real part of the work and keeps the next move clear.