11 November 2021

Working With A Timeline


I have written before about the importance of a believable timeline to your work-in-progress, especially to your longer pieces. The rule of thumb I have consistently followed is "the longer your piece, the more detailed your timeline needs to be."

There is an inherent logic to this maxim. The longer your piece the easier it is to lose track of pieces of your plot, either details or entire subplots. It's easy for things to get away from you over the course of a 90,000 word novel. And while it's also possible to lose the thread in a short story with a length of a few thousand words, you're less like to do so because you're juggling less words, less scenes, less characters, and less action.

Author Nancy Christie lays out a lot of great guidelines for getting the most out of your respective timeline in a blog post on her website. You can read it here.

For today's blog post I am going to offer up a detailed timeline of actual events as they occurred during a pretty emotionally charged (for myself, and my family, at least) event: my nine year-old son's recent surgery. Okay, here goes.

Tuesday, September 28th:

Doctor's appointment with a specialist regarding my son's persistent health condition. Discussion of options, including surgery to correct the condition. Decided on surgery and scheduled a call from the specialist's support staff.

Every day for the next two weeks:

Played phone tag with the specialist's support staff, who seemed unable or unwilling to call on our primary number (my wife's cell) rather than our home number. Calls to the support staff's number in response to the messages they left on our home voicemail went unanswered, requiring the leaving of multiple voicemails consisting of detailed requests for information/guidance on our part.

Tuesday, October 12th:

Finally made contact with specialist's support staff, Scheduled surgery for Tuesday, November 2nd. received instructions for pre-surgery preparation, including a flu shot and a COVID test for our son on the Sunday before his surgery. Also informed that contact via our HMO's website could sub in for actual phone contact going forward.

Every day for the next three weeks:

Played another round of phone tag with the specialist's support staff, who, yet again, seemed unable or unwilling to call on our primary number (my wife's cell) rather than our home number. Calls to the support staff's number in response to the messages they left on our home voicemail went unanswered, as did repeated email requests for information/clarification as to what other information the specialist's support staff required in addition to everything we had provided thus far. This again required the leaving of multiple voicemails consisting of detailed requests for information/guidance on our part.

Friday, October 29th:

Finally made contact with the only member of the specialist's support staff able to understand the phrase, "Please contact us on our primary number, rather than the secondary one listed in our patient profile." Very knowledgeable, and very helpful, EXCEPT when it came to setting the actual time of the surgery on Tuesday, November 2nd. Knowledgeable support staff member assured us that these schedules tended to firm up the day before said scheduled surgery. And that "someone from this department will definitely called you on Monday, November 1st, with your son's scheduled surgery time, as well as with detailed instructions for when/how to get there."

Sunday, October 31st:

Our son receives both his flu shot and his COVID test. Went trick-or-treating that night as planned. Still wading through the pile-o-candy he plundered from the willing hands of our very generous neighbors.

Monday, November 1st: 

Waited all day by the phone for the promised final call from specialist's support staff. No call was forthcoming. Finally at 3 PM called support staff number and waited on hold until after 5 PM. Finally hung up and called the 800 consulting nurse service. The consulting nurse got into the HMO's system and looked up our son's scheduled starting time for the next. Said that according to the system, our son was scheduled for surgery at 7:40 AM the following morning. We asked whether that was when he went in to surgery, or when we needed to have him there. Consulting nurse assured us that according to the information available in the H MO's system, 7:40 was when we needed to have our son there. We also received pre-surgery dietary instructions (no food after midnight, etc.).

Tuesday, November 2nd:

6:45 AM: Putting on my shoes preparatory to driving our son to the hospital, we received a call from specialist support staff. Luckily this time the call came on my wife's cell, and she was able to catch it before it went to voicemail. "Where are you?" the caller demanded. "Surgery is in an hour, and you're supposed to be here an hour before!"

My wife explained that we never received the promised call from specialist's support staff on Monday, and further how we called the consulting nurse service just to get his surgery time at all. "Nevermind that!" the caller fairly shouted. "You need to get here NOW!"

