11.1 Your Ship Will Take Damage

This is not pessimism. It is certainty. In any engagement against a peer adversary — a D7 battlecruiser, a Romulan Bird-of-Prey, or anything of comparable capability — your ship will be hit. Shields will absorb most of the energy, but some will get through. As the engagement continues, more will get through. Systems will fail. Hull will breach. Crew will die.

The question is not whether your ship takes damage. The question is: how much damage can your ship absorb, how fast can it be repaired, and how long can you sustain combat operations as the damage accumulates?

This section answers those questions.

---

11.2 How Damage Happens — The Physics of Getting Hit

Understanding the damage mechanism helps you predict what will fail, when, and why. It also helps you understand what Scotty is dealing with when he tells you he needs ten minutes.

Stage 1: Shield Absorption

The incoming weapon — phaser beam, disruptor bolt, plasma charge, torpedo — strikes your deflector shield. The shield absorbs the energy, converting it from destructive force into a form that dissipates through the shield grid. Shield strength drops by an amount proportional to the absorbed energy.

Damage at this stage: None to the ship itself. The shield took the hit. But the shield is now weaker, and the power grid is working harder to regenerate the shield. There is an indirect cost — power consumption increases, and if the shield generator is near its thermal or structural limits, the strain may degrade its future performance.

Stage 2: Energy Bleedthrough

As shields weaken below roughly 40-50%, they no longer absorb incoming energy completely. Some portion of the weapon's energy penetrates the shield and reaches the hull and internal systems. This bleedthrough increases as shields drop further.

Damage at this stage:

• Power system surges: Energy that bleeds through the shield enters the ship's hull, which conducts it into the structural frame and — critically — into the electro-plasma system (EPS) power grid. This is what causes the console explosions that TOS depicts so consistently. The power grid acts as a conductor for combat energy, carrying destructive surges to control consoles, junction points, and relay stations throughout the ship.
• Minor structural stress: The hull flexes under energy impacts. At bleedthrough levels, this stress is manageable but cumulative. Each hit adds to the total structural fatigue.
• System fluctuations: Individual systems may flicker, reset, or momentarily fail as power surges pass through their circuits. These are transient — annoying but not critical.

Stage 3: Shield Section Failure

When a shield section reaches 0%, there is no energy barrier in that facing. Incoming weapons fire strikes the hull directly.

Damage at this stage — an order of magnitude worse:

• Hull breaches: Direct weapon hits on the hull can breach it — creating openings that decompress the affected compartment and potentially adjacent ones. TOS depicts these as localized catastrophes — the compartment is lost, personnel inside are killed or evacuated, and emergency forcefields or physical barriers seal the breach to protect the rest of the ship.
• Structural damage: The hull's structural members — the frame, spars, and load-bearing elements that hold the ship together — take direct damage. This is not repairable in combat. Structural damage accumulates and weakens the ship's ability to withstand subsequent hits.
• System destruction: Equipment in the hit area is destroyed outright. If that equipment is critical (a shield generator, a power conduit junction, a phaser relay, a sensor array), its loss degrades a specific capability.
• Massive power surges: Without the shield to buffer incoming energy, the full force of the weapon's output enters the ship's power grid. Console explosions become more violent. EPS conduits rupture, venting superheated plasma into corridors and compartments. Secondary fires and explosions cascade through connected systems.
• Crew casualties spike: Personnel in and near the impact area are killed. Personnel throughout the ship are at increased risk from console explosions, power conduit failures, and secondary effects.

Stage 4: Deep Penetration

Sustained fire on an unshielded hull section can penetrate to critical internal systems — the reactor, main engineering, the torpedo magazine, structural bulkheads. At this point, the damage threatens not just combat capability but the survival of the ship.

Damage at this stage:

• Reactor containment threatened — antimatter breach risk
• Primary structural failure — the ship may literally break apart
• Magazine detonation — if torpedo storage is hit, secondary explosions
• Life support failure in large sections
• Loss of main engineering as a functional space

---

11.3 The Damage Cascade — What Fails and In What Order

Damage in TOS follows recognizable patterns. Understanding the typical failure sequence helps you anticipate what's coming next and prioritize repair efforts.

The Typical Cascade (Shield-Phase Damage)

While shields are holding but degrading:

