THE LEARNING CENTER · KEY IDEAS

Better context.
More useful work.

Simple habits for getting a useful first draft—and knowing what to check.

SIMPLE TEST

What would someone need to know to do this well?

If a teammate would need certain information to do the task well, ChatGPT probably needs it too.

Start there. Explain the job, provide the relevant information and describe the result you need. A model can work with your brief, but it cannot reliably fill in facts you have not supplied.

Return to your practice task.

If a teammate were helping with this task, what would they need to know before producing a useful first draft?

TASK · CONTEXT · EXPECTATION

Give a brief someone can work from.

01 / THE TASK

What are you trying to do?

Name the action, the goal and why it matters.

02 / THE INFORMATION

What information should ChatGPT use?

Provide background, files, sources, examples, audience, constraints or goals.

03 / THE RESULT

What would a good response look like?

Provide the format, tone, length, sections, criteria or an approved example.

Example: a missed project meeting

Task: Draft an email.

Context: It is for a colleague who missed today’s project meeting and needs the key decisions. Use the actual meeting notes I provide.

Expectation: Use three bullets, a warm tone and a clear next step. Mark missing owners or deadlines for me to confirm.

WORKING WITH FILES

Give it something useful to work from.

A file provides context. Your instructions explain what to do with it.

Common ways to use files with ChatGPT
File typeWhat ChatGPT can doWhat to check
ReportSummarize key findings, risks and recommended actions.Check the summary against the report; separate its recommendations from new suggestions.
SpreadsheetIdentify trends, outliers or questions to investigate.Check units, time periods, missing values, formulas and totals.
PolicyTurn requirements into a checklist or quick-reference guide.Check the current version, scope, exceptions and exact wording of requirements.
Meeting notesPull out decisions, owners and action items.Confirm names and deadlines; flag anything the notes leave unresolved.
Template / past exampleRewrite a draft to follow the same structure and tone.Carry over the format, not old facts, names or commitments.
Draft documentSuggest edits, identify gaps or adapt it for a different audience.Confirm that edits preserve the intended meaning and factual claims.

Point to the relevant material.

Name the file, sheet, section or date. Explain which source takes priority if files conflict. Ask for page, section or cell references where available so you can check the result.

Try this: “Use the attached report. List the five main findings, the evidence for each and any unanswered questions. Include page references where available. Flag unreadable or missing material.”

USE THESE ON YOUR NEXT TASK

Small habits. Better first drafts.

01

Name the job.

Start with an action and a purpose. Draft, compare, extract, explain or organize. Keep the first request focused enough to check.

Try this

“Draft a follow-up email that confirms the decisions in these meeting notes.”

02

Give it the same brief you would give a teammate.

Include the background, audience, goal, constraints and relevant sources. Explain details that would otherwise be easy to misunderstand.

Try this

“The reader missed the meeting. They need the decisions, their responsibilities and the next deadline.”

03

Use the source, not your memory of it.

Provide the actual policy, order record, notes or approved document. For current facts, use web search and open the authoritative source.

Try this

“Use the attached policy dated October 1. Identify the section supporting each answer.”

04

Define what good looks like.

Specify the format, length, tone and required content. A useful output can be judged against a few clear criteria.

Try this

“Use three bullets, a warm tone and a clear next step. Keep it under 150 words.”

05

Show one useful example.

An approved example can explain your preferred style or structure. Tell the model which features to follow and which details must change.

Try this

“Follow this example’s format. Use only the facts in the new notes; do not reuse its names or figures.”

06

Make missing information visible.

Ask the model to flag gaps and conflicts. Give it permission to ask a question or leave a placeholder when a needed fact is absent.

Try this

“If an owner or date is missing, mark it [confirm]. Do not invent it.”

07

Separate facts from suggestions.

A plausible recommendation is not a recorded decision. Keep source-backed facts, assumptions and proposed next steps distinct.

Try this

“Label each item as a recorded decision, an open question or a suggested next step.”

08

Check the date and scope.

A source can be real and still be outdated or irrelevant. Check the version, location, customer, product and time period before relying on it.

Try this

“Which source version and date does this answer use? Flag anything that needs a current check.”

09

Break complicated work into reviewable steps.

Extract the facts first, review them, then draft or analyze. Smaller steps make errors easier to find before they spread.

Try this

“First list the decisions and action items from the notes. Wait for my review before drafting the email.”

10

Review with CLEAR.

Check Complete, Logical, Evidence, Audience and Relevant. Open the cited sources and confirm they support the claims. Recheck important figures.

Try this

“Compare this draft with the brief. List missing requirements, unsupported claims and anything that does not fit the audience.”

11

Revise one problem at a time.

Tell the model what needs changing and what is already working. Specific feedback is easier to act on than “make it better.”

Try this

“Keep the three decisions unchanged. Shorten the introduction and make the next step more specific.”

12

Use approved tools and appropriate information.

Follow your organization’s rules for customer, employee and confidential records. Share the information needed for the task, with the right access controls.

Try this

“Use this approved, redacted sample to develop the template before working with live records.”

13

Keep consequential actions under review.

A draft is different from sending a message, changing a record or approving a payment. Decide which actions need an authorized person’s approval.

Try this

“Prepare the customer reply and show the supporting order record. Wait for approval before sending.”

14

Test the awkward cases.

Try missing fields, conflicting records, unusual requests and outdated sources. A useful workflow should handle exceptions or route them to a person.

Try this

“What happens if these notes contain two different deadlines? Show the conflict instead of choosing silently.”

15

Measure useful work, not just speed.

Track the time saved alongside accuracy, review effort and rework. A faster draft is valuable when it helps someone finish the job well.

Try this

“Record drafting time, checking time and corrections for this task before and after using AI.”

16

Keep the source of truth outside the chat.

Save approved decisions in the system your team uses: the CRM, document library, ticket or accounting record. Assign someone to keep it current.

Try this

“After approval, record the final decisions in the project document and link back to the meeting notes.”

PUT ONE IDEA TO WORK

Return to your own task.

  1. Write the task in one sentence.
  2. List what a teammate would need to know. Gather those sources.
  3. Describe a good response: audience, format and required details.
  4. Ask for a first draft, with missing information flagged.
  5. Review with CLEAR: Complete, Logical, Evidence, Audience, Relevant.

One useful prompt

“Before drafting, identify any missing information that would materially change the answer. Ask me for it, or use a clearly marked placeholder.”

Sources and further reading

PUT IT TO WORK

What should we build for you?

Bring one bottleneck. We’ll discuss the sources, the system and the business case.