Natural English–Roman-Urdu writing is code-switching with a purpose. English may hold a technical term, while Roman Urdu may carry a reaction, instruction, or emotional beat. It is not word-for-word translation decorated with slang.

By the end, you will have a language style card, matched script pair, three calibrated posts, and review notes.

// concept

Mix by Meaning, Not by Word Count

Start with meaning units: one promise, reason, example, warning, or action per line. Decide what each unit must do before choosing its language. A “60% English, 40% Roman Urdu” target is a review signal, not a quota.

Meaning unit	Usually works well in	Reason
Product names, UI labels, technical terms	English	The audience may already search for these exact terms
Explanation or step	Either, based on the audience	Clarity matters more than showing a mix
Emphasis, reassurance, reaction	Roman Urdu	Spoken rhythm can make the line feel immediate
Legal, financial, or safety detail	The clearest wording	Never blur a qualification

Compare a literal conversion with a meaning-first rewrite:

English source: This template keeps your weekly posts consistent without making every post sound the same.

Forced/literal sample: Yeh template aapki haftawaar posts ko mustaqil rakhta hai baghair har post ko aik jaisa sunaye.

Natural mixed sample: Yeh template weekly posts ko consistent rakhta hai, lekin har post ko copy-paste jaisa nahi banata.

The literal sample is understandable, but “haftawaar,” “mustaqil,” and “baghair … sunaye” create an unexpectedly formal register. The natural version keeps established content terms in English and expresses the contrast in simple Roman Urdu. Test that choice with the intended audience.

// concept

Build a Language Style Card and Glossary

Do not ask AI to “sound Pakistani.” That invites clichés and exaggerated slang. Give it a language card based on consented audience research or your own natural speech.

// template — copy me12 lines

LANGUAGE STYLE CARD
Audience: [specific segment, region, age range, channel]
Relationship: [teacher-to-learner / peer-to-peer / brand-to-customer]
Pronoun: [aap / tum] — never switch without a reason
Target mix: [for example, 60% English / 40% Roman Urdu; review signal only]
Use English for: [UI labels, domain terms, product names]
Use Roman Urdu for: [steps, emphasis, reassurance, punchlines]
Spelling choices: hai (not he); nahi (not nahin); mein = in; main = I
Sentence style: [short spoken lines / formal written lines]
Avoid: [forced slang, stereotypes, unexplained idioms, filler words]
Channel adjustment: [short-video voice / LinkedIn text / carousel]
Reviewers: [one target-audience speaker; permission recorded]

Add a terminology list so one concept does not alternate between “workflow,” “kaam ka nizaam,” and “process.”

Concept	Preferred form	Avoid	First-use note
content calendar	content calendar	posting wali sheet	Explain as the weekly publishing plan
call to action	CTA	action ki pukaar	Define CTA once, then use CTA
source check	source check	research kar lena	State exactly which claim and link to check
draft	draft	kaccha content	“First version” is a clear alternative

A spoken TikTok or Reel script may carry more Roman Urdu than a LinkedIn post for professional peers. Test each channel instead of copying one ratio everywhere.

// concept

Prompt for a Matched Pair, Then Back-Check It

AI needs the language card, an English meaning anchor, and one good example. Redact private DMs and customer details first.

// prompt — copy me22 lines

You are editing a short spoken script. Preserve meaning before style.

Audience: Pakistani freelance designers starting to publish educational content.
Channel: 45-second vertical video.
Relationship: experienced peer speaking to a beginner; use “aap”.
Mix: about 60% English and 40% Roman Urdu as a review signal, not a word quota.
Keep in English: content calendar, source, draft, CTA.
Roman-Urdu spelling: hai, nahi, mein, main.
Avoid: forced slang, “scene on hai,” cultural clichés, literal translation,
and claims not present in the source.

English meaning anchor:
<source>
[paste the approved English script]
</source>

Return:
1. English reference, split into numbered meaning units.
2. Natural mixed script with the same numbered units.
3. A change note for each unit: PRESERVED, REFRAMED, or NEEDS REVIEW.
4. A glossary of technical terms kept in English.
Do not add facts, examples, promises, or audience assumptions.

Back-check line by line. Ask: Is the promise unchanged? Did “may” disappear? Did the CTA gain urgency? Mark NEEDS REVIEW if a line loses a condition or adds a claim.

Read the script aloud at recording pace. Mark tongue-twisting switches, clashing registers, and lines too long for one breath. Then ask someone from the intended audience—not simply any Urdu speaker—to review meaning and naturalness. A Karachi university student may not represent a Pashto-first business audience in Peshawar.

