S6E18 · Starship Mine graph

Picard authorizes sweep despite Worf’s warning

On the Bridge, Picard is immediately besieged by Geordi and Worf as the ship prepares for evacuation. Geordi warns that the Enterprise’s high baryon particle levels may require a stronger-than-normal sweep, risking system overloads, while Worf urgently requests authorization to disable command functions during the sweep. Picard, under extreme time pressure, prioritizes Worf’s security concerns over Geordi’s engineering warnings, authorizing the sweep despite the potential risks. The moment underscores Picard’s tactical focus on immediate threats—here, the baryon sweep—while revealing his tendency to defer to Worf’s security instincts over Geordi’s technical expertise. Just as Picard exits to take Orton’s call, Worf’s request to skip the reception (granted) contrasts with Geordi’s denied request, exposing a subtle but telling hierarchy in Picard’s leadership. The scene crystallizes the crew’s fractured priorities and Picard’s burden of balancing competing crises under duress.

Plot Beats

The narrative micro-steps within this event

1

Picard authorizes the disabling of command functions in preparation for the baryon sweep, while Worf informs Picard of an incoming message from Administrator Orton.

serious to business

Who Was There

Characters present in this moment

8

Controlled urgency, tinged with mild frustration at the competing demands on his time, but masking deeper anxiety about the potential risks of the sweep.

Captain Picard is immediately confronted by Geordi and Worf upon entering the bridge. He listens to Geordi's technical concerns about the baryon sweep and Worf's security authorization request, then makes a rapid decision to prioritize Worf's request, authorizing the sweep via the computer. He then grants Worf permission to skip the reception but denies Geordi's similar request, before exiting to take Administrator Orton's call in the Ready Room.

Goals in this moment
  • Efficiently resolve the competing requests from Worf and Geordi to maintain ship security and readiness for the baryon sweep.
  • Authorize the sweep and disable command functions within the required timeframe, adhering to protocol.
  • Excuse himself to handle the urgent incoming call from Administrator Orton.
Active beliefs
  • Security threats to the ship during the sweep are more immediate than potential system overloads.
  • Chain of command and protocol must be followed, especially during time-sensitive crises.
  • Not all senior staff can be excused from diplomatic duties without causing offense.
Character traits
decisive under pressure tactically pragmatic authoritative diplomatic fair but hierarchical
Follow Jean-Luc Picard's journey

Professionally resolute, then visibly pleased and smug after successfully securing his personal excuse from the reception while Geordi is denied.

Worf requests Captain Picard's authorization to disable command functions during the baryon sweep, citing the computer's need for Picard's authorization. After Picard grants his initial request, Worf then requests and is granted permission to be excused from Commander Hutchinson's reception. He shows satisfaction after being excused and gives a 'dirty look' at Geordi's frustration.

Goals in this moment
  • Secure Picard's authorization for the safe disabling of ship command functions per protocol.
  • Obtain personal permission to skip the diplomatic reception, which he finds undesirable.
Active beliefs
  • Strict adherence to authorization protocols is essential for ship safety during a critical procedure.
  • His personal dislike of diplomatic functions is a valid reason to seek an excuse.
Character traits
protocol-driven tactically focused deferential to authority self-interested triumphant
Follow Worf's journey

Professionally worried, then deflated and annoyed after being overruled and Denied his request.

Geordi La Forge urgently presents his engineering concerns to Picard. He warns that the Enterprise's high baryon particle levels may require a stronger-than-normal sweep, risking overloads on the installed field diverters, and requests additional time to install protective units. He is courteous when interrupted by Worf, but is ultimately denied his own request to be excused from the reception, leaving him visibly frustrated.

Goals in this moment
  • Secure authorization for additional field diverters to protect key systems from potential baryon sweep overload.
  • Obtain permission to be excused from the reception to oversee engineering preparations.
Active beliefs
  • The safety of the ship's systems is paramount and must be prioritized over diplomatic niceties.
  • His technical assessment of the increased risk is accurate and requires immediate action.
Character traits
technically precise proactive respectful of hierarchy frustrated
Follow Geordi La …'s journey
Supporting 3

Not applicable; Data is an android and does not experience emotions. His state is one of neutral, analytical observation.

Data enters the bridge with Picard and observes the last stages of the frenetic shutdown. He does not speak during this event, standing as a silent, observing presence amidst the urgent exchanges between Picard, Geordi, and Worf.

