How to Plan Live Streaming Services in Mumbai

01

Start from the decision, not the format

The single most useful hour in any live streaming project is the one spent deciding what the viewer must do differently after watching. Broadcast-grade multi-destination streaming with redundant bonded internet. That outcome — a stream that does not drop during the ceo keynote — dictates structure, running time, tone and where the film sits in the funnel. Skip it and you get a technically competent video that nobody can evaluate, because there is no agreed definition of working.

Write the brief in one paragraph: who is watching, what they currently believe, what they should believe afterwards, and the single action that follows. If the brief cannot survive that compression, it is not a brief yet — it is a wish list, and wish lists are what produce four-minute films that nobody finishes.

Agree the success metric in the same session. It changes production decisions immediately: a film measured on completion rate is cut differently from one measured on qualified enquiries, and knowing which one you are making prevents an expensive argument at fine cut.

02

Script, storyboard and the approval chain

Scripting is where cost is controlled. Every structural problem caught on a page costs nothing; the same problem caught in the grade costs a reshoot. We work to a written treatment first — tone, structure, key scenes — then a full shooting script, and both go through the approval chain before any kit is booked.

Map the approval chain honestly at kickoff. In most Mumbai organisations it is longer than marketing admits: brand, legal, the business unit sponsor, and often a regional or global sign-off. Each additional reviewer adds a message to the film and a round to the schedule, which is why nominating one arbiter to resolve conflicting feedback is worth more than any efficiency in production.

Two revision rounds are built into our schedules. Projects that exceed them almost always share one cause: feedback gathered sequentially rather than consolidated. Collect every comment into a single document, resolve internal contradictions before sending, and the two rounds are enough.

03

Recce, permissions and Mumbai's real lead times

The recce is the cheapest insurance in production. An hour at the location tells you where the power is, where the noise comes from, whether the lift takes a lighting stand, and which window has the sun at 3pm. Most Mumbai schedule overruns trace back to a location nobody visited beforehand.

Permissions vary enormously by area and issuing authority — municipal wards, estate managers, MIDC gate offices, MMRDA, railway or port authorities, and DGCA for anything airborne. Lead times run from two days for a private estate to three weeks for institutional or municipal exteriors, so filing happens in week one, in parallel with scripting, not after script lock.

04

Crew, kit and what actually needs to be on the call sheet

The crew list should follow the brief, not the invoice. For live streaming the working core is stream director, vision mixer, audio engineer, network engineer, built around atem constellation, liveu bonded uplink, backup 5g. Adding roles beyond that is justified when the film needs controlled light, live sound with multiple speakers, or art direction — and not otherwise.

Kit is the least important variable in the finished film and the one clients ask about most. A senior DOP with a mid-range camera package produces better work than a junior operator with a flagship body, every time. Spend the argument on people.

• Confirm on the call sheet: Live programme is in scope.
• Confirm on the call sheet: Recorded ISO masters is in scope.
• Confirm on the call sheet: Chaptered VOD is in scope.
• Confirm on the call sheet: Analytics report is in scope.

05

Building a schedule that survives Mumbai

Mumbai imposes three constraints on any schedule: traffic, monsoon and access windows. Call times get set against the local peak pattern, not a generic 9am; exteriors between June and September carry a weather contingency day; and buildings with restricted service-lift hours dictate when gear can move, which in turn dictates when you can actually roll.

Build the schedule backwards from the delivery date, then add the review dates as fixed calendar entries with named owners. Publishing the review dates at kickoff is the single highest-leverage scheduling habit we have: it converts "we're waiting on feedback" from an excuse into a visible, dated dependency.

06

Delivery, versioning and handover

One master is not a delivery. Every channel has its own aspect ratio, duration ceiling, caption behaviour and loudness spec, and a film exported once for all of them performs worse everywhere. Agree the version list at brief stage so it is scoped and priced rather than requested as a favour after delivery.

Handover should include an asset index — file names, durations, aspect ratios, where each version is meant to run, and the caption files. Six months later, when someone new inherits the campaign, that index is the difference between reusing the footage and reshooting it.

07

How to measure whether it worked

Most video budgets in Mumbai are approved without a success metric, which is why the second film is always harder to get signed off than the first. Decide the number before production starts and instrument for it: view-through rate at 25, 50 and 75 per cent tells you where the script loses people; click-through and assisted conversions tell you whether the proposition landed; and for internal work, completion rate against a training or onboarding cohort is the only figure that matters.

Set the benchmark honestly. A live streaming asset placed on a landing page above the fold behaves nothing like the same cut running as paid social, and comparing the two produces a false conclusion. We publish expected ranges with the delivery so the marketing team is not benchmarking a 90-second explainer against a six-second bumper.

Review at 30 days, not at launch week. The first week's numbers are dominated by internal traffic and paid burst spend. The 30-day picture is what tells you which cutdown to fund next, which thumbnail to replace, and whether the opening ten seconds needs a re-edit — a cheap fix that regularly doubles retention without a reshoot.

08

Where these projects go wrong

Failed video projects in Mumbai rarely fail on craft. They fail on decisions made before anyone picked up a camera — an unclear owner, a brief written as a format, a review chain nobody mapped. The pattern is consistent enough that we plan against it explicitly, and it is worth checking your own project against the same list before you commission anything.

The most expensive of these is the late approver. A stakeholder who appears at fine cut with a structural objection is not asking for a revision, they are asking for a reshoot, and by then the crew is on another job and the location is booked out. Naming one arbiter at kickoff is free and saves more money than any negotiation on day rates.