BBTL MARKETING CO.

Guide · 11 min read · Updated 2026-10-04

How to Plan a Street Play (Nukkad Natak) Campaign: Step-by-Step Guide

A practical, sequenced guide to planning street play (Nukkad Natak) in India — objectives, locations, permissions, team training, live reporting and what to measure before you scale.

Quick answer

To plan street play (Nukkad Natak): fix one measurable objective, pick venues where your audience already is, secure permissions in the 3–15 working days they typically need, train the team before day one, run with daily reporting, then scale only the locations that beat your cost-per-outcome target.

How to Plan a Street Play (Nukkad Natak) Campaign: Step-by-Step Guide

Key takeaways

  • One objective, one primary KPI, decided before the venue is booked
  • Permissions are the critical path, not a parallel task
  • Train and mock-pitch the team before day one, not on it
  • Report daily; review and reallocate weekly

Step by step

  1. 1

    Script & local-language adaptation (Days 1-6)

    Write the script around the message and adapt it to the local dialect rather than translating a standard version.

  2. 2

    Casting & rehearsal (Days 5-12)

    Cast and rehearse performers to a fixed running time, closing with a run-through validated by team members from the catchment.

  3. 3

    Location permissions (Days 8-16)

    Secure market committee, panchayat, society or campus permission for each location on the touring schedule.

  4. 4

    Performance circuit (From go-live)

    Run the touring schedule with geo-tagged, performance-wise reporting rather than a single aggregate count.

  5. 5

    Message-recall review (After the circuit)

    Check recall and, where relevant, enquiry capture against the plan, and adjust the script or route for any leg that underperformed.

What is street play (Nukkad Natak)?

A street play, or nukkad natak, is a short, live theatrical performance carrying an awareness or product message, staged in the open at a market, haat, society or campus rather than on a conventional stage. It holds a crowd's attention considerably longer than a direct pitch because people stay to watch a story resolve, which is why it is the standard format for awareness, CSR and rural messaging where a demonstration or sampling pitch would struggle to hold an audience at all.

A performance narrative gives bystanders a reason to keep watching that a sales pitch does not, and because the message is delivered inside a story rather than stated directly, it is retained and repeated by word of mouth after the performance ends. Running the script in the local dialect rather than a translated version is what makes that retention work in practice, since a translated script reads as an outsider's message and a dialect script reads as something the audience's own community is saying.

Most media plans treat it as one line inside a bigger BTL programme rather than a standalone channel, which is why the steps below assume it is being planned alongside at least one other touchpoint rather than in isolation.

Who it reaches, and where

Street Play (Nukkad Natak) reaches market shoppers, residents and rural audiences who stop to watch a live performance, reached through story rather than a direct pitch At the venue level, a weekly haat or mela day typically produces somewhere in the 600–2,500 contact range — a planning assumption for sizing the team and stock, never a promise.

Different venue types in the list below are not interchangeable stand-ins for each other; each one reaches a different slice of the audience at a different volume, which is why the venue mix should be chosen from this list rather than defaulted to whichever location is easiest to book.

  • Haat or mela — 600–2,500 contacts on a typical day
  • Market canopy — 250–900 contacts on a typical day
  • Residential society — 120–400 contacts on a typical day
  • College campus — 500–2,000 contacts on a typical day

When to run it

Response and cost both move with the calendar. For street play (Nukkad Natak), the window that matters most is October to February — post-harvest liquidity makes rural routes most productive

Running outside that window does not make the format ineffective, but it does change what a realistic target looks like, and a plan built on the wrong season's numbers reads as underperformance that is really just a mismatched calendar.

The lead times below are working days, not calendar days, and they assume the brief does not change mid-process — a venue swap or a last-minute city addition resets the clock on whichever row it touches, which is the single most common reason a quoted timeline slips.

Lead time by rollout size
RolloutWorking days needed
Permissions alone3–15
Single-city pilot5–10
Custom fabrication10–25
Regional rollout14–21
National rollout21–45

Formats to choose from

A complete brief should name the format before it names the venue. The formats below cover most briefs for street play (Nukkad Natak); pick one or two to pilot rather than trying all of them at once.

Running more than two formats in a first pilot is rarely a sign of ambition — it is usually a sign that the objective in step one was never actually narrowed down.

  • Market and haat performances — A short play staged in an open market or weekly haat, timed to the hours when footfall is naturally highest.
  • Society and campus performances — The same format adapted for a gated-society common area or a college campus, where the crowd is more captive than an open market.
  • CSR and government-scheme messaging — Scripts built around a public-health, safety or scheme-awareness message, commissioned by a brand, NGO or government programme.
  • Multi-location circuit — The same cast and script performed across several locations on a touring schedule, so one production serves many towns or villages.

What a pilot like this should produce

Before the team goes live, write down what the numbers above should produce — it is the only way to tell on day three whether the campaign is underperforming or the plan was wrong.

Expected output of the 8-day pilot

12,400 contacts at a haat or mela, converted through the planning ranges in figures.ts.

Contacts engaged
12,400
Leads captured (8%–22% of contacts, mid-point)
1,860
Leads qualified (45%–70% of leads, mid-point)
1,070

At a ₹1,49,600 ex-GST budget, that is ₹80 per lead before any lead has been verified as a sale.

Treat these as planning ranges to size the team and stock against, not as a guarantee — the actual report should replace every one of these numbers with what was measured.

Reviewing the pilot before you scale it

A pilot exists to be reviewed, not just run. Compare the actual numbers against the example above stage by stage — contacts, then leads, then qualified leads — rather than only at the final cost-per-lead figure, because the stage where the real number diverges from the plan is what tells you what to fix.