1. Console overloads (first visible damage) — bridge and engineering stations spark and explode as power surges travel the grid. Crew injuries begin.
2. Non-essential system failures — low-priority systems on overloaded circuits trip offline. Automatic load-shedding protects critical systems by sacrificing lesser ones.
3. Lighting and gravity fluctuations — brief power interruptions as the grid compensates for combat loads. Dramatic but not operationally critical.
4. Sensor degradation — if sensor arrays or their power feeds are on stressed circuits, resolution may decrease. Science officer reports reduced capability.
5. Communication interference — internal and external comms may experience static, dropouts, or temporary failures as the communication grid shares power pathways with other systems.

The Typical Cascade (Hull-Phase Damage)

Once shields fail on a section and the hull is taking direct hits:

1. Hull breaches — compartments open to space. Emergency forcefields activate (while power holds). Crew in affected areas are killed or evacuated.
2. Power conduit ruptures — EPS conduits in the damaged area break, venting plasma and severing power pathways to downstream systems. This is how damage in one area degrades capability in another — the power that fed a phaser bank travels through conduits that run through the hull, and a hit that ruptures those conduits shuts down the phaser bank even though the bank itself is undamaged.
3. Shield generator damage — shield emitters on the hull surface are vulnerable to direct fire. Losing an emitter reduces or eliminates shield coverage in that area, preventing shield restoration even if power is available.
4. Weapons system damage — phaser banks, torpedo tubes, and their feed systems are hull-mounted or hull-adjacent. Direct fire can destroy them.
5. Propulsion damage — hits on nacelles, pylons, or impulse engines degrade or eliminate propulsion capability.
6. Structural frame damage — the ship's skeleton weakens. Each subsequent hit does disproportionate damage because the structure can no longer absorb and distribute impact forces.

The Typical Cascade (Critical-Phase Damage)

If damage continues beyond hull breaches:

1. Main engineering compromise — damage reaches the engineering section. Reactor efficiency drops as containment systems are stressed. The risk of antimatter breach becomes non-theoretical.
2. Multiple simultaneous system failures — the ship's systems are so interconnected that cascading failures become self-reinforcing. A power loss causes a sensor failure, which causes a targeting loss, which causes a weapons failure, which prevents you from suppressing the enemy's fire, which causes more power loss.
3. Life support failure — in large sections or shipwide. Crew must evacuate to areas with functioning life support, further concentrating personnel and reducing the ship's operational envelope.
4. Loss of navigational control — if helm and navigation systems are destroyed, the ship drifts. Even with engines functional, without navigation you can't maneuver effectively.
5. Catastrophic structural failure or reactor breach — the ship is destroyed.

---

11.4 Scotty's Art — Field Repair Under Fire

Your chief engineer and his damage control teams are what stand between "the ship is damaged" and "the ship is destroyed." Field repair during combat is the most demanding engineering task imaginable — working on critical systems while the ship shakes, power surges through the grid, compartments decompress, and the captain demands more capability than the laws of physics currently allow.

What Scotty Actually Does

It's worth understanding the specific techniques Scotty employs, because each one has different time requirements, risks, and capabilities.

Power Rerouting

The most common and fastest field repair. When a power conduit is severed or a relay is destroyed, Scotty bypasses the damaged section by routing power through alternate pathways.