Goals in this moment
  • Observe and catalog the ongoing chain of command and decision-making process.
  • Await orders or opportunities to contribute relevant information.
Active beliefs
  • The Captain will issue orders as needed; his role is to be ready to execute them.
  • Factual information, not emotional reaction, is the appropriate response in a crisis.
Character traits
observant patient non-interfering
Follow Data's journey

Focused and industrious, with a sense of controlled urgency common to routine emergency procedures.

Unidentified Bridge Crew are in the final stages of shutting down their consoles as part of the evacuation preparations. They provide the backdrop of operational urgency, a silent chorus of busy bodies physically executing the orders and protocols for the baryon sweep.

Goals in this moment
  • Complete the secure shutdown of their respective stations in time for the baryon sweep.
  • Avoid interference with senior officers' discussion.
Active beliefs
  • Their duty is to complete the assigned shutdown without question.
  • Following standard protocol is the best way to ensure ship safety during the sweep.
Character traits
efficient procedure-oriented background presence
Follow Unidentified Bridge …'s journey

Not applicable; machine.

The USS Enterprise-D Computer verbally acknowledges and processes Picard's authorization and command. It responds to his verbal command with a confirmation, serving as the tool through which Picard executes the decision to disable command functions, highlighting the technical interface between command intent and ship operation.

Goals in this moment
  • Correctly process and acknowledge Captain Picard's authorization command.
  • Execute the disablement of command functions at the specified time.
Active beliefs
  • None; the computer operates on programmed logic and procedural commands.
Character traits
responsive precise neutral authority-based
Follow USS Enterprise-D …'s journey
Hutchinson

Commander Hutchinson is mentioned by Worf as the host of the reception. Picard also mentions him, expressing a wish to …

Orton

Administrator Orton is mentioned as sending a priority message to Captain Picard from Arkaria Base. This message interrupts the bridge …

Objects Involved

Significant items in this scene

