According to Film Music Reporter, Federico Jusid and Lorenzo Perelmuter have teamed up to score Collision Course, the international title of Colisión. The outlet announced the assignment on October 27. Daniel Sánchez Arévalo’s thriller arrives on Netflix on October 30.
The announcement does not describe the score or divide the work between the two composers. I am not going to manufacture that division from the order of their names or the length of their résumés. It does open a useful production question: how can two composers build one score without creating two competing soundtracks?
Two announced composers do not reveal the workflow
Two names associated with a score do not tell us who wrote each cue, established the themes, built the mock-ups or supervised delivery. Different working structures can produce the same announcement.
Composers may divide scenes, collaborate on every thematic idea, or split writing and production responsibilities. One may follow a character group while the other develops a contrasting musical system. They may also work as one studio, exchanging versions until individual boundaries stop being useful.
The published information about Collision Course does not support choosing among those models. The announcement does not provide a daily org chart.
A shared architecture can guide the cue split
A thriller involving several characters can tempt a production to allocate scenes by character or plot line. That may distribute the workload, but distribution alone does not create identity.
Before assigning cues, I would define common principles. How much space should music occupy against suspense, dialogue and effects? Which ideas belong to the film as a whole? Which colours can remain attached to one point of view? When should the score refuse to underline a twist?
A shared score bible can record palette, themes, tempo language, approach to silence and the boundary with sound design. It should not force both composers to write in an identical voice. It should stop every new scene from redefining the film.
Divide problems, not only scenes
The simplest model gives each composer a cue list. It becomes fragile when characters meet, picture changes or an idea introduced in one section must return in another.
I prefer a division that also follows dramatic problems. One composer might carry a thematic family across several sequences. The other might own a tension mechanism or a texture that cuts across plot lines. Responsibilities remain clear without turning the film into sealed blocks.
This needs a common cue tracker. Each row should identify picture version, first-pass owner, status, consolidated notes and thematic material. If a cue changes hands, the receiving composer needs the approved starting point and the reason for the transfer.
Nothing in the available sources establishes that this was the method used on Collision Course. It is a production framework prompted by the announcement, not a claim about the film’s private workflow.
Build one feedback chain
Two composers should not receive two different films by email. Production can consolidate director and producer notes and identify who will resolve conflicting feedback.
Scheduled joint reviews can check thematic continuity, mock-up quality and the way cues hand off to one another. They should not become a permanent committee meeting for every bar. Their value is catching an architectural split while it is still cheap to correct.
Mock-up standards matter as well. A director can mistake a production-quality difference for a compositional difference. A shared template, a small common sound palette and consistent naming reduce that noise in approvals while leaving room for each composer to work efficiently.
Both composers need the same cut naming, change notes and reconform rules.
Make assets portable
A two-composer workflow creates more handoffs. Sessions may depend on different DAWs, sample libraries, plug-ins and routing. Production does not need to impose an identical studio, but the music team needs an exchangeable baseline.
I would define aligned stereo exports, consistent stems, useful tempo maps, required MIDI and a common naming convention. Every file must point to the correct cue and picture cut. The goal is not to archive every creative gesture. It is to let the team resume work without reconstructing context for half a day.
The dub stage also needs one delivery logic. Stem groups should describe comparable musical functions. If each composer splits deliverables according to a different philosophy, the re-recording mixer discovers the org chart at the worst possible time.
Alternates need the same discipline. A no-melody version or reduced-percussion stem must have a clear status. Editorial should know whether it is an approved alternate, an experiment or an obsolete file.
The announcement sits inside an existing professional connection
A 2022 Spanish Screenings guide described Lorenzo Perelmuter as a composer who had worked with Federico Jusid, among other collaborators. That establishes a previous professional connection. It does not establish the hierarchy or division of labour on Collision Course.
The distinction is worth preserving. The guide does not establish a previous co-composition or an equal working relationship. It does not let an outside observer assign authorship scene by scene.
What production should lock
A two-composer score can benefit from five explicit decisions: the musical architecture, cue ownership, the person consolidating notes, technical delivery standards and the precise credit language.
I would add a takeover rule. If one composer is unavailable or a scene changes late, the other needs to know which approved materials can continue and which changes require a fresh creative decision. That protects schedule without blurring authorship.
The Collision Course announcement does not reveal how Federico Jusid and Lorenzo Perelmuter organised their work. It establishes a smaller, verifiable fact: Film Music Reporter says they teamed up to score the film. For producers, that association is a reason to look behind the names. A shared score does not become coherent in the end titles. It becomes coherent through the brief, cue ownership, versions, feedback and deliverables.