Community› The Bump Message Boards› TTC After a Loss
TTC After a Loss
New Discussion

This may be a stupid question...

forevermyfenixforevermyfenix member
in TTC After a Loss
If you participate in the Month Check Ins, do you use the EDD or the actual birth/loss date? We lost Fenix July 31st, but he was due Aug 26th. I want to say maybe I should follow the July board, but I'm conflicted. Because Fenix was 36 weeks I guess he holds closer to his birthdate than his EDD, but I can't explain any logic behind that. 

So, which do you follow, EDD or loss date?
BFP #1 12/19/13 We lost our Fenix 7/31/14 at 36 weeks due to torn umbilical cord
Lilypie - Personal pictureLilypie Angel and Memorial tickers
My Chart TTA until Feb 2015
~*ALL AL WELCOME*~
image
Report Reply to Post

Re: This may be a stupid question...

  • tlc35tlc35 member
    Most people post in the month check in of their EDD, but if you feel like you belong in July I'm sure you would be welcomed.
    Me: 37                                               
    DH: 45
    BFP #1 3/19/14  EDD 11/29/14 MMC D&C 4/24/14
    BFP #2  12/4/14 Beta #1 218 at 12dpo Beta #2 1055 at 16dpo
    Saw heartbeat 12/29.  Please be a rainbow.
    imagerainbows
              
    All welcome                                   
                              
    Report Reply
  • Loading the player...
  • forevermyfenixforevermyfenix member
    Thanks ladies! @holdingouthope I was debating into'ing in both, but was worried that it would be considered "double dipping" or something like that. Then again, what better way to get closer to more people here on TB? 
    BFP #1 12/19/13 We lost our Fenix 7/31/14 at 36 weeks due to torn umbilical cord
    Lilypie - Personal pictureLilypie Angel and Memorial tickers
    My Chart TTA until Feb 2015
    ~*ALL AL WELCOME*~
    image
    Report Reply
  • PinkCaminoPinkCamino member
    (((Hugs))) you participate in whichever check in you want and feel comfortable in.
    Report Reply
This discussion has been closed.
Choose Another Board
Search Boards
"
"