// worked_example

Worked Example

This hypothetical sample is for an Islamabad stationery seller explaining how to plan product posts. No result is claimed.

English meaning anchor

// prompt — copy me5 lines

1. Posting only when you remember makes your product story hard to follow.
2. Choose one weekly theme before writing individual posts.
3. Put the product photo, price source, and delivery note beside each draft.
4. Then write three posts from the same theme: a use case, a detail, and an FAQ.
5. Save this checklist and test it for one week.

Awkward first draft

// prompt — copy me3 lines

Jab aap yaad karte hain tab posting karna aapki product kahani ko follow karna mushkil banata hai.
Pehle aik haftawaar mauzoo muntakhib karein, phir individual posts ko likhein.
Yeh zabardast content hack aapka game totally change kar dega.

The first two lines mirror English grammar. “Haftawaar mauzoo muntakhib karein” breaks the friendly register, while the last line invents a result and adds forced slang. The fix returns to the approved meaning units.

Natural matched script — revised sample

// prompt — copy me5 lines

1. Sirf yaad aane par post karein, toh product ki story scattered lagti hai.
2. Individual posts likhne se pehle ek weekly theme choose kar lein.
3. Har draft ke saath product photo, verified price source, aur delivery note rakhein.
4. Phir us theme se teen posts banayein: ek use case, ek product detail, aur ek FAQ.
5. Checklist save karein aur ek week test karke dekhein ke workflow aap ke liye practical hai ya nahi.

Review notes: Unit 1 is reframed without changing the cause. Units 2–4 preserve the instructions. Unit 5 keeps “test” instead of promising improvement. During read-aloud review, replace “verified price source” with “price ka verified source” if target reviewers prefer that order.

// failure_cases

Failure Cases to Diagnose

6 cases to diagnose

Switching every few words
Group words by meaning unit and let a complete phrase stay in one language.
Literal English syntax
Lines such as “main is ko sense banata hoon” reveal translation, not natural code-switching. Restate the intended meaning as you would say it aloud.
Performative slang
Words the creator never uses—added only to appear local—damage trust. Delete them and use the audience’s observed vocabulary.
Terminology drift
“CTA,” “action line,” and “call wali ending” refer to one concept. Lock one preferred form in the glossary.
Lost qualification
“This may help” becomes “yeh zaroor kaam karega.” Compare numbered meaning units and restore uncertainty.
One mix for every platform
A spoken script can read too casual on LinkedIn. Make and test a channel-specific version.

// pakistan_angle

Pakistan Angle

Roman Urdu is convenient on Latin-keyboard phones, but it is neither one standardized voice nor a substitute for Pakistan’s linguistic diversity. Urdu, Punjabi, Pashto, Sindhi, Balochi, Saraiki, Hindko, and other languages shape expression. Do not borrow regional words to impersonate a community. For a specific language group, involve a speaker from that audience.

Roman-Urdu spellings vary: one reader writes “nahi,” another “nahin.” Choose a readable convention without treating another spelling as ignorant. For important public information, offer clear English, Urdu script, or a relevant regional-language version instead of assuming Roman Urdu reaches everyone. A low-data voice note supports read-aloud review during load-shedding; never upload identifiable chats or phone numbers as tone examples.

// hands_on

Hands-On Exercise

7 steps

Build your language system and matched content set:

Choose one audience segment and channel. Complete the style card, including pronoun, ratio signal, spelling, English terms, and banned expressions.
Create a glossary of at least eight recurring terms. Define each term and decide whether it stays English or uses one Roman-Urdu form.
Write a five-unit English reference script using only claims you can support.
Run the prompt. Keep both scripts numbered for back-checking.
Repair any literal translation, lost qualification, forced slang, or inconsistent spelling. Read the result aloud and note every changed line.
Ask one consenting reviewer: “Which line would you never say this way?” Record the wording issue, not their identity.
Use the approved card to write three short posts: one spoken-video caption, one carousel line set, and one LinkedIn version. Adjust the ratio by channel without changing the core claim. Done means the style card, glossary, script pair, three posts, and notes can be checked side by side.

// completion_rubric

Completion Rubric

6 checks — tick as you verify

0/6

// sources

Sources

4 official sources — check every claim yourself

// check_yourself

Check yourself

4 questions · answers and options are taken word-for-word from this course

0/4

1 / 4 · diagnose
Your work shows this failure mode: “Switching every few words.” What does the lesson tell you to do about it?