This case study documents a 10-day, multi-state film shoot across Kashmir, Rajasthan and Delhi for Indonesian production house Falcon Pictures on the feature Titik Nol. It is a technical reference for producers and production executives who need to understand how compressed multi-state Indian schedules are actually structured and delivered — how three shooting zones absorb risk across geography, how a line producer India holds a schedule together under compressed timelines, and how decisions made in pre-production determine whether a shoot survives its most difficult days.
Why This Production Required a Different Scheduling Model
Executing a multi-state shoot in India within a severely compressed timeline is not a function of logistics alone. It is a test of planned sequencing, production hierarchy, and risk management across geography. For international productions entering India—particularly those operating outside familiar regulatory, climatic, and security environments—the role of a line producer India shifts from coordination to production architecture.
Titik Nol was a 10-day, three-state shoot for Falcon Pictures, the Indonesian production house behind the feature film Titik Nol (IMDb). The production covered Kashmir, Rajasthan, and Delhi across a single compressed schedule — three states with distinct operational profiles, managed as one unified sequence. Cross-border collaboration, politically sensitive regions, and seasonal constraints ran in parallel across all three zones.
The production was structured around three operational zones — a model used in high-risk, multi-jurisdictional shoots where each state carries a distinct function beyond its geography. Each zone carried a specific operational role, defined not by geography alone but by what it could reliably deliver under pressure — continuity, scale, authenticity, or recovery.
The project was executed with Manav Paul serving as Co-Producer, overseeing line production workflows, on-ground logic, and inter-state coordination. Pre-production logistics — vendor sourcing, equipment movement, and crew deployment — were coordinated through a line producer Mumbai base before units dispersed across the three shooting zones. From a production standpoint, this role was critical in aligning the creative requirements of an international director with the operational realities of filming across India’s most logistically and politically complex regions.
Why the Production Was Structured Across Three Zones
Titik Nol was developed by Falcon Pictures, one of Indonesia’s leading production houses, with a strong commercial and international distribution footprint. The decision to shoot extensively in India was driven by narrative requirements—landscape diversity, cultural density, and visual contrast—but executing this vision within a 10-day window required a departure from standard location-by-location sequencing.
India offers extraordinary visual and geographic diversity, deep crew and technical talent pools, but highly fragmented permissions, climate volatility, and regional governance differences that demand a different production architecture than most international markets.
The focus here is production mechanics — how a schedule gets designed to survive real-world constraints instead of assuming ideal conditions.
Most published production breakdowns focus on what was shot and where. This document focuses on how the schedule was built, and why specific decisions were made under time pressure.
The schedule was worth examining for four compounding reasons. Completing a multi-state shoot in 10 days is not exceptional by Indian standards — but doing so across Kashmir, Rajasthan, and Delhi with international stakeholders and security dependencies requires a different production philosophy. Kashmir is not merely a remote location; it is a location-bound risk environment, while Rajasthan presents scale, crowd, and daylight challenges, and Delhi functions as both opportunity and constraint due to density, security zones, and administrative layering. The production was also designed from the outset assuming things would go wrong — missed shots, weather loss, access delays, and crowd volatility were expected variables, not exceptions, and fallback logic was prioritised over ideal sequencing. Finally, with a foreign production house and global distribution expectations, delivery had to meet international benchmarks of predictability, documentation, and accountability despite operating within India’s unpredictable production environment.
Zone-Based Planning vs. Location-by-Location
A defining feature of this project was the rejection of a traditional “location-by-location” schedule. Instead, the production structured the shoot into three operational zones, each carrying a distinct function. Rajasthan was designed as a multi-role base and backup zone, capable of absorbing creative, logistical, and continuity pressure — functioning as a planned fallback for terrain, crowd, and character geography beyond its primary story locations. Kashmir was treated as an irreplaceable capture zone, where only scenes that could not be approximated elsewhere were scheduled, minimising exposure to weather, security, and access volatility. Delhi operated as the continuity and recovery hub, absorbing missed scenes, hosting interior cheats, executing high-load technical days, and providing administrative control throughout the schedule.
This zone-based approach allowed the production to redistribute risk across geography, instead of concentrating it on individual shooting days.
Pre-Built Recovery vs. Reactive Fixing
A common failure point in multi-state Indian shoots is reactive problem-solving—attempting to fix issues on the same day, in the same location, under worsening conditions. This production deliberately avoided that approach.
This required pre-approved alternate locations, pre-matched continuity environments, a clear separation of irreplaceable versus replicable scenes, and centralised recovery mechanisms routed through Delhi — all decisions made before the first shooting day, not during it.
As a result, when daylight was lost, crowds became unmanageable, or weather intervened, the production did not stall. It re-routed.
Each phase illustrates how planning translates into delivery under real-world pressure — balancing creative ambition with operational reality.
This breakdown is a technical reference, not a promotional narrative—designed for producers, studios, and production executives seeking to understand how complex, multi-state shoots in India are actually delivered.
Why Rajasthan Was Scheduled First
Rajasthan was deliberately designed not as a singular filming destination, but as a distributed operational base capable of serving multiple purposes simultaneously. It functioned as the primary story location for early narrative progression, as geographic and visual backup for politically and climatically sensitive regions, and as a timeline recovery buffer to absorb losses later in the schedule.
This multi-role design ensured Rajasthan contributed value beyond its own shooting days, acting as a stabilizing force for the entire production.
Operational Logic: Front-Loading the Schedule
Engaging a line producer Rajasthan at the front end of the schedule was a decision driven by operational control, not creative preference. Compared to Kashmir, it offered decentralised permissions with faster local coordination, efficient inter-city connectivity across the Jaipur–Pushkar–Ajmer–Jodhpur–Jaisalmer corridor, high visual diversity within manageable travel radii, and enough operational tolerance to reshuffle days, scenes, and units without cascading delays.
This made Rajasthan the optimal environment to front-load scenes carrying higher logistical weight while preserving flexibility for later, higher-risk locations. The approach allowed the production to test workflows, calibrate crew rhythm, and validate fallback systems before entering restricted zones.
Jaipur: Daylight Risk and Recovery Design
The shoot commenced in Jaipur during winter, a period when compressed daylight windows create predictable exposure risk. Instead of attempting to maximize output per day—a common mistake in short schedules—the plan prioritised loss containment.
Every exterior daylight scene was pre-mapped with a Delhi-based alternate, with blocking, lensing, and camera height matched in advance. Art direction, wardrobe states, and performance continuity were logged for redeployment — so a lost Jaipur day could be absorbed in Delhi without visible discontinuity.
When an exterior sequence was lost to early sundown, the unit did not attempt forced completion or overtime recovery. The scene was immediately reassigned to a daylight-safe Delhi location later in the schedule.
This decision avoided cascading delays, crew fatigue, and quality compromise. Daylight losses should never be recovered within the same location—recovery must be deliberate, not reactive.
Pushkar: Time-Bound Cultural Capture
Pushkar introduced a fundamentally different challenge. The mela is a non-repeatable, time-bound cultural event, meaning failure carried no recovery option. The strategy therefore prioritised authentic capture over coverage volume.
Newly constructed infrastructure that conflicted with the film’s 1990s timeline was rejected in favour of an older, smaller bus stop that aligned visually and logistically. Dialogue scenes were positioned on the periphery of the mela rather than within peak-density zones, and short zoom inserts with establishing shots conveyed scale without requiring prolonged crowd engagement.
This approach minimized interference with the event, reduced security exposure, and preserved realism. Crucially, it allowed the unit to capture the essence of Pushkar without attempting to control it—a distinction that often determines success in live cultural environments.
Jaisalmer: Kashmir Backup Engineering
Jaisalmer was never treated as a standalone desert location. From the outset, it was scouted and approved as a structural backup for Kashmir, particularly for sequences involving movement, travel, and character transition.
The selection criteria were operational: terrain overlap capable of doubling for rugged northern routes, casting availability that could plausibly support cheat geography, and controlled environments suited to interior vehicle and bus sequences that Kashmir’s access constraints would have made difficult.
Several complex interior and road-based scenes were executed in Jaisalmer, significantly reducing dependence on Kashmir’s limited weather and access windows. When Kashmir later imposed tighter shooting constraints, this prior work proved decisive in maintaining narrative continuity.
Ajmer and Jodhpur: Density and Scale Management
Ajmer was deployed for high-density, dialogue-driven scenes set within narrow lanes and food joints. Instead of attempting crowd lock-ups, the plan embraced natural density — short takes with selective coverage, rapid resets without disrupting pedestrian flow, and ambient energy used as a production asset rather than a problem to suppress.
Jodhpur introduced a different challenge: scale without congestion, particularly at Mehrangarh Fort. The rear sections of the fort were selected, tourist entry points bypassed entirely, and visual scale preserved through framing and movement rather than crowd control.
This allowed the production to achieve architectural grandeur without operational friction.
Outcome of the Rajasthan Phase
By the close of the Rajasthan phase, all high-risk crowd-dependent scenes were complete, critical backup material had been captured to protect the Kashmir schedule, and schedule elasticity had been preserved — leaving the production with room to recover without creative compromise in the phases ahead.
Rajasthan, therefore, functioned not merely as a filming location, but as a scheduling backbone—absorbing risk, enabling fallback, and stabilizing the overall production workflow.
Why Kashmir Required a Separate Regulatory Track
The line producer Kashmir engagement was structured as a location-bound shooting window — only scenes that could not be recreated elsewhere were assigned to this cluster. This is a critical distinction in line production strategy.
Kashmir: Operational Constraints
Kashmir carried four compounding constraints: harsh and unpredictable climate, security clearances involving armed forces, restricted movement zones, and limited daily shooting windows. Each of these operated independently, but their combination made scheduling in Kashmir fundamentally different from any other phase of the production.
Diplomatic and Ministerial Clearances for Foreign Crews
In this case, Kashmir carried an additional layer of complexity due to the involvement of a foreign production house and non-Indian crew members. Unlike standard domestic shoots, foreign productions operating in politically sensitive regions fall under the purview of the Ministry of External Affairs, with mandatory coordination through the Indian Mission (Indian Embassy) relevant to the producer’s home country.
For this production, regulatory clearance did not fall within the standard operational scope of the Film Facilitation Office (FFO). By virtue of the crew being non-Indian and the project qualifying as a biopic / non-fiction narrative, approvals were required directly from the Ministry of External Affairs (MEA), with formal involvement of the Indian Mission (Indian Embassy) in the producer’s home country.
In such cases, the FFO does not act as an approving authority. Its role is limited to routing documentation, and applicants are formally redirected to the MEA process. Importantly, initiating an application through the FFO without prior regulatory clarity carries a material risk: the FFO application fee is non-refundable, even when the project is subsequently deemed outside its mandate.
MEA vs FFO: Where Most Foreign Productions Go Wrong
MEA approvals for foreign productions — particularly those involving border-sensitive regions such as Kashmir, military-adjacent environments, or politically contextual narratives — require script screening and content vetting, crew nationality verification, embassy-level coordination, inter-ministerial consultation, and extended security review timelines.
Under normal circumstances, this process can take up to three months, independent of production schedules or location availability.
Regulatory Advantage Through Prior Experience
Manav Paul drew on prior experience navigating MEA-led approvals to avoid misrouting the application, eliminate redundant submissions, and prevent delays caused by approaching incorrect authorities in Delhi. This ensured that regulatory clearances progressed in parallel with technical pre-production, instead of becoming a downstream bottleneck.
In high-sensitivity regions like Kashmir, this regulatory foresight is not an administrative detail—it is a critical scheduling dependency. Missteps at this stage can halt a production entirely, regardless of creative readiness or logistical preparedness.
At this stage, the co-producer role moved beyond logistics into procedural navigation. Experience with Delhi-based ministerial workflows ensured that the production engaged the correct authorities from the outset, avoiding common delays caused by approaching parallel or non-jurisdictional departments. This eliminated trial-and-error engagement and prevented unnecessary escalation loops within Delhi’s administrative ecosystem.
Compressing Approval Timelines Through Procedural Accuracy
By structuring the clearance pathway correctly—ministerial first, operational second—the production was able to compress approval timelines, align security expectations early, and lock Kashmir shooting windows with confidence instead of assumption. In a border-sensitive region, this distinction directly determines whether a shoot proceeds on schedule or collapses under regulatory uncertainty.
Given these factors, the Kashmir schedule was designed around irreplaceability, not volume.
Interior vs Exterior Segregation
A key decision was to exclude all interior continuity from Kashmir wherever possible. Interiors were recreated later in Delhi, matched for light direction, window placement, and art textures, and logged meticulously during location recce to ensure clean continuity across the cut.
Kashmir was reserved for mountain roads, high-altitude exteriors, military-adjacent environments, and atmospheric establishing shots — material that could not be replicated or approximated in either Rajasthan or Delhi.
This segregation reduced exposure to weather delays and minimized security dependencies.
Armed Forces and Local Fixer Coordination
Movement operated through pre-approved corridors with armed escort coordination and embedded local fixers carrying both terrain knowledge and protocol expertise. Daily call sheets were finalized only after security confirmations, and shot lists were prioritized based on access volatility rather than creative preference.
Why Kashmir Days Stayed Flexible
Because backup material had already been captured in Rajasthan, the director was given greater freedom to improvise in Kashmir. This is a subtle but important outcome of strong line production: creative freedom increases when production risk is absorbed before the shoot starts.
Several rugged road sequences initially planned for Kashmir were reassigned to Jaisalmer footage, allowing the Kashmir days to focus on visually unique material.
Weather and Continuity Management
Mountain tops and rugged terrain were captured early each day before weather shifts set in. The schedule ran on early call times, minimal company moves, and a reduced lighting footprint — each a deliberate constraint to keep the unit mobile and the shooting window protected.
Continuity was preserved by ensuring that wardrobe and vehicle states matched pre-shot Rajasthan material, enabling clean intercutting.
By the end of the Kashmir phase, the production had captured all non-replicable visuals without overextending the unit or risking schedule collapse.
Why Delhi Closed the Schedule
Delhi functioned as the operational backbone of the entire shoot — not just another filming city, but the continuity and compliance fallback for all material that could not safely or predictably be executed in Kashmir. Missed scenes, interior continuity, high-load technical days, and infrastructure-heavy sequences were all routed through Delhi as a matter of pre-production design, not reactive adjustment.
Delhi Day Structure: Interior Cheats and Recovery
Delhi was positioned as the final shooting block for deliberate reasons. The city offered architectural doubles for both Kashmir interiors and Rajasthan street environments, which meant scenes that couldn’t be captured in their primary locations could be recreated without breaking visual continuity.
The schedule opened at Chandni Chowk market, where the unit covered exterior street scenes alongside hostel interiors dressed to match Kashmir reference footage. A daylight scene lost in Jaipur was recovered here within the first 48 hours — reconfirming the value of pre-matched location documentation carried forward from the Rajasthan phase.
The most technically complex single day involved early morning monastery scenes followed by a full booking at Dilli Sarai railway station. Separate train bogies were dressed as India and China interior environments, requiring coordinated art department, camera, and continuity teams working within a single unbroken window. All departments ran simultaneously. The sequence completed without spillover, and the schedule held.
This day demonstrated what Delhi’s infrastructure uniquely enables: high-load coordination across multiple departments and locations within a compressed urban window — a capability that no other city on this schedule could have replicated.
The Final Buffer Day
The most demanding day in the Delhi block combined school interiors, hospital scenes, and a controlled explosion sequence. A remote Greater Noida location was selected for the pyrotechnic work, reducing urban permit risk and providing sufficient buffer zone for the safety team. All departments were synchronized across three environments. The unit shot until 1:00 AM and completed without schedule spillover.
The final day of the schedule had been deliberately left unassigned — a planned buffer, not an afterthought. Its non-use is the clearest indicator of controlled line production: a 10-day multi-state shoot that ended with a rest day intact rather than a recovery session. For international productions evaluating India as a filming territory, an unused buffer day is more informative than any crew testimonial — it quantifies what professional pre-production discipline looks like at scale. Film fixers in India operating at this level build buffer into the schedule as an architectural decision, not a contingency guess.
Titik Nol demonstrates that effective line production in India is not defined by speed, but by the ability to design delivery systems that absorb uncertainty without compromising creative intent.
Rajasthan functioned as the continuity and backup engine that kept the schedule recoverable. Kashmir was treated as an irreplaceable, tightly scoped capture zone reserved only for non-replicable material. Delhi absorbed continuity, compliance, and compression under controlled conditions, delivering the production’s most technically demanding days without the volatility of the northern phases.
A line producer working in India succeeds by anticipating risk before it appears on a call sheet—distributing exposure across locations, timelines, and permissions instead of concentrating exposure on a single geography. This approach is essential for any multi-state film shoot in India, and reflects the broader role of a line producer in India operating across jurisdictions with competing regulatory and logistical demands — particularly when projects involve foreign crews, security-sensitive regions, or compressed schedules.
This project was completed not because conditions were favorable, but because the production framework was resilient by design. It reflects the operational standard now required for serious multi-state filmmaking in India—and sets a benchmark for how professional line production should be evaluated by international studios, OTT platforms, and large-scale production houses. The full network of line production territories India maps how this execution model scales across every major production corridor in the country.