7:25 AM: After breaking the sound barrier to get to downtown Seattle in heavy early commute traffic and in the middle of a driving rainstorm (I know, heavy rain in Seattle, in November? Who'd have thought?), my wife directed me into the first available parking structure labeled with the name of the hospital where our son was scheduled for surgery. Wrong building. After several wrong directions from well-meaning employees, found the right building, and trudged 5 long blocks to it in a pouring rainstorm.

7:38 AM: Checked in at surgery front desk.

7:50 AM: Checked in by surgery staff, escorted to pre-op prep room. Quick side point: everyone on this hospital staff was friendly, professional, kind, and compassionate. From the point we checked in we were in the best of hands. In fact, the exact term we heard over and over again from the staff who took part in our son's surgery was, "We'll take good care of him." And they were as good as their word.

8:25 AM: After meeting the anesthesiologist, the surgery nurses and meeting again with the specialist who would perform  the surgery, our son was wheeled into the surgical station and placed under anesthesia. We adjourned to the waiting room to do just that.

Wait.

And wait.

And wait.

(The surgeon had assured us that the operation would take anywhere from an hour to to two hours, based on when she found when she made her incisions. Two days after this surgery, a voicemail from the surgical staff with date/time stamp of 11/2/2021 at 9:32 AM popped up on my iPhone. In it the staff member who called-my phone never rang- stated that our son was fully anesthetized and going in to surgery at that time.)

11:25 AM: My wife's cellphone battery dies. She returns to the car to both charge her phone and move the car to the parking garage for the building where our son actually had surgery.

11:28 AM: Surgical staff come find me in the waiting room after being unable to raise my wife on her cell. I go upstairs to where my son is coming out of surgery.

11:32 AM: I get a seat next to the bed where my son is being brought out of anesthesia. The specialist informs me that our son did very well and we talk about follow-up procedures and scheduling, etc. The anesthesiologist enters and begins to remove the tubes connected to my son as he's coming out of anesthesia. She and the attending nurse anesthetist cheerfully dodge my son's flailing arms as he's beginning to be aware of his surroundings, all while deftly removing every tube connected to him. It's clear that this is not their first rodeo.

12:15 PM: My wife meets us in a recovery room on the 9th floor, where we're informed that our son will need to eat something and keep it down before we can take him home. When asked what he would like to eat, our nine year-old repeatedly responded: "Nothing, I just want to go home."

2:00 PM: After repeated attempts to order food for our son (no reply to several calls to the dietary department), the recovery room nurse succeeded in contacting our specialist, who told her what she had told me when our son was coming out of anesthesia: he didn't need to eat. He could just go home. I had assured the nurse of this, but she did her job properly and, since it apparently wasn't recorded that way in our son's chart, she followed protocol until able to contact our specialist for confirmation.

2:30 PM: Our specialist, thinking she was doing us a favor, arranged for our son's post-surgery medication to be available at the busiest downtown Seattle pharmacy our HMO runs. We parked there and forty-five minutes later my long-suffering wife emerged from the building with our son's prescription in hand. At this point we realized none of us had eaten that day.

3:10 PM: After making our way out of downtown Seattle during early rush hour traffic, we pull in to a Burger King to get something in our stomachs.

3:17 PM: We order.

3:20 PM: We pay at the window.

3:35 PM: We FINALLY get our order. Which all three of us wolf down.

4:00 PM: We arrive at home.

4:03 PM: It stops raining for the first time all day. Because of COURSE it does.

4:15 PM: Our entire family crashes. Thank God for California King beds!

*************

And that's it for this particular timeline. See? If it's detailed enough, the resulting story will be the richer for it, am I right?

And on that note, that's all for me this time around.

See you in two weeks!

7 comments:

  1. I am glad your son's surgery was a success and hope that his recovery is going smoothly.
    Automated phone systems are one of the curses of civilization.

    ReplyDelete
  2. Thank God all went well with your son's surgery. The daily log of such a day is enough to make me throw in the towel and go right back to bed myself.
    And Janice is right - we are still getting phone messages about my stepson's appointments from a clinic in Jacksonville, Florida (which means, of course, that he never receives the notices). I have called repeatedly to try to get them to understand that I live in South Dakota, and he isn't here. Two years & counting, no luck.

    ReplyDelete
  3. Our hopes for a speedy recovery.

    ReplyDelete
  4. Jumping Murphies. So sorry that that happened. We had our own fascinating experience this week with what is sometimes humorously referred to as America's healthcare system. I'll tell you about it some time. At least it didn't involve children. Best wishes to your family.

    ReplyDelete
  5. Wow. I'm glad your son's surgery went well. The less I say about automated phone systems, the better.

    On the timeline, yes. When I was still writing novels, I always made a list of scenes in chronological order to make sure everything happened in the right order and with the right people in the right place. Since I tend to use mulitple POV in my novels, I had to make sure where everyone was at any given time and what they knew, especially if someone else didn't know it.

    ReplyDelete
  6. Whoa! I'm glad your son is doing well despite the phone monkeys. My best to you, your wife, and your boy.

    ReplyDelete
  7. The main thing, my hopes to you and your family on the continued recovery.

    ReplyDelete

Welcome. Please feel free to comment.

Our corporate secretary is notoriously lax when it comes to comments trapped in the spam folder. It may take Velma a few days to notice, usually after digging in a bottom drawer for a packet of seamed hose, a .38, her flask, or a cigarette.

She’s also sarcastically flip-lipped, but where else can a P.I. find a gal who can wield a candlestick phone, a typewriter, and a gat all at the same time? So bear with us, we value your comment. Once she finishes her Fatima Long Gold.

You can format HTML codes of <b>bold</b>, <i>italics</i>, and links: <a href="https://about.me/SleuthSayers">SleuthSayers</a>