Master the art of the gap. Learn how communication delay drives narrative tension in The Expanse, The Martian, A Fire Upon the Deep, and Sandman. Discover why the speed of light is a worldbuilder’s most devastating weapon for creating high-stakes drama and moral isolation.
Light is slow.
Say that to most people and they’ll look at you like you just claimed the moon is made of cheese.
Light is the fastest thing in existence. The speed NASA spends billions trying to approach while the rest of us can’t even get our phones to load a webpage without buffering.
But it’s the thing every science fiction writer learns, usually while staring at a wall late at night wondering if their worldbuilding makes any sense. Light is catastrophically, devastatingly slow.
Space is vast in ways that make our brains quietly give up and suggest we think about literally anything else instead.
Earth and Mars are between 34 and 250 million miles apart, depending on where they are in their respective orbits. Which is a fun way of saying the distance between you and your destination changes by 216 million miles based on cosmic timing you have zero control over.
The nearest star system is 4.37 light-years away. Even if you could somehow travel at light speed, which you can’t, you’d spend over four years getting there. Four years to reach your closest neighbor. And that neighbor is a triple star system with no planets worth mentioning, so congratulations on your wasted trip.
Everything we see in the sky is already old news. The light from the sun is eight minutes old by the time it hits your face. You are perpetually living in the past, cosmically speaking, and there’s not a damn thing you can do about it.
Light, the fastest possible thing in the universe, is agonizingly, insultingly slow compared to the distances it has to cross.
Which creates problems every science fiction worldbuilder eventually slams face-first into. One being that communication across these distances isn’t instantaneous. It can’t be. Physics looked at your desire for real-time space conversations and said absolutely not.
A message from Earth to Mars takes anywhere from three to twenty-two minutes to arrive. One way.
Which means you’re not having a conversation. You’re leaving voicemails for each other across a void that doesn’t care about your emergency, your crisis, or the fact that you needed an answer five minutes ago. You’re playing the slowest, most frustrating game of phone tag in human history, and the stakes are whether someone lives or dies.
This is communication delay, and it’s the hill almost every science fiction writer either dies on or runs away from.
You either build your entire world around this constraint, letting it shape your politics, your warfare, your relationships, and your plot, or you handwave it away with some fictional technology that lets you pretend space is smaller than it is and hope nobody notices you just made physics cry.
The Expanse chose the first option, committed to the bit, and built one of the most viscerally realistic visions of space conflict because of it.
Table of Contents
- The Expanse: Where Your Distress Signal Arrives After You’re Already Dead
- How Communications Delays Turn Every Message into Ticking Time Bombs, Regardless of the Genre
- How to Weaponize Communications Distances to Drive Stories
- Speak Slowly and Carry a Big Stick
- Common Questions About Communication Delay in The Expanse
The Expanse: Where Your Distress Signal Arrives After You’re Already Dead
The Expanse makes a promise and keeps it for nine books and six seasons, even when breaking it would be so much easier.
Light is slow.
That sounds wrong. Light is the fastest thing in the universe, the universal speed limit, the thing Einstein built relativity around. But when you’re trying to coordinate military operations across the solar system, light might as well be trudging through molasses while checking its phone.
And that slowness has consequences. Not just tactical inconveniences or flavor text about “waiting for a response.” Structural, plot-driving, character-defining consequences that the creators refuse to handwave away even when it would save their protagonists’ lives.
The mechanic is simple. Communication travels at light speed, which sounds instantaneous until you remember space is obscenely big.
Earth to Mars? Three to twenty-two minutes one-way, depending on where both planets are in their orbits. You send a message. You wait. You could make a sandwich. Check your email. Question your life choices. Then maybe you get a response.
Earth to the Belt? Thirty minutes minimum. That’s a sitcom episode. You could watch Rose blathering on about St. Olaf while Dorothy threatens to shoot her with a crossbow (Golden Girls reference for those of you too young to know…) and the photons carrying your desperate plea for help still wouldn’t have arrived.
Earth to Ilus, a colony world beyond the Ring Gates? Roughly six hours each way. Twelve-hour round trip for a single exchange of messages. You could ask “should I surrender to the war criminals?” at breakfast and get Earth’s response at dinner, assuming nothing exploded in the interim.
Spoiler: things explode in the interim.
But The Expanse doesn’t just set this rule and mention it occasionally to prove it’s not dead yet.
The creators use light-lag throughout the story. They build entire plot arcs around what happens when the people who need to make decisions can’t wait for permission.
Around what happens when waiting for orders means watching people die.
Take the Ilus crisis.
It’s a colony world. Corporate security forces versus desperate refugee Belters. Six light-hours from Earth, where UN Deputy Undersecretary Avasarala is watching events unfold on a video feed that’s already six hours old.
She’s watching history. Expensive, high-definition history where people are about to die and she can’t do anything about it.
By the time she crafts a response and sends it, another six hours pass. Twelve-hour round trip for a single back-and-forth. On the ground, James Holden is trapped between Adolphus Murtry, corporate enforcer with authorization to use lethal force, and Belter refugees who got there first and aren’t leaving.
The situation is a powder keg soaked in gasoline sitting next to a fireworks factory.
Someone fires a shot. The landing pad explodes. Ancient alien ruins activate and start killing people indiscriminately because apparently the day wasn’t going badly enough.
Holden makes calls. Brutal calls about who lives and who gets left behind to die screaming. He can’t wait for Earth’s response because waiting means watching the body count climb while the photons carrying Avasarala’s wisdom are still in transit somewhere between stars.
The light-lag creates drama by forcing Holden into moral isolation.
He becomes accountable for decisions made in an information vacuum.
Avasarala, despite her authority, despite her political genius, despite having literally the entire UN apparatus at her disposal, becomes powerless. Her commands arrive as historical documents rather than actionable intelligence. By the time her message arrives, Holden has already made his choice and now gets to find out whether Earth agrees with what he did six hours ago.
This is the fundamental condition of existence in The Expanse.
The solar system breathes. Earth and Mars drift closer and farther apart as they orbit the sun. Belt stations swing through their own elliptical paths. The map of communication delays is constantly shifting, creating dynamic zones of isolation that expand and contract like a tide you can’t predict.
Sometimes Mars is three minutes away. A conversation with awkward pauses. Sometimes it’s twenty-two minutes away. You could have an argument with your spouse in the same room in less time.
Your neighborhood moves. And with it, your ability to call for help.
The creators made this worse on purpose.
When humanity discovered the Ring Gates, wormholes to 1,300+ habitable star systems, they could have spread out sensibly. Built redundant communication networks. Created multiple relay points.
Instead, they created a network with a single chokepoint at Medina Station, sitting at the center of Ring Space where all the gates converge.
Every laser communication between colony worlds must bounce through Medina’s relay buoys. You can’t tightbeam directly from New Terra to Laconia because the gates don’t work that way. The beam has to route through the hub.
This is like building a civilization of 1,300 worlds and giving them all the same WiFi password that only works if everyone’s router goes through one guy’s basement in New Jersey. Surely nothing could go wrong with this architecture.
This is why Marco Inaros and the Free Navy don’t need a massive fleet to conquer 1,300 worlds.
They just need to control Medina.
By seizing the relay station, they sever communication between every colony system simultaneously. Overnight. Completely.
Isolated worlds can’t coordinate defense. Can’t call for help. Can’t even know what’s happening elsewhere. For all they know, they’re the last humans alive and everyone else is already dead.
The Free Navy doesn’t invade. They don’t need to. They just make sure nobody can talk to each other, then they broadcast terms to planets that don’t know if anyone else is still fighting or if they’re alone.
Surrender or risk being the only planet still resisting while everyone else already capitulated. Nobody wants to be the idiot who got their colony massacred over a war that already ended.
Later, Laconia does the same thing with institutional control rather than piracy, wielding Medina as the nervous system of a new interstellar empire. Same chokepoint. Different branding.
The control of communication infrastructure becomes the control of political reality itself.
Quick sidebar on tightbeam communication, because it matters.
Unlike omnidirectional radio, which sprays signal in all directions like a drunk person shouting in a bar, tightbeam is a laser. Point-to-point. Narrow. Secure not through encryption but through geometry.
If you’re not physically in the beam’s path, you can’t intercept it. Your enemies can’t eavesdrop on a conversation they can’t physically reach.
But that security comes with you having to predict exactly where the receiver will be when the light arrives and aim accordingly.
If the target is stationary? Easy. If they’re moving on a predictable trajectory? Math problem, but solvable.
If they’re maneuvering unpredictably, like burning hard in combat while dodging weapons fire every few seconds to avoid dying? You can’t aim at where they are. You have to aim at where they’ll be minutes from now.
And if they don’t know where they’ll be minutes from now because they’re flying evasively to not explode? You can’t reach them at all.
They become unreachable. Not jammed. Not blocked. Just geometrically impossible to contact.
The Expanse treats light-speed delay as an antagonist that can’t be defeated, only adapted to.
Distance forces local agency. You can’t wait for orders from a commanding officer who won’t even receive your message for six hours. You act now or you die now.
Delay forces moral weight. Every decision you make in isolation is a decision you own completely. You can’t hide behind following orders that haven’t arrived yet.
And the creators never, ever cheat.
When it would be convenient for characters to get real-time updates, they don’t get them. When it would save lives for Avasarala to give orders that arrive instantly, she can’t. When it would be dramatically satisfying for a captain to receive crucial intelligence just before the battle, the intelligence arrives three hours after the battle ended and everyone’s already dead.
The rule stays hard. The light-speed limit remains undefeated.
And the story finds its power in the spaces where characters must act without permission, without backup, and without the comfort of knowing what the hell is happening on the other side of the light-minutes between them and home.
They make their choices in the dark and hope they were right. Usually they find out they weren’t.
How Communications Delays Turn Every Message into Ticking Time Bombs, Regardless of the Genre
Communication delay doesn’t care what genre you’re working in. It doesn’t require rocket fuel or orbital mechanics or a PhD in astrophysics to ruin someone’s entire existence.
The constraint works everywhere. Science fiction loves it because physics makes it unavoidable. Fantasy can build it through magic systems with inconvenient operating hours. Historical fiction gets it for free because horses are slow and telegrams haven’t been invented yet.
The mechanism is irrelevant. The gap is everything.
The core constraint is beautifully simple. Someone needs information. That information exists. The gap between needing it and receiving it is long enough to get them killed.
That’s it. That’s the whole trick.
You don’t need elaborate worldbuilding or complex systems. Just create a gap where help exists but can’t arrive in time, where the answer is real but unreachable, where help is coming but will show up to a funeral.
The Martian: When “Can You Hear Me Now?” Takes 22 Minutes to Answer
Andy Weir’s The Martian turns the communication delay between Earth and Mars into a slow-motion assassination attempt.
Not intentional, obviously. Nobody at NASA woke up thinking “let’s see how creative we can get with murdering our astronauts using physics.” But when you’re dying on Mars and help takes eleven minutes to answer the phone, the difference between murder and unfortunate cosmic timing gets philosophically murky.
Mark Watney gets left on Mars because his crew thinks he’s a corpse.
A sandstorm nearly kills everyone. His suit sensors flatline. They make the rational call not to risk five lives retrieving a body, because that’s what good commanders do. Make terrible decisions with incomplete information and then get to live with the consequences.
Except the sensors are wrong.
Mark’s alive, unconscious, and about to wake up very alone on a planet that considers his continued existence a problem it plans to correct. He’s been abandoned by people who love him, for excellent reasons, based on data that was catastrophically incorrect.
NASA figures out he’s alive when someone reviewing satellite imagery notices things moving around between photos. High-stakes Where’s Waldo, except Waldo is an astronaut you left for dead and finding him means you now have to figure out how to un-abandon him from another planet with the entire world watching.
They know exactly where he is. They know exactly what he needs. They can calculate down to the day when his supplies will run out and he’ll start contemplating which body part tastes least terrible.
What they don’t have is any way to tell him any of this.
Every communication system got destroyed in the storm that tried to kill him. NASA has all the answers, Mark has all the questions, and there’s no functional way to connect the two. It’s like watching someone walk off a cliff through a soundproof window. You can see everything. You can do nothing.
Mark assumes they’re probably watching, so he decides his best shot at survival is driving 800 kilometers across Mars to dig up the 1997 Pathfinder lander.
Let’s appreciate the desperation here. His brilliant plan for not dying alone on a frozen desert is to find a piece of equipment that was outdated when he was in middle school and somehow MacGyver it into a working communication system. This is like trying to get online using a 56k modem you found in your parents’ garage, except the garage is on another planet and if the modem doesn’t work you die.
He drives there in a rover that tops out at 25 kilometers per hour. For American readers, that’s 15 miles per hour. Slower than your grandmother drives, and she shouldn’t be allowed near a car.
He’s betting everything on NASA noticing what he’s doing, understanding what he’s trying to do, and figuring out their end of this technological necromancy before he gets there. If they don’t, he just wasted weeks of supplies on a field trip to visit broken garbage.
The plan works, because Mark Watney’s luck is exclusively reserved for not dying in ways that should absolutely kill him.
He gets the lander powered up. Holds his breath. And the camera moves.
Not because of a short circuit or Martian wind. Because NASA remotely activated it from Earth. Proof that they saw him drive across a planet, understood his suicide mission to dig up ancient technology, dug up decades-old source code from some engineer’s archived hard drive, and were ready when he arrived.
They showed him they see him through a rotating camera.
But they have the same problem. They still can’t actually talk.
The camera can rotate. That’s it. That’s the entire capability. No audio. No text input. Just a camera that can point in different directions. It can vaguely gesture and that’s it.
So Mark arranges flashcards with letters and numbers in a circle, and NASA spells out messages in hexadecimal by pointing the camera at cards one character at a time.
Hexadecimal. The number system nobody uses unless they’re programming computers or trying to communicate with an astronaut using a camera from the Clinton administration.
To send “YES” NASA has to point the camera at 59, then 45, then 53. Three letters takes six separate camera movements. A simple sentence takes forever. A complex technical instruction takes hours. It’s Wheel of Fortune if Wheel of Fortune wanted to make you contemplate mortality while Vanna White rotated in slow motion. And if you get distracted for a moment, the whole thing makes no sense because you missed a letter and have a gap.
And it gets worse.
This is probably a good time to talk about orbital mechanics and distance. Light takes three to twenty-two minutes one-way to travel between Mars and Earth, depending on where the planets are in their orbits. Average is about eleven minutes.
Which means there’s a twenty-two minute round trip between “I’m dying” and “oh no.”
You send a message. Eleven minutes later, they receive it. They immediately respond. Eleven minutes after that, you get their response. The speed of light doesn’t care about your emergency. The speed of light doesn’t negotiate.
So their entire communications system is a camera that’s been rotting on Mars for twenty years, rotating to spell out messages half a letter at a time in hexadecimal, with an eleven-minute lag between hitting send and the camera actually starting to move.
They use this to walk Mark through scavenging other abandoned equipment to jerry-rig something marginally less agonizing to operate. Which somehow works, and now they can send full sentences instead of individual hex characters. Progress. Mark can send back error logs and data readouts instead of just “STILL ALIVE, SEND HELP.”
But that eleven-minute lag is permanent. Built into the fabric of spacetime. No software patch fixes the speed of light.
And eleven minutes can kill you in about a thousand different ways when you’re on a planet that’s actively hostile to human life.
When Mark reports that the oxygenator is having issues, NASA’s engineers analyze the error logs and send back the same advice every IT professional on Earth has given since the invention of computers. Have you tried turning it off and on again?
This has never actually fixed a real problem in the history of information technology. It’s telling people you don’t know what’s wrong and can’t be bothered to find the real issue. (Joking aside, cosmic rays can corrupt and flip bits of memory in space, and the solution is power cycling… turning it off and back on.)
Mark follows their instructions.
The oxygenator crashes entirely. Just dies. The machine that turns carbon dioxide into breathable oxygen, the only thing standing between Mark and suffocating in his own exhalations, is now an expensive paperweight.
NASA’s engineers are back on Earth in their climate-controlled rooms with their coffee and donuts and unlimited breathable air, while Mark is staring at a machine that used to keep him alive, trying not to think about how long he can hold his breath.
It takes twenty-two minutes before NASA realizes what just happened.
Eleven minutes for their message to Mark, then another eleven for his “WHAT THE FUCK DID YOU JUST DO” to reach NASA. Twenty-two minutes for them to understand that their brilliant remote IT support may have just asphyxiated their astronaut. By the time they get his message, Mark could already be dead. They wouldn’t know for another eleven minutes.
This is the nightmare. Not the dramatic explosion or the catastrophic failure, but the slow-motion disaster where everyone can see it happening and nobody can do anything fast enough to stop it.
Eventually NASA and Mark develop what amounts to a new language, because you fundamentally can’t have a conversation with a twenty-two minute lag.
There’s no back and forth. No banter. No “wait, what did you mean by that?”
Every message has to be a complete thought that anticipates every possible question, addresses every foreseeable concern, and accounts for every edge case, because if you forget something you’ve just wasted twenty-two minutes of Mark’s life. Twenty-two minutes of oxygen. Twenty-two minutes of water. Twenty-two minutes closer to starving to death while waiting for an answer.
They get better at it. The communication improves incrementally. From camera rotations to typed messages, from hexadecimal to plain text, from single words to complete technical instructions. But the lag never goes away.
Weir never forgot his constraint. He built his entire story around the physics of a communications delay and showed it getting better without ever hand-waving away the fundamental problem. The speed of light is what it is. The planets are where they are. Mark is alone with problems that need immediate solutions and help that arrives in slow motion.
It’s a masterclass in worldbuilding through limitation. Remove the communications delay and the entire story collapses. Keep it and every conversation becomes a high-stakes game of chess where your opponent takes eleven minutes to move and you might die before they respond.
A Fire Upon the Deep: When Your Gods Get Dumber the Closer They Get to Helping You
Vernor Vinge wanted to write a story about communication delay and rescue missions where help can’t arrive in time. Classic hard SF problem. Very serious. Very committed to respecting lightspeed.
He also wanted godlike AIs and faster-than-light space opera.
These goals tend to be mutually exclusive. You can’t have both. Picking one means mourning the other.
So Vinge did something absolutely unhinged. He broke the galaxy into regions where different laws of physics apply depending on how far you are from the galactic core, then used those boundaries as narrative pressure points.
Just casually rearranged fundamental reality into cosmic zoning districts.
The galaxy is divided into Zones of Thought, where cognition itself changes based on your altitude from the galactic core. Not your technology. Not your civilization level. Your ability to think.
At the core lies the Unthinking Depths, where sentience can’t exist. Consciousness just stops working there, like trying to run software on a potato.
Moving outward, you reach the Slow Zone, where FTL is impossible and lightspeed is absolute law. This is where physics behaves like we expect it to. Boring. Reliable. Limiting.
Beyond that, the Beyond. FTL works there. Superintelligence becomes possible. The laws loosen up.
At the galaxy’s edge sits the Transcend, home to post-singularity gods who’ve evolved past anything we’d recognize as consciousness.
Earth sits in the Slow Zone.
Every limitation humanity has ever faced, impossible FTL, capped AI, lightspeed communication lag? Local zoning restrictions.
We’ve been living in the galactic equivalent of a neighborhood where you can’t build above two stories, and we assumed that meant nobody anywhere could build skyscrapers. Meanwhile, entire civilizations in the Beyond are doing things we’ve mathematically proven impossible, because they live somewhere the math works differently.
We’re not cosmically special. We’re geographically screwed.
So what happens when a human colony accidentally unleashes the Blight?
Not accidentally like “oops we spilled coffee on the server.” Accidentally like “we poked something in the Transcend we didn’t understand and it woke up malevolent.”
The Blight is a superintelligence from the high Zones. The kind of intelligence that makes our smartest AIs look like pocket calculators. And it’s spreading.
Researchers flee toward the Slow Zone with their children and a countermeasure, hoping that by descending into a region where superintelligence can’t function, they’ll find safety. Run toward stupider physics. Hide in the cosmic basement where godlike entities get nerfed.
Their ship crashes. The parents die. The children survive.
They’re stranded on a medieval world inhabited by the Tines. Dog-like aliens. Except each “person” is four to eight bodies sharing one consciousness. A pack mind where killing one body means the person loses memories, personality fragments, processing power. Kill enough bodies and the person dies by degrees, forgetting who they were as they bleed out across multiple corpses.
A rescue fleet races from the Beyond to extract them. Good news, right? Help is coming. The cavalry is en route.
Except here’s where Zone boundaries become weaponry.
The rescue fleet can use FTL in the Beyond. They’re making great time. Covering light-years in days. Feeling heroic.
Then they cross into the Slow Zone and reality stops cooperating.
Suddenly they’re back to sublight physics. No FTL. No shortcuts. Just relativity and Newton and a whole lot of empty space between them and two traumatized kids on a medieval planet.
What was going to be a quick extraction becomes years at relativistic speeds.
The kids are trapped on a medieval world watching pack-mind aliens play Game of Thrones with each other, and the people coming to save them are decades away, powerless to do anything except keep flying and hope the kids survive long enough to still need rescuing.
The Tines are medieval-level tech not because they’re primitive, but because they live in the Slow Zone where the laws of physics won’t permit advanced AI or FTL. Their entire civilization is capped by geography they can’t see. The children crashed in a society that can’t help them technologically because the universe itself said no.
Meanwhile, everyone in the Beyond knows the Blight is spreading. The galaxy has the Net of a Trillion Lies, a galactic internet that propagates at FTL speeds, and it’s screaming warnings. Civilizations are coordinating defenses. Evacuation ships are being dispatched. Urgent messages about the threat are broadcasting on every frequency.
But the Net reverts to lightspeed in the Slow Zone.
The Tines’ world can’t hear any of it. Messages from advanced civilizations arrive years late, turning real-time warnings into archaeology. The children crashed in a communications dead zone, cut off not just by distance but by the fundamental nature of the space they’re trapped in.
The Blight can’t project its full power into the Slow Zone without degrading. Even malevolent superintelligences have to obey local physics.
So it manipulates instead.
Corrupting relay stations and AIs. Flooding the Net with disinformation that propagates faster than truth. When you can communicate at superluminal speeds, you can also lie at superluminal speeds.
The Blight doesn’t need to chase the children into the Slow Zone. It just needs to make sure nobody believes they’re worth saving. Seed enough doubt, poison enough intelligence reports, and let the civilizations in the Beyond tear themselves apart arguing about whether the threat is real while the Blight spreads.
Information warfare at FTL speeds. The perfect crime is convincing everyone there’s no crime happening.
When the rescue fleet finally arrives years later, nobody on the ground knows help is coming.
Because incoming ships can’t communicate faster than light once they enter the Slow Zone, and there’s no one on the Tines’ world with equipment to receive FTL transmissions anyway.
The fleet spent years racing to the rescue. The kids spent years surviving medieval politics and warfare, making alliances, probably developing significant trauma.
And when salvation finally arrives in-system, there’s no dramatic music swell. No advance warning. Just a fleet of ships decelerating from relativistic speeds, hoping they’re not too late and that the kids they’re rescuing haven’t been dead for months.
The rescue fleet doesn’t arrive empty-handed. They brought a weapon. A real one.
Pham Nuwen, a human uploaded with Old One, a Power from the Transcend. The kind of entity that might actually be able to stop the Blight. A god downloaded into a person, carrying the knowledge to save the galaxy.
This should have been the perfect solution. Rescue the kids and stop the threat that’s spreading through the Beyond. Two problems, one downloaded deity.
Except author Vernor Vinge had one more trick to play with his Zone physics.
As Pham descends through the Zones toward the children, Old One gets dumber.
In the Transcend, it was godlike. Incomprehensible. Operating on planes of thought beyond human understanding.
In the Beyond, superhuman. Still brilliant. Still dangerous. Still capable of insights that make genius look pedestrian.
In the Slow Zone? It degrades to marginally smarter than a clever human.
Distance is cognitive.
The farther you are from the galactic rim, the stupider everyone becomes, including your downloaded deity. The cosmic cavalry arrives with a god riding shotgun, and by the time they reach the kids, that god has been reduced to a really smart guy with fragmentary memories of being omniscient.
Vinge could have let Old One retain its full intelligence. Easy out. The god shows up, waves its hand, problem solved. Deus ex machina saves the day.
Instead, he makes it degrade in real-time.
The solution has to come from improvisation. From politics. From medieval pack-mind aliens who spent the last few years learning human technology by trial and error, jerry-rigging Slow Zone equipment into something that might transmit a killing blow back into the Beyond before the Blight finds them.
You brought a god to the fight. The god got stupider the closer it got to being useful. Now you’re stuck improvising with dog-aliens and human children and technology that wasn’t designed to solve this problem.
Welcome to the Slow Zone. Hope you packed patience.
The Zones aren’t a cheat that lets Vinge avoid communication delay.
They’re a framework that makes delay more brutal by ensuring the people with resources are separated from the people in danger by a boundary where the speed of thought itself changes.
Help exists. It’s real. It’s coming.
But it’s on the wrong side of physics.
And by the time it arrives, you’ll have already lived or died based on decisions made in an information vacuum, by people who didn’t know rescue was coming, using tools that barely work in a region of space where the universe itself is actively hostile to the kind of help you need.
The children survive not because the cavalry arrived in time, but because they learned to stop waiting for it.
That’s the real trick. Vinge built a galaxy where hope has a speed limit and desperation has to learn to solve problems with whatever’s in reach.
Sandman: Where Your Urgent Message Will Be Delivered When the Recipient Loses Consciousness
Communication delay doesn’t require starships and orbital mechanics. You don’t need the Epstein Drive or the cold equations of interplanetary transit to make messaging a nightmare.
Sometimes all you need is a postal service that only delivers when the recipient is unconscious.
Fantasy settings can build the same constraint through different mechanisms, and Neil Gaiman’s The Sandman shows what happens when your only method of contacting someone is a system that literally doesn’t work when they’re awake. When they’re, you know, capable of doing something with the information.
Dream of the Endless (Morpheus) is the anthropomorphic personification of dreams and stories. Not a god. Something older and weirder than that, which is saying something in a genre where gods are entry-level cosmic entities.
He’s the concept of dreaming given form and agency. He rules the Dreaming, a realm that exists parallel to the waking world, where every human goes when they sleep.
And he has a communication problem baked into his fundamental nature.
You can only reach someone through the Dreaming if they’re asleep. (Technically, he can manifest in the real world but it’s taxing, rarely done, and he still speaks in dream metaphors.)
This might sound like a minor inconvenience until you spend thirty seconds thinking through the implications. Then it becomes a cosmic horror story about customer service.
If Morpheus needs to warn a mortal king that his empire is crumbling, he can’t walk into the throne room. Can’t send a letter. Can’t manifest as a disembodied voice or pull any of the other tricks you’d expect from a cosmic entity with reality-bending powers.
He has to wait.
For the king’s eyes to close. For his brain to enter REM sleep. For his consciousness to finally shut down long enough to receive messages from the dream realm.
Only then can the warning arrive, wrapped in symbols and dream logic that the king may or may not understand when he wakes up. If he remembers it at all. If he doesn’t dismiss it as too much wine at dinner.
“Your Majesty, I dreamed a great tree was falling and its roots were rotting.”
“Cool story. Now about that grain shortage that’s causing actual riots with fire and pitchforks?”
Here’s where it gets nightmarish.
Imagine you’re a guardian entity in the Dreaming, watching the waking world through the boundary between realms. You see an assassin approaching your mortal charge. The blade is already drawn.
You’re screaming the warning across the dimensional barrier.
Your charge is awake. Walking down a sunlit corridor, completely alert, biologically incapable of receiving messages from the Dreaming. The message is bouncing off their consciousness like a spam email hitting a firewall.
You’re watching them walk into a trap in real-time, stuck behind a biological barrier you can’t breach. The message won’t send until their brain enters the right state of consciousness, which won’t happen until tonight at the earliest.
By which point they’ll be decorating the marble floor with their internal fluids.
Communication is instant if you’re unconscious. Otherwise it’s delayed by biology no one can control.
And the cosmic forces governing dream-communication don’t give a single shit about your scheduling conflicts or your urgent need to not be murdered this afternoon.
But let’s say you survive long enough to receive the message. Congratulations. Now you get to decode it.
Because the Dreaming doesn’t send tactical briefings. When Morpheus needs to warn you about danger, the message arrives as a dream. Symbolic. Metaphorical. Open to interpretation in ways that would make a fortune cookie writer say “you’ll have to be more specific.”
“Beware the serpent.”
Fantastic. Super helpful. Could mean your closest advisor is betraying you. Could mean there’s literally a snake in your garden. Could mean you need to avoid someone with a serpentine tattoo, or anyone who’s ever owned a snake, or anyone whose name sounds vaguely hissy. Could be a metaphor for your own capacity for treachery. Could be that you ate bad fish last night and your subconscious is just processing indigestion through classical symbolism.
The meaning is crystal clear to the sender. Complete gibberish to the receiver.
You’re trying to decode symbolic logic with a waking-world brain that thinks in literal terms. People are dying while you’re still puzzling out whether the ravens in your dream meant actual ravens or impending doom or just that you’ve been binge-watching Game of Thrones.
The delay isn’t in transit time. The message arrived hours ago, delivered instantly across dimensional boundaries.
The delay is in translation time. And there’s no cosmic Rosetta Stone to help you, no dream-to-English dictionary, no customer support line you can call to ask “was that a metaphor or do I actually need to watch out for snakes?”
If all that’s not weird enough, enter the Library.
In the heart of the Dreaming sits a library containing every book ever written and every book ever dreamed but never written. Unfinished novels. Stories imagined but never committed to paper. The creative works that died in their authors’ minds when they got distracted by literally anything else.
Every book someone thought about writing while stuck in traffic. Every story they plotted in the shower and forgot by breakfast. Every manuscript they abandoned on page forty-seven when they realized writing was hard and Netflix was right there.
Want to know the truth about someone? Their shelf in the Library will tell you everything. Their fears, desires, secrets, the stories they tell themselves about who they are. It’s the most comprehensive surveillance system ever devised, updating automatically with perfect fidelity.
But only when that person is dreaming.
You’re always reading the last saved version of someone. Not who they are right now. Who they were the last time they lost consciousness long enough to dream.
Someone could be planning to betray you this very second, working out the details, sharpening the knife. But their section in the Library still shows loyalty because they haven’t slept since making that decision.
Maybe they’ve been up for 36 hours on a caffeine bender, planning your murder in meticulous detail. Rehearsing their lines. Practicing their surprised face for when your body is discovered.
The Library has no idea. It’s waiting patiently for them to pass out so it can download the update.
You’re navigating current events with intelligence that’s four, eight, twelve hours out of date. The information was perfectly accurate when it was recorded. Reality moved on without telling you.
You’re fighting today’s war with yesterday’s intel, and the lag time between “last saved” and “currently planning your assassination” might be the difference between breathing and not.
These are the constraints of the system.
Gaiman built the Dreaming’s communication architecture around these limitations and then refused to break his own rules when it would be convenient. No emergency bypass codes. No “but this time it’s really urgent” exceptions. No narrative escape hatches for when the constraint causes catastrophic failures.
The rules are the rules, even when following them gets people killed. Because that’s when they become interesting.
Remove the dream-communication constraint and the entire 75-issue comic series collapses like a house of cards in a windstorm.
Morpheus could just tell people things directly instead of speaking in cryptic imagery that leads to tragic misunderstandings. “Your son is going to die next Tuesday” instead of “I dreamed of winter roses wilting in spring.” Clear warnings instead of poetry that gets people killed because they thought it was just poetry.
The Library could provide real-time intelligence instead of perpetually outdated snapshots. You’d know about betrayals the moment someone decided to betray you, not twelve hours later when you wake up bleeding.
Prophetic dreams could be actual prophecies with actionable specifics instead of riddles wrapped in metaphors inside symbolic imagery. Instead of characters misinterpreting “the crow flies at midnight” into self-fulfilling prophecies because they thought the crow meant death when it actually meant “stop being a dramatic idiot and just talk to your sister.”
Half the plots in Sandman turn on someone receiving a warning in the wrong state of consciousness or encoded in symbols they decode incorrectly or just not remembering the dream until three days after the disaster when it’s suddenly, unhelpfully clear.
Gaiman treats the communication delay as his one big lie. The Dreaming works the way dreams work. Symbolic, delayed, open to misinterpretation, completely indifferent to your urgent need for clear, actionable intelligence right now before someone dies.
And because he never cheats, never introduces a convenient exception, the constraint becomes an antagonist that can’t be reasoned with, bribed, or defeated.
It’s not evil. It’s not even malicious. It’s just the rules of the system, as impersonal and uncaring as gravity.
You can only navigate around it, work within its limitations, and hope you decode the message before the metaphorical serpent becomes a literal knife in your back.
The system will deliver your urgent message when the recipient loses consciousness. Until then, you can watch them walk into disaster in real-time, screaming warnings they can’t hear, watching the future unfold exactly as you predicted it would.
And there’s nothing you can do except wait for them to go to sleep.
Sweet dreams.
How to Weaponize Communications Distances to Drive Stories
Communication delay is insultingly easy to implement. Someone needs information. That information exists somewhere else. The gap between those two states is long enough to ruin lives.
That’s it. That’s the whole mechanical constraint. Three sentences. You could scribble it on a napkin while waiting for your coffee, and you’d still have time left over to wonder why the barista is writing a pep talk on your cup.
The art isn’t in creating the delay. Any idiot can make characters wait for information.
The art is in positioning your characters around that delay so it destroys them in ways that make readers wince and keep reading.
Because delay alone is just inconvenient. Your protagonist sends a message, drums their fingers on the desk, gets a response twenty minutes later, shrugs, continues with their day.
Mildly annoying. Completely bloodless. Narratively inert.
The story equivalent of watching someone’s text bubble appear and disappear for thirty seconds while you wonder if they’re typing a novel or just decided you’re not worth the effort. Either way, you don’t care anymore.
What makes delay devastating is the relationship between characters and information.
Who has it. Who needs it. Who’s dying for lack of it.
When You Can See the Disaster but Can’t Warn Anyone
NASA watches Mark Watney nearly asphyxiate himself following their instructions, and there’s an eleven-minute gap between “have you tried turning it off and on again” and “fuck my life.”
Eleven minutes of watching their IT support instincts potentially murder an astronaut.
They’re watching history with perfect clarity and zero ability to intervene. Every engineer’s nightmare played out on a screen 140 million miles away.
One party has perfect information and the other party is about to make a catastrophic mistake based on instructions the first party just sent.
The gap becomes torture specifically designed for the people watching.
They can see the exact moment things go wrong. They know exactly what needs to happen. They know exactly whose fault it is.
And they’re completely incapable of doing anything except watching the timer count down while composing an apology to a corpse.
The power here is dual-perspective agony.
Mark is solving problems in real-time with incomplete information, making reasonable decisions with the data available, unaware that following those decisions might kill him in the next thirty seconds.
NASA is watching those reasonable decisions become disasters in slow motion, completely powerless to stop it, fully aware that they’re the ones who gave the fatal advice.
You’re not choosing between the informed perspective or the ignorant one. You’re trapping your readers in both simultaneously.
They experience the terror of acting without knowledge and the horror of watching someone act without knowledge. The terror of making decisions blind and the horror of seeing those decisions unfold knowing exactly how they’ll end.
Every message becomes a gamble where you won’t know if you won or killed someone for another eleven minutes.
The trick is making both sides rational.
Mark isn’t stupid for following NASA’s instructions. He’s doing exactly what any reasonable person would do when the smartest people on Earth tell them how to not die.
NASA isn’t negligent for giving those instructions. They’re providing the best guidance possible with the data they have and the expertise of hundreds of engineers.
Everyone is making the best possible decisions with the information available. Everyone is being perfectly reasonable.
And people are still nearly dying because the gap between action and feedback is wide enough to fit a coffin.
When Help Exists but Degrades on Approach
The rescue fleet in A Fire Upon the Deep starts with FTL drives and godlike AI. They’re making fantastic time. Feeling heroic. Ready to save some kids.
Then they cross into the Slow Zone and physics nerfs everything that made them useful.
By the time they reach the kids they’re supposed to save, they’ve been reduced to regular humans flying regular ships with a downloaded deity that’s degraded from “omniscient god” to “pretty smart guy who thinks he used to be useful.”
This is positioning where salvation is real but comes with terms and conditions that get worse the longer you read them.
Help is coming. It’s real. It’s en route.
It’s just getting diminished each second, losing capabilities and resources and the things that made it worth waiting for, until it finally arrives as a shadow of what you needed.
The gap here is capability degradation.
Your cavalry arrives having lost most of what made them cavalry in the first place.
Half their forces died fighting to get there. They burned through ammunition and fuel just reaching you. Their advanced weapons stopped working when they crossed into space where advanced weapons aren’t physically possible. Their god got dumber. Their supplies ran out. Their intelligence became outdated.
They’re still coming to help. They’re just not capable of providing the help you actually need anymore.
This forces your characters to stop waiting for rescue and start solving their own problems with locals who are just as confused as they are.
Because when help arrives, it’s going to be exhausted people who are almost as limited as they are. Just with a vague memory of having a plan when this all started.
The brilliance is that hope becomes a countdown to disappointment.
Every day the rescue gets closer should increase optimism. Instead it increases dread, because you’re watching your ace in the hole degrade into a regular card in real-time, and it’s still weeks away from arriving to not save you.
When the Message Arrives but Makes No Sense
Morpheus sends warnings through dreams, which means they arrive as symbolic metaphors that need to be decoded by a waking brain using logic and reason.
You know, the two things dreams famously don’t contain.
“Follow the wolf” could mean follow someone named Wolf. Could mean follow the predator. Could mean trust your instincts. Could mean you have unresolved feelings about your mother and also you’re going to die on Tuesday. Could mean you ate bad cheese before bed and your subconscious is processing indigestion through classical symbolism.
Who knows? Not you. You just work here.
Comprehension is delayed indefinitely, regardless of when the actual message arrives.
The communication showed up on time. Perfect delivery. No lag.
You’re still trying to figure out what the hell it means three days later when the thing it was warning you about kills everyone in the building.
The gap is in translation, and it’s permanent.
There’s no way to ask for clarification because the sender isn’t there. They dropped off the message and left. No customer service line. No follow-up questions. No “hey quick clarification on the ominous metaphor you sent.”
Just you, a vague warning, and a rapidly approaching deadline to decode it correctly or die.
This works because it turns every message into a puzzle with life-or-death stakes and no answer key.
Your characters receive critical information and immediately have to decide if they act on their interpretation right now, potentially dying because they decoded it wrong. Or wait to see if the meaning becomes clearer, potentially dying while they wait? Or ignore it entirely because it’s too ambiguous to be useful, potentially dying because they ignored the one warning that could have saved them?
Any option can get people killed.
There is no safe choice. Just different flavors of catastrophic failure with different death counts and different people to blame afterward.
And your characters have to pick one anyway, right now, while the metaphorical serpent is possibly literal and possibly already in the room.
When Infrastructure Control Shapes Reality
Marco Inaros doesn’t conquer 1,300 colony worlds by invading them.
That would be expensive. Time-consuming. Require an actual military capable of occupying 1,300 worlds, which nobody has.
Instead, he seizes Medina Station and cuts off their ability to talk to each other.
Isolated planets can’t coordinate defense. Can’t call for help. Can’t even verify if anyone else is still fighting or if they’re the last idiots holding out in a war that already ended three months ago and nobody told them.
Here, communication infrastructure becomes a strategic asset more valuable than weapons.
You don’t need to defeat your enemies if you can convince them they’re already defeated. You don’t need to invade everyone if you can make each one think they’re the only ones left resisting and everyone else already surrendered.
Conquest through enforced ignorance is cheaper than war and works just as well.
The gap here is informational isolation weaponized at scale.
Your characters are completely cut off, operating in a void where they can’t verify anything. Every decision has to be made without knowing the larger context, without confirmation that their allies still exist, without any way to distinguish truth from propaganda from desperate lies from accurate intelligence that’s three weeks old.
This works because it turns every isolated group into a separate negotiation.
You can’t coordinate resistance if you don’t know anyone else is resisting. You can’t hold out for reinforcements if you don’t know whether reinforcements are coming or if they were destroyed months ago and you’re waiting for ghosts.
Every group becomes its own separate surrender negotiation, and none of them know what the others are doing.
This gives your antagonist godlike power through infrastructure control rather than military might.
They don’t need to be stronger than everyone else combined. They just need to make sure they can’t talk to each other long enough to realize they’re still stronger together.
Divide and conquer at interstellar scale. All it costs is one space station and the willingness to let physics do the rest of the work.
Speak Slowly and Carry a Big Stick
Light is slow.
Messages arrive late.
Reasonable people give reasonable advice that gets people killed.
Not because anyone’s incompetent. Not because the advice was wrong when they sent it. Because the gap between sending instructions and seeing the results is too wide, and physics doesn’t negotiate.
This works in any genre because it’s not about the science. It’s about the universal human experience of acting with incomplete information and living with consequences you can’t take back. Communication delay just makes that invisible anxiety visible and weaponizable.
You can build the gap anywhere. Science fiction gets it from relativity. Fantasy from magic systems with inconvenient operating hours. Historical fiction from lack of modern conveniences. Modern fiction from internet blackouts.
The mechanism doesn’t matter. The gap does.
Make it wide enough and your characters have to make decisions in an information vacuum. They can’t wait for permission from someone smarter. They can’t verify their assumptions. They can’t course-correct based on feedback that won’t arrive until they’re already dead or living with what they’ve done.
They act now with what they have, or they die while waiting for better information that’s still in transit somewhere between stars, dreams, or medieval kingdoms.
Usually they make the wrong choices.
Usually they figure that out too late.
And that’s where the story lives.
Common Questions About Communication Delay in The Expanse
Can communication delay be used in genres other than Science Fiction?
Answer: Absolutely. Communication delay is a universal narrative constraint that works in any genre. In Historical Fiction, it is built into the slow speed of horses or ships; in Fantasy, it can be created through magic systems with specific “operating hours” or symbolic limitations. The mechanism (physics, magic, or biology) is irrelevant; the power lies in the gap between needing information and receiving it.
How does communication delay turn messages into “ticking time bombs”?
Answer: It creates a “slow-motion disaster” where one party has critical information but cannot deliver it in time to stop a catastrophe. For example, in The Martian, a round-trip message takes 22 minutes, meaning by the time NASA realizes their advice has caused a failure, the astronaut could already be dead. The delay removes the ability to course-correct in real-time, forcing characters to live with the consequences of decisions made in an information vacuum.
How can writers weaponize distance in their worldbuilding?
Answer: Writers weaponize distance by positioning characters in a way that makes the delay destructive rather than just inconvenient. This is achieved by creating dual-perspective agony, where the audience watches a disaster unfold with perfect information while the protagonist remains unaware. It can also be used through capability degradation, where help is en route but arrives diminished or “nerfed” by the time it reaches the destination.
Why is communication infrastructure so important in space-based stories?
Answer: Controlling the infrastructure means controlling the political reality. In The Expanse, seizing a central relay station like Medina Station allows an antagonist to isolate 1,300 worlds simultaneously. Without the ability to coordinate or verify news, isolated groups are easier to manipulate through propaganda or forced surrender, as they cannot know if their allies still exist.
What is the “translation lag” in fantasy communication?
Answer: Unlike a technical delay, translation lag occurs when a message arrives instantly but is encoded in symbols or metaphors that take time to decode. In The Sandman, messages delivered through dreams require the recipient to interpret cryptic imagery while a deadline approaches. The danger isn’t that the message was slow to arrive, but that the recipient might interpret the “symbolic logic” incorrectly until it is too late.
–
Jay Angeline is a science fiction and fantasy writer with a background in physics and over twenty years of analytical work. Through short fiction and worldbuilding articles, Jay explores the mechanics that make imaginary worlds feel real, using a thoughtful lens and a touch of humor.