FWD: Monarch concerns
FWD Monarch Concerns
SubjectLiam Burke, Beth Wilder
AuthorCharlie Wincott
DateOctober 8th, 2016
ActAct 2: Perfect Place to Hide Something
PartAct 2, Part 1: Industrial Area
LocationIndustrial Area Security Station
PreviousInternal Monarch Comms 1
NextInternal Monarch Comms 2

FWD: Monarch concerns is a email Narrative Object found in Act 2, Part 1 of Quantum Break. The email details Liam Burke's message to Beth Wilder and Charlie Wincott's report of it.


DATE: OCT 8, 2016 – 7:10am
SUBJECT: FWD: Monarch concerns

Mr. Hatch,

I’ve been monitoring company email servers and found something interesting. Just thought you might want to know your golden boy has been a bit snoopy as of late. Attaching his email below:

DATE: OCT 8, 2016 – 5:10pm
SUBJECT: Monarch concerns


I’m starting to grow suspicious about what’s going on here. I have a hunch you feel the same way. I’ve been allowed a lot of freedom to come and go in my position, but it comes at the cost of very low clearance. Most members of the team know something I don’t and they’re not eager to share. Tomorrow’s operation is more than a simple retrieval mission. There are dates and times marked with detailed events that are expected to come to pass. I’ve seen charts with “Fracture – 4:15am” labeled. It’s not too much detail for plan, it’s like it’s all been mapped out. How?

Something big is coming. I and feel it. They told us our directive is to protect our world from dangers that lie ahead. If that’s so then why do I get the feeling there’s something coming that we’re doing absolutely nothing to stop? And if everybody else knows this then why the hell is nobody acting on it? I can’t sit back and watch if there’s even a chance that this could put Emily in danger. I need to know more. Serene won’t answer my messages. Hatch is a closed book. I’m hoping you’re an open one.


Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.