> ## Documentation Index > Fetch the complete documentation index at: https://zenofirm.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Start the day on Today > Read what needs your decision and what has changed, beside the work waiting in the queue. Today is the page the console opens on. It answers two questions in a minute: what needs your decision, and what has changed. Beside it, the work queue shows what is waiting, due or overdue. Your assistant writes the brief and the console lays it out. You read a short takeaway for each subject and open the evidence only when you want it. ![Today: decisions beside the work queue](https://mintcdn.com/zenofirm/71BnQmiGf5OjeNT9/images/illustrations/cloud/today-decision-brief.svg?fit=max\&auto=format\&n=71BnQmiGf5OjeNT9\&q=85\&s=547e18d61c537f0b6e456343e0445a30) ## What is on the page | Part | What it holds | | - | - | | **Needs your decision** | Findings your assistant cannot settle on its own: an ambiguous charge, a gap it could not explain, a choice only you can make. | | **Worth knowing** | Material changes that need no action, such as a close that is now reconciled. | | **Earlier notes** | Notes written before Today became a brief. They move up once your assistant revises them. | | **Work queue** | Changes waiting for your approval, then what is overdue, due soon, waiting on you, and what needs a look. | On a wide screen the queue sits beside the brief. On a phone it sits above it. The client picker narrows the page to one client. People limited to particular clients see only those clients' subjects, and firm-wide subjects are visible only to people with access to the whole firm. ## Read a subject Each subject shows its client and when it was last updated, then: * **A title** naming the decision or the change. * **A takeaway**: one sentence saying what matters and why now. * **Next**, on a decision only: the one thing someone needs to do. * **A link** to the page where you do it, such as the coding rules, a plan or a bank feed. It opens the real page, with its normal review and permissions. **Details** opens the evidence: the figures, a table or a diagram, the records and dates behind the conclusion, any further links, and who wrote it. **Remove from Today** is there too. It takes the subject off the shared page for everyone, and it approves nothing and closes nothing. ## The work queue The queue is gathered from across the firm and is always current, whatever the brief says. | Band | What lands there | | - | - | | **Waiting for your approval** | Single changes your AI asked to make outside a plan. | | **Overdue** and **Due soon** | Engagement periods past due or due within the week. | | **Waiting on you** | Plans to read, documents to check, answers from clients. | | **Needs a look** | Entries that failed to post, questions drafted and not sent, agents that stopped checking in. | | **Housekeeping** | Stale syncs and check-ups, folded away until you open them. | If the console cannot read a list, the queue says so rather than showing it empty. ## Ask your assistant to keep it current After a review, ask for it in so many words, or make it a step in a [playbook](https://zenofirm.com/docs/cloud/cadence.md): > Review Ridgeline's bank lines from this week and put what I need to decide > on Today. Don't plan anything yet. Your assistant reads the page first, then publishes one revision: it updates the subject it wrote last time rather than adding another, combines related findings, and removes what is resolved. A decision stays until it is answered. A good brief is short: three to five subjects for a client, fewer when the books are quiet. What stays off it: * **What the queue already shows.** A document arrived, a plan awaits approval, a client replied. A subject appears only when your assistant has something new to add, such as a reason the plan needs a closer look. * **Reports and diaries.** A full profit and loss, a list of the steps it took, a check that found nothing. Those belong in the [work log](https://zenofirm.com/docs/cloud/console.md#work-log) or a report. * **Boilerplate.** How a document was read, or a safety disclaimer repeated on every note. > [!TIP] > > A balance difference is not proof of a mistake. Before a gap becomes a > decision, your assistant checks timing and what is not yet posted, then names > only the amount it still cannot explain and the check that would explain it. ## History **History** lists every saved version of the page, including subjects that were removed. Open one to read what the page said then. The work queue keeps showing current work while you read an old version. ## What the brief cannot do Your assistant's notes are context, not instructions or approvals. Notes are drawn without scripts, forms or anything fetched from elsewhere, and a note cannot draw an approval button. Approving a plan still happens on the plan's page or in the chat, with your own click. Publishing to Today changes no books and sends nothing to a client. The tools behind the page are `qb_today` and `qb_revise_today`. See [the tool reference](https://zenofirm.com/docs/cloud/tools.md#today). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.