The Role-Context-Task-Format Structure
12 min read
If you learn one technique from this entire course, make it this one. Role-Context-Task-Format (RCTF) is a four-part structure that turns any rough request into a professional brief. It works for every AI tool and every kind of task.
The four parts
Role tells the AI who to be. Models write differently as "an experienced retail copywriter" than as a blank slate. A role sets vocabulary, perspective, and standards in a single sentence.
Context gives the background the AI cannot know: your business, your customer, the situation, any constraints. This is where you paste in real material — your current draft, your notes, your product details. Remember the context window from Chapter 1: if it is not on the desk, it does not exist.
Task states exactly what you want done, with numbers where possible. "Write 3 subject lines" beats "help with subject lines."
Format describes what the output should look like: length, structure, tone, bullet points versus paragraphs, table or list. Format instructions save the most editing time of all four parts, and they are the part people most often skip.
RCTF in action
Sam runs a 12-person landscaping company and needs a job posting. Here is the RCTF version of his prompt:
Role: You are an experienced hiring manager who writes job posts
for skilled trades and gets strong applicants.
Context: I run a 12-person residential landscaping company in
Halifax. I need a full-time crew lead. Pay is $28-32/hr, Mon-Fri,
company truck provided. Our crews take pride in tidy, on-time
work, and most of our business is repeat customers.
Task: Write a job posting for the crew lead position.
Format: About 250 words. Friendly but professional. Structure:
one short intro paragraph, a bulleted "What you'll do" list
(5 bullets), a bulleted "What we're looking for" list (4 bullets),
and one closing line telling people how to apply.Notice what the labels do: they force you to think through the request before the AI ever sees it. Half the value of RCTF is that it debugs your own thinking.
You do not have to write the labels out every time. Once the habit forms, a well-ordered paragraph works just as well — the structure matters more than the headings.
Which part fixes which problem
When an output disappoints, one of the four parts is usually missing. Use this to diagnose:
- Wrong tone or wrong expertise level: strengthen the Role.
- Factually off, generic, or ignorant of your situation: add Context.
- Did a different job than you wanted, or did too much or too little: sharpen the Task.
- Right content, annoying shape (too long, wall of text, wrong structure): specify the Format.
Common mistakes to avoid
- Writing a role but no context. "You are a marketing expert" alone still knows nothing about your bakery.
- Stacking three tasks in one prompt. "Write the email, then a social post, then five headlines" muddies all three — you will learn a better way in Chapter 3.
- Describing format after the fact. Saying "make it bullets" on round two works, but saying it up front costs nothing.
- Forgetting constraints. If it must not mention pricing, must fit in an SMS, or must avoid promising exact dates — say so in Context.
Try it now
Take a task you actually need done this week and write it as four labeled lines: Role, Context, Task, Format. Spend at least two sentences on Context — real details about your business, not placeholders. Run it, and notice how much closer the first draft lands compared to your usual one-line asks. Save this prompt; you will turn it into a reusable template in Chapter 3.