7
Enterprise-D Bridge Mission Ops Station (Worf's Primary Console)

Worf’s console serves as the communication hub for the bridge during this event. It beeps sharply with the incoming message from Administrator Orton, interrupting the discussion between Picard, Geordi, and Worf. Worf relays the message to Picard, who immediately exits to the Ready Room to address it. The console is a functional but unobtrusive element, its beep a stark reminder of the external pressures facing the crew. Its role is to facilitate communication, but in this moment, it also symbolizes the disruption of institutional demands amid a crisis. The console’s beep is the catalyst for Picard’s departure, shifting the dynamic on the bridge.

Before: Worf’s console is active and fully functional, monitoring …
After: Worf’s console remains active but is no longer …
Before: Worf’s console is active and fully functional, monitoring incoming communications. It is part of the bridge’s operational infrastructure, though its primary role in this scene is to alert Worf to Orton’s message.
After: Worf’s console remains active but is no longer the focus of attention after Picard exits to the Ready Room. Its beep has served its purpose, and the bridge crew returns to their respective tasks, though the atmosphere is now charged with the additional pressure of Orton’s pending communication.
Captain's Ready Room

The incoming message from Administrator Orton is the external disruption that pulls Picard away from the bridge’s crisis. It arrives at a critical moment, interrupting the discussion between Picard, Geordi, and Worf and forcing Picard to prioritize administrative coordination over immediate technical and security concerns. The message is a reminder of the broader institutional context in which the Enterprise operates, and its urgency underscores the layered challenges Picard must navigate. Orton’s communication is off-screen but deeply consequential, as it shifts the focus of the scene and reinforces the tension between operational and bureaucratic demands.

Before: The message is en route but not yet …
After: The message has been received and acknowledged by …
Before: The message is en route but not yet delivered. It exists as a pending communication, its content unknown but its urgency implied by Worf’s immediate relay to Picard.
After: The message has been received and acknowledged by Picard, who exits to the Ready Room to address it. Its delivery has disrupted the flow of the bridge’s crisis, pulling Picard’s attention away from Geordi and Worf and introducing a new layer of institutional pressure.
Worf's Bridge Console (USS Enterprise-D Bridge Console)

Worf’s console serves as the communication hub for the bridge during this event. It beeps sharply with the incoming message from Administrator Orton, interrupting the discussion between Picard, Geordi, and Worf. Worf relays the message to Picard, who immediately exits to the Ready Room to address it. The console is a functional but unobtrusive element, its beep a stark reminder of the external pressures facing the crew. Its role is to facilitate communication, but in this moment, it also symbolizes the disruption of institutional demands amid a crisis. The console’s beep is the catalyst for Picard’s departure, shifting the dynamic on the bridge.

Before: Worf’s console is active and fully functional, monitoring …
After: Worf’s console remains active but is no longer …
Before: Worf’s console is active and fully functional, monitoring incoming communications. It is part of the bridge’s operational infrastructure, though its primary role in this scene is to alert Worf to Orton’s message.
After: Worf’s console remains active but is no longer the focus of attention after Picard exits to the Ready Room. Its beep has served its purpose, and the bridge crew returns to their respective tasks, though the atmosphere is now charged with the additional pressure of Orton’s pending communication.
Baryon Sweep

The baryon sweep is the looming, invisible threat that drives the entire event. Geordi warns that the Enterprise’s elevated particle levels could force the Remmler Array to use a stronger beam than normal, risking system overloads and potentially catastrophic failure. This threat is abstract but deeply consequential, serving as the backdrop for Picard’s decisions. The sweep is not yet active, but its impending arrival creates a sense of urgency and dread, shaping the crew’s actions and dialogue. Picard’s authorization to disable command functions is a direct response to this threat, as is his denial of Geordi’s request for additional field diverters. The baryon sweep embodies the larger narrative tension between control and chaos, stability and destruction.

Before: The baryon sweep is imminent but not yet …
After: The baryon sweep is authorized to proceed, with …
Before: The baryon sweep is imminent but not yet underway. The Enterprise is in the final stages of evacuation, and the crew is scrambling to prepare for its arrival. Geordi’s warnings about the sweep’s potential intensity are based on the ship’s current particle levels, which are higher than usual due to its operational history.
After: The baryon sweep is authorized to proceed, with command functions disabled as a precaution. The sweep itself has not yet begun, but the stage is set for its arrival. The crew’s actions—Picard’s decisions, Geordi’s frustration, Worf’s satisfaction—are all reactions to this impending threat, which now hangs over the scene like a sword of Damocles.
Enterprise Core Command Pathways

The Enterprise’s command functions are the focal point of Worf’s request and Picard’s authorization. These functions represent the ship’s core operational pathways, including navigation, weapons, and internal systems, and their disablement is a drastic but necessary measure to protect them from the baryon sweep’s radiation. Picard’s decision to disable them is a calculated risk, prioritizing security over potential technical instability. The computer voice acknowledges the authorization, its detached tone underscoring the gravity of the action. The disablement leaves the ship’s command systems vulnerable but aligns with Worf’s security-focused priorities, creating a narrative tension between short-term safety and long-term stability.

Before: The command functions are fully operational, though the …
After: The command functions are disabled, as authorized by …
Before: The command functions are fully operational, though the crew is in the process of evacuating the ship. Worf’s request to disable them is a proactive measure to shield them from the baryon sweep, which is expected to be stronger than usual due to the Enterprise’s particle levels.
After: The command functions are disabled, as authorized by Picard. This action leaves them protected from the sweep’s radiation but also renders them inactive, creating a temporary but critical vulnerability. The disablement is a double-edged sword: it addresses the immediate threat but introduces new risks, reflecting the crew’s fractured priorities and the emotional cost of Picard’s leadership.
Enterprise-D Bridge Field Diverters

Geordi’s request for additional field diverters to protect the computer core and bridge from the intensified baryon sweep is a critical but denied element of this event. He explains that the Enterprise’s high baryon particle levels—due to five years of intensive warp travel—could trigger a stronger-than-normal sweep, risking system overloads if the diverters aren’t installed. His plea for 20 minutes to reinforce the systems is met with a firm ‘no’ from Picard, who prioritizes the immediate threat of the sweep over long-term technical safeguards. The field diverters symbolize the tension between proactive engineering and reactive crisis management, and their absence looms as a potential point of failure. Geordi’s frustration at their denial is palpable, highlighting the emotional cost of Picard’s decision.

Before: The field diverters are requested but not yet …
After: The field diverters remain uninstalled, leaving the computer …
Before: The field diverters are requested but not yet installed. Geordi emphasizes their urgency, noting that the Enterprise’s particle levels are unusually high due to prolonged warp travel. The diverters are a preventive measure, but their installation is delayed by the evacuation timeline and Picard’s priorities.
After: The field diverters remain uninstalled, leaving the computer core and bridge vulnerable to the baryon sweep. Geordi’s request is denied, and the crew proceeds without this critical safeguard. The diverters’ absence becomes a latent threat, reinforcing the high-stakes nature of Picard’s decisions and the potential consequences of his prioritization of security over engineering.
USS Enterprise-D Bridge Consoles (Evacuation Shutdown)

The bridge consoles on the Enterprise-D are depicted in a state of controlled shutdown as the evacuation proceeds. Geordi references their current status, noting that additional field diverters for the computer core and bridge have not yet been installed—a critical detail that underscores the ship’s vulnerability during the baryon sweep. The consoles flicker off one by one, their deactivation symbolizing the ship’s transition from active duty to a state of suspended animation. Worf’s console beeps with the incoming message from Orton, serving as a tangible interruption that pulls Picard’s focus away from the technical and security discussions at hand. The consoles are both a functional tool and a narrative device, reflecting the crew’s urgency and the stakes of their decisions.

Before: The bridge consoles are partially active, with crew …
After: The bridge consoles are largely deactivated, their screens …
Before: The bridge consoles are partially active, with crew members in the process of shutting them down. Geordi’s warnings about the baryon sweep and the need for additional field diverters are tied to their current state—some systems are still operational, but the ship is transitioning to a minimal-power configuration. Worf’s console is functional and beeps with the incoming message from Orton, indicating its role as a communication hub.
After: The bridge consoles are largely deactivated, their screens dark as the shutdown proceeds. The computer voice acknowledges Picard’s authorization to disable command functions, confirming that this critical system is now vulnerable during the baryon sweep. Worf’s console remains active but is no longer the focus of attention, as Picard exits to the Ready Room to address Orton’s message. The overall atmosphere of the bridge is one of tension and urgency, with the consoles serving as a visual metaphor for the ship’s precarious state.

Location Details

Places and their significance in this event

1
Arkaria Base Reception Hall

The Enterprise-D bridge is the primary setting for this event, serving as the nerve center of the ship’s operations during the evacuation. The bridge is depicted as a space of controlled chaos, with crew members shutting down consoles and senior officers (Picard, Geordi, Worf) engaged in urgent discussions. The atmosphere is tense, with the weight of the baryon sweep and the evacuation pressing down on everyone. The bridge’s functional role is to facilitate the crew’s response to the crisis, but it also symbolizes the institutional power of Starfleet and the personal stakes of the characters involved. The location’s mood is one of urgency and frustration, with Picard’s decisions and the crew’s reactions playing out against the backdrop of flickering consoles and beeping alerts.

Atmosphere Tension-filled with rapid-fire dialogue, flickering consoles, and the hum of urgent activity. The air is …
Function Command center for the Enterprise-D during the evacuation, where critical decisions about the baryon sweep, …
Symbolism Represents the intersection of institutional power (Starfleet) and personal agency (the crew’s individual priorities and …
Access Restricted to senior staff and essential crew during the evacuation; unauthorized personnel are not present.
Flickering bridge consoles being shut down by crew members. The sharp beep of Worf’s console signaling the incoming message from Orton. Picard’s fingers hovering near the console as he issues authorization for the command function disablement. Geordi’s frustrated expression as his request for additional field diverters is denied.

Organizations Involved

Institutional presence and influence

2
Starfleet

Starfleet is the overarching institutional framework that shapes every decision and action in this event. The crew’s adherence to protocols—such as the evacuation, the baryon sweep, and the disablement of command functions—is a direct reflection of Starfleet’s operational guidelines. Picard’s leadership is constrained by Starfleet’s hierarchy and priorities, as seen in his denial of Geordi’s request for additional field diverters and his grant of Worf’s security-focused request. The organization’s influence is also felt through the incoming message from Administrator Orton, which pulls Picard away from the bridge to address administrative matters. Starfleet’s presence is both a source of structure and a point of tension, as the crew must navigate its protocols amid a crisis.

Representation Via institutional protocol (evacuation procedures, baryon sweep authorization, command function disablement) and external communication (Orton’s …
Power Dynamics Starfleet exercises authority over the Enterprise’s actions, dictating procedures (e.g., evacuation, baryon sweep) and requiring …
Impact Starfleet’s influence is felt in the crew’s adherence to protocol, the prioritization of security over …
Internal Dynamics The event highlights the tension between operational priorities (e.g., Geordi’s engineering concerns) and security priorities …
To ensure the safe evacuation of the Enterprise and the protection of its systems during the baryon sweep, in accordance with Starfleet protocols. To maintain institutional coordination between the Enterprise and external entities (e.g., Arkaria Base, Administrator Orton), even amid operational crises. Institutional protocols (evacuation procedures, baryon sweep authorization, command function disablement). Hierarchical authority (Picard’s decisions reflect Starfleet’s priorities, even when they conflict with individual crew members’ requests). External communication (Orton’s message disrupts the bridge’s crisis, pulling Picard’s attention to administrative matters).
Remmler Array

The Remmler Array is the external system responsible for the baryon sweep, which looms as the primary threat in this event. Though not directly depicted, its influence is felt through Geordi’s warnings about the sweep’s potential intensity and the crew’s preparations to mitigate its effects. The Array’s role is to purge radiation buildup from the Enterprise, but its operation is a double-edged sword: while necessary for the ship’s safety, it also introduces the risk of system overloads due to the Enterprise’s high particle levels. The Array’s involvement is implied but critical, as it drives the urgency of the scene and shapes Picard’s decisions.

Representation Via the baryon sweep procedure, which is the immediate threat driving the crew’s actions and …
Power Dynamics The Remmler Array exerts indirect but significant power over the Enterprise and its crew. Its …
Impact The Remmler Array’s involvement reinforces the theme of external forces shaping the crew’s decisions. Its …
To perform the baryon sweep and clear the Enterprise of radiation buildup, as part of its standard operational procedure. To ensure the sweep’s effectiveness, even if it requires a stronger-than-normal beam due to the ship’s particle levels. Technical constraints (the Enterprise’s high particle levels necessitate a stronger sweep, increasing the risk of system overloads). Procedural demands (the sweep must proceed as scheduled, regardless of the crew’s preparations). Indirect pressure (the crew’s actions—e.g., disabling command functions, denying field diverters—are reactions to the Array’s impending operation).

Narrative Connections

How this event relates to others in the story

Across episodes

Threads arriving here 1

"Episode 14's urgent Computer response to the Romulan disruptor strike (minimal damage, shields/phasers readiness) escalates into Episode 18's immediate Computer authorization for disabling command functions during the baryon sweep (high-risk system shutdown), reflecting a progression in crisis severity."

Romulan dissidents materialize on Enterprise
S6E14 · Face of the Enemy

Themes This Exemplifies

Thematic resonance and meaning

Key Dialogue

"GEORDI: I just finished..."
"WORF: Request permission..."
"GEORDI: ((to Worf)) After you..."
"WORF: ((to Geordi)) No sir. I believe you spoke first."
"PICARD: We're running out of time, gentlemen. Mister Worf?"
"WORF: The computer needs your authorization to disable command functions during the baryon sweep."
"PICARD: Are we ready, Mister La Forge?"
"GEORDI: Almost. I've requested some additional field diverters for the computer core and the Bridge and they haven't been installed yet."
"PICARD: ((concerned)) Additional units?"
"GEORDI: We've logged more warp hours in five years than most ships do in ten, so our baryon particle levels are pretty high. I'm a little worried that when the Remmler Array starts sweeping the ship it might have to use a stronger beam than normal to clear out all the radiation."
"PICARD: ((understanding)) And that might overload the field diverters protecting our key systems. How long until the new ones are in place?"
"GEORDI: I'd say another twenty minutes."
"PICARD: Very well. ((to com)) Computer, disable all command functions in thirty minutes. Authorization: Picard gamma-six-zero-seven-three."
"WORF: ((off console)) Incoming message, Captain. It's the station administrator, Mister Orton."
"PICARD: In my Ready Room."
"WORF: Sir. Request permission to be excused from Commander Hutchinson's... reception."
"PICARD: Permission granted. I only wish I could excuse myself as well."
"GEORDI: Captain, permission to -"
"PICARD: Sorry, Mister LaForge... I can't excuse the entire senior staff. Worf beat you to it."