Skip to content
Independent guide · Dots Bot

Work & Business

Use a dot to prepare decisions across inboxes, meetings, projects, sales, and research.

Updated 4 October 2026 · Independent of OpenAI

Work & Business — Keep important work moving
Visual guide to Work & Business

Workflows span people and systems, so a clear boundary matters as much as a good output. Start with a narrow source set and state who may see the result.

Use a dot to prepare decisions across inboxes, meetings, projects, sales, and research. Think of this as a small research or drafting assignment. Source, date, uncertainty, and a review point make the outcome usable.

Editorial route

Define the audience before the output

An inbox triage brief may be for your eyes only, a proposal is for a customer, and a status note may go to a whole team. That audience changes which source can be quoted, which assumptions can remain open, and who must approve the next step. Start with the narrowest account or project. Then choose the guide that matches the actual deliverable rather than asking for a single agent to silently manage everything at once.

Choose a route

Guides in this section

Pick the specific page that matches the work in front of you. Each guide has a flat URL, a concrete review point, and links back to this overview. If the request spans several guides, finish one bounded piece before adding the next.

Define the task

How to use this section

Gather relevant work sources, owners, goals, cadence and label the version or account. A narrow source set usually gives you a result that can actually be audited.

A useful deliverable

Reviewable drafts and concise decision lists. Separate completed work from proposed actions so you know exactly what has happened.

Worked situation

How this plays out in practice

An account manager needs a morning inbox brief, a meeting pack, and a Friday status note. Those outputs share context, yet each has a different audience and approval point. The decisive information is easy to overlook in a generic task. Require it to appear in the output before moving to an action.

Define what information can cross from one workflow to another, who owns each decision, and when an external message needs a human sign-off. Retain the key reference and the date so a future revision does not have to reconstruct the whole task.

A practical sequence

Run a bounded first pass

1. Establish the starting point

Before acting, confirm the identity and date of relevant work sources, owners, goals, cadence. A result built on the wrong version is difficult to repair downstream.

2. Request a reviewable draft

For each responsibility, define the inputs, the update rhythm, the expected deliverable, and the decisions you want escalated. Ask for a draft first and adjust based on the first result. Ask for a smaller, verifiable result if the source set is too large for one pass.

3. Decide the next action

At the handoff, restate no external commitment without authorization. Give separate approval for any recipient, purchase, or lasting edit.

Editorial judgment

Where a plausible answer can fail

A polished report may expose confidential notes to the wrong team. Scope sources and recipients before optimizing the format of the answer. Inspect external effects separately from the prose. A good draft can still propose the wrong recipient or target.

Connected apps have separate permissions. Review recipients, confidential information, and commitments before anything leaves your workspace. A request for one more source can be the right result when the existing material cannot settle the issue.

Where to go next

Connect this result to the right follow-up

If you are new to the product, Get Started & Trust helps establish the account and permission basics before you use this section as a working plan. Do not expand the task silently. Use a connected guide when the desired deliverable changes.

For a closely related outcome, open Triage Your Inbox. That guide focuses on find the messages that actually need your attention. It may use some of the same context, but you should confirm the source and the decision point again. If your next question is about a different angle, Prepare for Meetings and Draft Follow-Ups is a better fit: walk into a meeting with context, open questions, and a useful agenda. A new deliverable should have its own date, owner, and acceptance check.

Before you reuse this result elsewhere, look at Get Started & Trust for the wider product or review boundary. Take forward the verified facts and leave behind any assumption that was specific to this example. If the source has changed since the draft was made, update the relevant claim first. The purpose of the link is to make the next step more precise, not to imply that every connected guide is needed for every reader.

Adapt this

Build your own task brief

Edit the bracketed information and any sentence that does not fit your account. This is a suggested workflow, not a promise that your dot has access to a particular app or feature.

Your review

Check before moving on

Tick what you have actually checked. Your progress stays on this device for this page and can be cleared at any time.

0 of 4 checked

Questions

Frequently asked questions

Which guide should I open first?

Open the child guide closest to the result you need: reviewable drafts and concise decision lists. Start with its inputs and review gate, then come back to this overview for adjacent tasks.

What information matters most for work & business?

Start with relevant work sources, owners, goals, cadence. Workflows span people and systems, so a clear boundary matters as much as a good output. Start with a narrow source set and state who may see the result. Give the exact source or account where a decision depends on it.

How do I combine two related workflows?

Define separate results and approval points. Connected apps have separate permissions. Review recipients, confidential information, and commitments before anything leaves your workspace.

What would a useful result look like here?

Reviewable drafts and concise decision lists. It should make assumptions visible and leave a trail to the source, especially for dates, prices, permissions, or changing product details.

What is the common failure in this situation?

A polished report may expose confidential notes to the wrong team. Scope sources and recipients before optimizing the format of the answer. Review that issue in the actual output instead of treating a polished presentation as proof.

Where can I check the current details?

Follow the official source linked below and inspect your account where access matters. This page was revised in October 2026; availability, terms, and product behavior can change.

Source for current product details: official OpenAI documentation or announcement ↗. The worked situations and briefs on this independent site are editorial examples. Confirm current access and details in your account. Editorial policy.