• Time: 2-5 minutes for a standard reroute
• Requirements: Alternate pathways must exist and be accessible. The bypass may carry less power than the original conduit (reducing the system's maximum output). The bypass may overload if sustained at high levels.
• Risk: Low to moderate. The main risk is that the bypass conduit wasn't designed for the load and may fail under sustained use.
• Capability restored: Partial. The system gets power, but possibly at reduced levels.

TOS shows Scotty performing power reroutes with remarkable speed and creativity. He knows the ship's power architecture intimately — not just the standard pathways but every secondary connection, every maintenance conduit, every emergency bypass. This knowledge is what allows him to find routes that the standard repair manual doesn't document.

Component Bypass

When a specific component fails — a relay, a transformer, a switching unit — Scotty can sometimes bypass it entirely, connecting the upstream and downstream elements directly. This eliminates the component's function (whatever regulation, switching, or transformation it provided) but restores basic power flow.

• Time: 5-15 minutes depending on component location and accessibility
• Requirements: The component's function must be non-essential for basic operation, or its absence must be compensatable through manual control
• Risk: Moderate. Removing a regulator from a circuit, for example, means the circuit runs unregulated — power fluctuations, overheating, and eventual failure are possible
• Capability restored: Partial, often degraded

Physical Repair

Actually fixing the broken thing — welding a cracked conduit, replacing a burned-out component from spares, reseating a dislodged module. This is slower than rerouting or bypassing but provides a more durable restoration.

• Time: 10-60 minutes depending on damage severity and component complexity
• Requirements: Replacement parts (if the component is destroyed, not just damaged), tools, access to the damaged area (which may be in a depressurized or damaged compartment)
• Risk: Low once completed — a proper repair is more reliable than a bypass
• Capability restored: Full, or near-full

Emergency Hull Patching

Sealing hull breaches to restore atmospheric integrity in damaged compartments. This uses emergency sealant, structural patches, and portable forcefield generators.

• Time: 5-15 minutes for a small breach, 15-60 minutes for a large one
• Requirements: Damage control teams with patch materials and forcefield generators. Access to the breach (which may require EVA if the compartment is fully depressurized).
• Risk: Moderate — patches hold against atmospheric pressure but may not survive additional weapons impacts in the same area
• Capability restored: Atmospheric integrity in the compartment. Personnel can re-enter. Systems in the compartment can be operated again.

System Recalibration

Some systems fail not because they're physically damaged but because the power surges and impacts have knocked their calibration out of spec. Sensors, targeting computers, and navigation systems may need recalibration after heavy combat.

• Time: 5-30 minutes depending on the system
• Requirements: Technical expertise and access to the system's control interfaces
• Risk: Low
• Capability restored: Full

Cross-System Improvisation

Scotty's signature: using one system's components to replace or supplement another's. Taking power cells from a non-essential system to supplement the shield generator. Using the deflector dish's power supply to feed the phasers. Repurposing sensor array components as communication relays.

• Time: Variable — 10 minutes to hours depending on complexity
• Requirements: Deep knowledge of multiple systems, creative engineering, and a commander willing to sacrifice the donor system's function
• Risk: High — improvised connections are fragile, untested, and may fail unpredictably
• Capability restored: Variable — sometimes surprisingly good, sometimes barely functional

---

11.5 Repair Priorities — What Gets Fixed First

When everything is broken, Scotty can't fix everything at once. Repair is a triage process, just like McCoy's medical triage. The engineer assesses what's damaged, what can be repaired with available resources and time, and what must be repaired first to keep the ship fighting.

The Priority Framework

This framework was introduced in Part 2. Here it is expanded with repair-specific detail:

Priority 1: Antimatter Containment

If containment is threatened, everything else stops. Every engineer, every damage control team, every available resource goes to stabilizing the reactor. If containment fails, there is no ship to repair. Nothing else on this list matters.

Repair approach: Reinforce containment fields, stabilize magnetic bottles, reduce reactor output to minimum safe levels, repair containment system damage. This may require shutting down the reactor entirely and switching to impulse/battery power.

Time: If containment is actively degrading, you have minutes — not the minutes-to-repair but the minutes-until-breach. Scotty may need to reduce reactor output (cutting your combat power) to stabilize containment before repair can even begin.

Priority 2: Shield Restoration

Shields are what prevent further damage. Every second without shields is a second where incoming fire causes hull damage, casualties, and cascading system failures. Getting shields back online — even partially — slows the damage rate and buys time for all other repairs.

Repair approach: Power rerouting to shield generators is the fastest path. If generators are damaged, partial capability may be achievable by running the remaining generators at increased output. If emitters are destroyed, no amount of power rerouting can restore shields on that facing — the hardware is gone.

Time: 5-10 minutes for power restoration to intact generators. Much longer if generators themselves are damaged.

Priority 3: Propulsion

If you can't move, you can't evade fire, can't rotate shields, can't control range, and can't escape. Restoring at least impulse maneuverability is critical.

Repair approach: For impulse, reroute power to intact impulse engines. For warp, the repair depends on the damage — conduit repair, nacelle systems restoration, or dilithium crystal replacement (if available). Warp restoration is almost always slower than impulse restoration.

Time: Impulse restoration: 5-20 minutes. Warp restoration: 30 minutes to hours, heavily dependent on damage type.

Priority 4: Weapons

You need to shoot back. Even partial weapons capability changes the engagement — an enemy fighting a ship that can't fire behaves very differently from one fighting a ship that might hit him.

Repair approach: Phaser bank restoration typically involves power rerouting and component bypass. If the bank itself is destroyed (emitter array physically damaged), there's nothing to reroute to. Torpedo tube repair involves mechanical clearing (jammed mechanisms) or power restoration to the launcher system.

Time: Single phaser bank restoration: 3-10 minutes. Torpedo tube clearing: 5-15 minutes. Destroyed weapons cannot be repaired in combat.

Priority 5: Life Support

Crew can survive without life support longer than without shields — minutes to hours depending on conditions. But life support is non-negotiable over any extended timeframe, and compartments without life support are compartments where your crew can't work.

Repair approach: Reroute power to life support generators. Seal breached compartments to allow atmosphere retention. In extreme cases, consolidate crew into areas with functioning life support and abandon the rest of the ship to vacuum.

Time: Power rerouting: 5-10 minutes. Compartment sealing: variable.

Priority 6: Sensors and Communications

You need to see and you need to coordinate. But you can fight blind for a short time if you must.

Repair approach: Sensor recalibration, power restoration to arrays, antenna repair for communications. Uhura and the science staff can assist with their own systems.

Time: 5-30 minutes depending on damage type.

Priority 7: Everything Else

Turbolifts, non-essential compartments, secondary systems, comfort systems. These wait until the ship is no longer in danger.

The Commander's Role in Repair Prioritization

You set the strategic context. Scotty sets the technical priorities within that context.

Example: You're in a running fight and your primary concern is reaching a starbase. You tell Scotty: "I need warp capability above all else." Scotty reprioritizes accordingly — warp restoration moves above weapons, possibly above shields if you're running rather than fighting.

Example: You're defending a position and reinforcements are en route. You tell Scotty: "I need to hold this position for thirty minutes. Shields and weapons are the priority — I'm not going anywhere." Scotty ignores propulsion repair and focuses everything on keeping your shields up and your phasers firing.

The engineer prioritizes. You contextualize. This partnership is the core of damage management.

---

11.6 Repair Timelines — The Numbers

We covered basic repair timelines in Part 2. Here they are expanded with more context about what affects the timing.

In-Battle Field Repair (Minutes)

Repair Task	Estimated Time	Key Variables
Power reroute (single circuit)	2-5 min	Availability of alternate pathway, complexity
Phaser bank restoration (from overload)	3-8 min	Whether bank is overloaded vs. damaged
Partial shield restoration (power reroute)	5-10 min	Generator condition, available power
Torpedo tube clearing (jammed)	5-10 min	Mechanical vs. electrical jam
Hull breach patch (small)	5-15 min	Access, breach size, atmospheric loss rate
Impulse engine restoration	5-20 min	Damage type, single vs. multiple engines
System recalibration (sensors, targeting)	5-30 min	System complexity, damage extent
Cross-system improvisation	10-60 min	Creativity required, physical work involved

Critical factor: these times assume the ship is still under fire. Repair teams are working while the ship shakes, while power surges happen, while secondary explosions are possible. Each new hit may undo work already completed or damage the system being repaired. A repair task estimated at 10 minutes may take 20 if the team has to stop and take cover, re-do work damaged by a subsequent hit, or work around a new failure in an adjacent system.

Scotty's Rule: When Scotty gives you a time estimate, it's his honest best assessment given current conditions. If conditions worsen (heavier fire, new damage), the estimate extends. If conditions improve (enemy breaks contact, fire reduces), the estimate may shorten. "I said ten minutes and I mean ten minutes" is Scotty committing to a timeline he believes he can hold — but physics doesn't care about commitments.

Post-Battle Repair (Hours)

Once the shooting stops, repair accelerates dramatically. Full power is available for repair systems. Damage control teams can work without interruption. Access to damaged areas is safer.

Repair Task	Estimated Time	Notes
Full shield restoration (from heavy damage)	2-6 hours	Depends on generator condition
Phaser bank rebuild (damaged, not destroyed)	4-12 hours	May require component replacement
Hull breach structural repair	6-24 hours	Emergency patches replaced with structural repair
Impulse engine overhaul	4-12 hours	If damage is to the engine itself, not just power feed
Warp drive repair (minor)	4-12 hours	Conduit repair, recalibration
Warp drive repair (major)	12-72 hours	Nacelle damage, reactor system repair
Console replacement	2-8 hours	Standard modular replacement from ship's stores
Internal power grid repair	4-24 hours	Depends on number of ruptured conduits
Sensor array repair/replacement	4-16 hours	Depends on whether arrays are damaged or destroyed

Ship's stores: Your ship carries a supply of replacement components — consoles, relay modules, conduit sections, structural patches, power cells. These stores are finite. After a heavy engagement, you may exhaust specific components. Post-battle repair is then limited by what you have aboard, with full restoration requiring a starbase.

Starbase Repair (Days to Weeks)

Damage beyond the ship's self-repair capability requires a starbase or shipyard:

Repair Task	Estimated Time	Why It Needs a Starbase
Structural hull repair (major)	Days to weeks	Requires external structural work, heavy equipment
Nacelle repair/replacement	Days to weeks	Specialized components, structural integration
Reactor system overhaul	Weeks	Core component replacement, containment recertification
Dilithium crystal replacement	Minutes if available	Supply is the issue, not installation time
Shield generator replacement	Days	Heavy component, integration testing
Major weapons system rebuild	Days to weeks	Emitter replacement, power system integration
Full combat refit	Weeks to months	Complete assessment and restoration of all systems

The starbase dependency: Your ship is designed for independent operations, but it is not infinitely self-sustaining. After a major engagement, reaching a starbase becomes a strategic priority — not just for repair, but for resupply of torpedoes, replacement components, dilithium crystals, and personnel.

---

11.7 Combat Endurance — How Long Can You Fight?

This is the integration question — bringing together everything from damage rates, repair capability, power reserves, crew endurance, and resource consumption to answer: how long can a Constitution-class starship sustain combat?

The Variables

Enemy damage output: How fast is the enemy draining your shields and causing damage? A single D7 at medium range delivers a certain damage rate. Two D7s deliver more. A Romulan plasma torpedo at close range delivers devastating damage in a single pulse.

Your shield management: Active shield rotation and management extend your shield endurance significantly. A well-managed shield envelope lasts 2-3 times longer than a passively maintained one.

Your power reserves: How much reactor output is available, how fast your dilithium is degrading, whether impulse backup is intact. More power means more shield regeneration and more weapons fire.

Repair rate: How fast Scotty can restore damaged systems relative to how fast new damage arrives. If repair rate exceeds damage rate (during lulls or at long range), your ship improves over time. If damage rate exceeds repair rate (sustained close-range combat), your ship degrades toward destruction.

Crew endurance: As covered in Part 2 — fatigue sets in after 4-8 hours, performance degrades significantly after 12 hours. Crew casualties compound the problem.

Resource consumption: Torpedoes expended, dilithium consumed, replacement components used, repair materials depleted. All finite, all declining.

Endurance Estimates by Scenario

Scenario 1: Single D7, medium range, active maneuvering

• Shield endurance: 30-60 minutes before critical section failure (with rotation)
• Weapons endurance: limited by power, not ammunition (phasers); torpedoes to be managed
• Crew endurance: not a factor in a fight this short
• Overall: 45-90 minutes of sustained combat before one side or the other reaches a crisis point
• Limiting factor: Shield degradation and power competition between shields and weapons

Scenario 2: Single Romulan Bird-of-Prey, cloaked engagement

• This engagement is episodic, not sustained — periods of search punctuated by brief violent exchanges during decloak-fire-recloak cycles
• Each exchange lasts seconds to a minute; the search periods last minutes to hours
• Overall duration: could extend for hours if neither side achieves a decisive hit
• Limiting factor: Patience, sensor capability, and the Romulan's power reserves (which deplete with each cloak cycle)

Scenario 3: Two D7s, close range

• Shield endurance: 10-20 minutes — shield rotation is ineffective against two ships
• Damage rate exceeds repair rate almost immediately
• Overall: 15-30 minutes before critical damage accumulates beyond combat viability
• Limiting factor: Shield overwhelm from concentrated fire on multiple facings simultaneously. This is a fight you should avoid or end quickly.

Scenario 4: Extended patrol in hostile territory, multiple engagements

• Per-engagement endurance per above estimates
• Between engagements: post-battle repair time of 2-12 hours depending on damage
• Strategic endurance: 3-5 significant engagements before torpedo supply, dilithium reserves, component stores, and crew fatigue degrade combat effectiveness to unacceptable levels
• Limiting factor: Cumulative resource depletion. Each fight degrades your readiness for the next. Without starbase resupply, you become progressively less capable.

The Endurance Spiral

Just as power failure cascades (Part 4), combat endurance degrades in a compounding spiral:

1. Initial damage reduces combat efficiency slightly
2. Reduced efficiency means fights last longer and cost more
3. Longer fights cause more damage and consume more resources
4. More damage means longer repair times between fights
5. Longer repair times in hostile territory increase risk of being caught mid-repair
6. Each subsequent engagement begins from a lower baseline of readiness

This spiral is why sustained combat operations without resupply are strategically unsustainable. You can win individual battles while slowly losing the ability to fight the next one. A commander must account for this — fighting the current battle while preserving the capability to fight the next.

---

11.8 The Decision to Break Off — Knowing When You've Lost the Ship

The hardest command decision is recognizing that you cannot win the current engagement and must disengage or accept destruction.

Indicators That You're Losing the Ship

Objective indicators (systems):

• Multiple shield sections at or below 20% with limited power for regeneration
• Main reactor operating at reduced output due to damage (the death spiral from Part 4)
• Weapons capability reduced to minimal — one phaser bank, no torpedoes
• Propulsion compromised — impulse only, or reduced impulse
• Multiple hull breaches with damage control teams overwhelmed

Objective indicators (crew):

• Casualty rate exceeding damage control team capability
• Key stations unmanned or manned by unqualified replacements
• Engineering reporting cascading failures faster than repair
• Sickbay at capacity with no ability to return crew to duty at the rate they're being lost

Subjective indicators:

• Scotty's reports are getting shorter and more urgent
• Spock's shield and damage reports show a consistent downward trend with no inflection
• Your tactical options have narrowed to a single viable course of action
• You're making decisions about which systems to sacrifice, not which to repair

The Disengage Decision

If you recognize these indicators and escape is possible:

1. Communicate intent to engineering: "Scotty, I need warp speed. Everything else is secondary."
2. Shift to full defensive posture: All remaining power to shields. Cease fire (conserve power for engines).
3. Maneuver for escape: Helm plot an escape course that minimizes exposure time during the warp transition.
4. Execute: Power to warp drive, accept the shield drop during transition, go to maximum warp.
5. Accept the parting shots: You will take fire during the escape. The hull will take hits. This is the cost of survival.

When escape is not possible (engines destroyed, enemy too close to evade, surrounded):

• The decision set narrows to fight-to-the-end, surrender, or self-destruct
• These options are covered in Part 12

What Kirk's Record Shows

Kirk broke off engagements when the math demanded it. He was not reckless with his ship or crew. When a fight was unwinnable and escape was possible, he withdrew — and returned when conditions improved.

The key insight from Kirk's record: breaking off is not admitting defeat. It is preserving the capability to fight again. A destroyed ship protects nothing. A ship that withdraws, repairs, and returns fights another day.

The only exception in Kirk's doctrine: when something was worth dying for — the safety of the Federation, the lives of those who couldn't protect themselves, the prevention of a catastrophe worse than the loss of the Enterprise. In those cases, Kirk stayed, and his crew stayed with him. But these were deliberate choices with clear reasons, not the result of failing to recognize a losing fight.

---

11.9 Damage Assessment — Reading Your Own Ship

Throughout an engagement, you need an accurate picture of your ship's condition. This picture comes from three sources:

Engineering Reports (Scotty)

Your chief engineer provides the most complete picture of the ship's physical condition. He has direct readouts from the reactor, the power grid, and every major system. His reports tell you:

• Power output and reserve status
• Shield generator condition (not just shield strength — the hardware that produces shields)
• Propulsion system status
• Weapons system status
• Structural integrity assessment
• Repair progress and estimated completion times

How to read Scotty's reports:

What Scotty Says	What It Means	What You Do
"Shields holding, Captain"	Everything is nominal	Continue current approach
"Shields weakening"	Damage rate exceeding regen	Consider rotation or disengagement
"I'm giving you all she's got"	Reactor at rated maximum	Do not demand more power
"I need ten minutes"	Repair is possible but needs time	Buy him ten minutes through maneuver
"I can give you one or the other, not both"	Power is insufficient for simultaneous demands	Choose which system you need more
"She cannae take much more"	Ship approaching structural or system limits	End the fight or leave — damage is becoming irreversible
"Captain, I've lost [system]"	System is gone — not degraded, destroyed	Adjust tactics to operate without it
"I might be able to jury-rig something"	Improvisation possible but uncertain	Give him permission and time, have a backup plan
(Silence from engineering)	Communications are down or engineering is in crisis	Send a runner. Prepare for the worst.

Science Station Reports (Spock)

Your science officer provides shield status numbers, hull integrity readings, and external assessment of the ship's condition as seen by sensors. This is the complementary view to engineering — Scotty reports from inside, Spock reports from the instruments.

Damage Reports from the Ship

Reports from department heads, section chiefs, and damage control teams flow through communications to the bridge. These provide granular detail — which deck, which compartment, which system, how many casualties. When internal communications fail, this flow stops, and you lose visibility into the ship's detailed condition.

---