Work Prompts: Inputs, Scope and Acceptance Checks
Write a Work request with the right source facts, an actual deliverable and checks you can repeat. Keep changing task details separate from saved preferences.
Supply a task, sources and a definition of done
Work prompts describe the current project. Keep changing facts and required outputs in the task; recurring account preferences have separate Custom Instructions settings. This reference defines what to supply, while the lesson walks through a real brief.
What to put in a Work request
Use the fields below to describe the outcome, sources and checks in your message. They guide the task; actual workspace permissions still determine what it can access.
Outcome: [The finished result and who will use it.]
Inputs: [Permitted notes/files, what each source supports and which is authoritative.]
Deliverable: [Actual file type, structure and required contents.]
Facts and unknowns: [Verified names/numbers/dates; missing information to leave explicit.]
Scope: [Allowed actions and any action requiring a decision.]
Preserve: [Correct facts, sections, interfaces or earlier versions.]
Checks: [Known totals, source comparisons, tests or other acceptance checks.]
Done means: [Delivered files, checks actually completed and anything incomplete.]Explain what each input means
| Item | Details |
|---|---|
| Source notes | Identify which facts may appear and which details are unknown. |
| Attached document | Name the relevant pages/sections and how they support the task. Wait for usable processing before relying on extraction. |
| Style reference | Say which aspects to adapt; do not treat its examples as facts about your project. |
| Conflicting material | Choose an authoritative source or ask for the conflict to remain explicit. |
| Local project | Use a supported client and actual project permission. A path written in a prompt is not a connection grant. |
Ask for an actual artifact when you need a file
Name the file type, sections, cells or slides and native structure that matter. In the real document task, the request asked for an editable Word file and a native table rather than only a prose outline. Inspect the returned artifact; a filename in a reply is insufficient.
Scope, preservation and review points
Name allowed actions and exclusions. Explain which existing facts, formulas or interfaces should stay unchanged and which actions need your decision. Actual workspace permissions and action-review settings still govern tools. A prompt does not grant access or prove a review pause occurred.
Make acceptance checks concrete
A source comparison, known total, required slide or relevant test can reveal a failure. Distinguish checks the assistant actually ran from proposed checks. For the workshop proposal, USD 480 − USD 370 = USD 110 and tax/delivery stayed unspecified.
Revise the same task with a specific target
Name the file, requested change and facts or interfaces to preserve. Ask for a separate revision when comparison matters, then inspect the complete result for contradictions.
In [ARTIFACT/VERSION], change only [SPECIFIC TARGET] to [REQUESTED CHANGE].
Preserve [NAMED CORRECT FACTS/SECTIONS/FORMULAS/INTERFACES].
Check [KNOWN ANSWERS] and reread the complete result for contradictions.
Keep the original and return a separate revision if needed.
State which checks actually ran and what remains incomplete.Access, task context and usage
Work requires Plus and applicable credits. Current request context can include permitted files, conversation history and enabled personalization. Request wording does not itself disable Memory or revoke permissions. Follow-ups can add usage; launch limits, active-session capacity and credits are separate.
If the prompt did not produce the required result
Identify the missing artifact, wrong figure or unsupported claim and state the expected result from your source. Supply a permitted relevant excerpt if the original source was unavailable. Keep the failing version and inspect the next output before relying on it.
Work prompt reference questions
Use concise, checkable requirements.
Are Work prompts the same as saved account instructions?
A Work prompt states the current task and changing facts. Saved Work instructions supply reusable preferences through their own settings and timing rules.
Can a prompt give Work access to a local path?
No. The client, workspace and actual grants determine local access. Attach a permitted source or use the supported project connection.
Do I need to ask for an editable file explicitly?
Name the actual artifact and structure you need, then inspect the delivered file. A Chat answer or written outline does not establish an editable workbook, document or deck.
Guides and resources
Find more detail and choose your next step.
Give your next task a clear definition of done.
Open Gab AI and choose Work. Supply your brief and permitted sources, then review the delivered files and any focused revision.