A shortfall at the contacts stage points at the venue or the day; a shortfall at the leads stage, with contacts on target, points at the pitch or the team; and only a shortfall at the qualified stage, with the first two on target, is actually about lead quality rather than lead volume.

Staffing the pilot correctly

The team sizing used above — 2 senior promoters, 4 promoters, 1 supervisor and 1 technician — is not arbitrary; it follows a ratio that keeps someone accountable for the venue rather than spreading a roster thin across more ground than it can cover.

Understaffing a venue is the fastest way to turn a sound plan into a disappointing report, because a thin team cannot both hold a pitch and capture data at volume — under pressure, data capture is usually the one that gets dropped first, and it is the one the report depends on.

Overstaffing has its own cost, just a quieter one: a team larger than the venue's contact volume can support simply raises the manpower line without raising the contacts, leads or qualified leads it is measured against.

Permissions and compliance to plan for

The biggest single risk in street play (Nukkad Natak) is permissions and compliance slipping the launch date, not the creative or the team.

Each item on the list below sits with a different authority or counterparty, and they rarely move in parallel — a missing document for one often blocks the filing for the next, which is why the sequence matters as much as the list.

  • Market committee, panchayat, society or campus permission per performance location
  • Amplified-sound permission where the performance uses a public-address system
  • Content clearance where the message is government, CSR or health-related
  • Performer safety and crowd-stewarding plan for an open, unticketed audience

Work backwards from the build date

Permissions alone typically take 3–15 working days. File from the build date backwards, not the go-live date forwards, or the schedule looks fine right up until it is not.

Mistakes that sink the plan

Most of the failures below are not creative failures — they are planning failures that show up on site.

Each one is specific enough to check against your own plan directly, which is the point — a generic warning to "plan carefully" has never once prevented any of these from happening.

  • Translating a standard script instead of writing it in the local dialect
  • Scheduling a performance at an hour the target audience is not actually present
  • Reporting a touring circuit as one aggregate number, which hides locations that were skipped
  • A message buried inside entertainment so thoroughly that nobody recalls what it was for
  • No crowd-stewarding plan for an open audience with no ticketing or seating

The brands that lose their street play (Nukkad Natak) launch date almost always lose it to a permission, not to the weather.

What to measure before you call it a success

Pick one of these as the primary KPI before go-live; the rest are context, not the scoreboard.

Writing the primary KPI down before the venue is booked is what stops a mid-campaign redefinition of success — the temptation to report the number that looks best is strongest exactly when the chosen one is underperforming.

A second, smaller campaign measured against a different primary KPI than the first is not comparable to it, however similar the two look on paper — decide the metric once, early, and keep it fixed across every pilot you want to compare against this one.

  • Locations and performances completed against the touring schedule
  • Audience size gathered and retained through the full performance
  • Message recall among bystanders after the performance
  • Enquiries or leads captured where a data-capture step follows the performance
  • Geo-tagged, performance-wise proof filed per location

Planning street play (Nukkad Natak)?

Get an itemised plan and quote from BTL Marketing Co. within 24 hours.

Frequently asked questions

How much does street play (Nukkad Natak) cost in India?+

Indicative pricing is ₹15,000 – ₹1.5L per show. The final quote moves with the cities chosen, the number of days, team size, fabrication and the permissions each venue needs, so ask for an itemised breakup rather than one lump-sum figure.

How quickly can street play (Nukkad Natak) go live?+

A single-city pilot can go live in 5–10 working days. A regional rollout across several cities typically needs 14–21 working days once permissions and fabrication are built into the schedule.

Which Indian cities can run street play (Nukkad Natak)?+

Street Play (Nukkad Natak) can be planned in any of India's 70 tracked cities, including Mumbai, Delhi, Gurgaon, Noida, Bangalore, Hyderabad, with tier 2 towns quoted on request.

Why is a street play used instead of a direct pitch for awareness messaging?+

A story holds an audience far longer than a pitch does, and a message delivered inside a narrative is remembered and repeated after the performance ends, which is exactly what a CSR or public-health campaign needs. A direct pitch on the same topic would lose the crowd within a minute.

Does the script need to be in the local language?+

Yes, in the actual dialect rather than a translation of a standard script. A translated script reads as an outside message; a dialect script reads as something the audience's own community is saying, which is central to why the format earns word-of-mouth repetition.

How many locations can one touring production cover?+

It depends on travel time between locations and performance length, which is why the touring schedule is built around realistic travel windows rather than a fixed number of stops, and why coverage is reported location by location rather than as a single circuit total.

When does a street-play campaign work best?+

Typically in the post-monsoon rural window, roughly October to February, when post-harvest liquidity and village gathering patterns both favour an open-air performance over other formats.

How long does a street play (Nukkad Natak) pilot take from brief to report?+

Count 3–15 working days for permissions, running in parallel with sourcing and training, then the activation days themselves, then a short review window — a single-city pilot typically closes inside the 5–10 working-day window quoted for it.

What is the most common reason a street play (Nukkad Natak) pilot underperforms?+

An objective that was never narrowed to one measurable KPI before the venue was booked. Everything downstream — which format, which venue, how the team is briefed — is easy to get right once the objective is specific, and hard to get right by accident when it is not.

Can the same team run more than one venue in a day?+

Only if the venues are close enough that travel time does not eat into the activation window, and only with a supervisor at each location — a team that splits across venues with no one accountable at either one tends to lose the thing this guide is built around: a trained pitch and reliable data capture.

What should change between the first pilot and the second city?+

Whatever the first pilot's report actually showed, not a generic assumption of what should work better. A second city run on exactly the same plan as the first is a second data point; a second city run on a plan that was never updated by the first pilot's findings has wasted the entire point of piloting.

Powered by IRPR