The first answer is generic. You add background, then another document, then the entire email thread. The conversation grows, but the task is still not clear.
For a one-off business task, give AI the outcome, audience, relevant source material, constraints and unresolved questions. Supply enough context to support that task, rather than every document available. A short, explicit brief can be more useful than a large unexplained upload.
Photo by Vitaly Gariev on Unsplash.
Define the accepted result
Say what you want to use the output for. Preparing an internal discussion note is different from writing a client message. The intended use determines which facts and qualifications matter.
For an illustrative supplier meeting, the result could be five questions about the client's responsibilities in a proposal. It does not need to include a general company strategy, every previous supplier email or an invented recommendation.
Name the person who will use the work and what they already know. This helps set the level of explanation without asking for vague professional language.
Use a six-field context brief
Record:
Task: the concrete result needed.
Purpose: the decision or action it supports.
Audience: who will read or use it.
Sources: the authorised material that governs the answer.
Boundaries: what must remain unchanged or outside scope.
Unknowns: information that must not be guessed.
Add the desired output form only after those basics are clear. A table is helpful when comparison matters; it does not repair an unclear question.
Explain the role of each source
Label a current procedure as authoritative, an old draft as background and a customer's message as a request. Do not assume the tool will infer those relationships from filenames.
If two sources disagree, identify which owner needs to resolve the conflict. A one-off context pack should not turn an outdated attachment into the governing instruction merely because it contains more detail.
Use only material suitable for the approved tool. More context is not automatically better when it includes irrelevant or unnecessary information.
An illustrative draft request
Instead of saying write an onboarding email, specify the recipient's stage, confirmed next step, approved document requirements and facts still unknown. Ask for the missing questions outside the draft.
The output can now be checked against a bounded task. If the client has not agreed a start date, the assistant can leave that detail unresolved rather than completing the email with a plausible promise.
End the task cleanly
When you accept the result, save the useful output and source references in the normal working location. Do not rely on the conversation as the only record somebody else can use.
For a recurring task, consider whether a maintained template is worthwhile. For a one-off task, avoid building an elaborate prompt system before a simple brief has proved insufficient. The preparation should remain proportionate to the work it helps you complete.
For related practical guidance, see maintaining shared prompt templates and selecting suitable source documents.
Hili Consulting can help prepare a bounded context brief for a one-off AI task. Arrange a free 30-minute consultation and bring one example of the work you want to improve.
