Answers.Body: <p>The calculation of <strong>next</strong> or <strong>past 3 months</strong> was decidedly dodgy for relative dates in searches (which is why these have been replaced with 90-day intervals in v4.7). The same method may apply for the membership status update.  </p>
  
  <p>If I remember correctly, it calulates the number of days in three calendar months starting with the current month.</p>
  
  <p>So I think you may find that for an end date of March 31, CiviCRM will change the status after 31(March) + 30 (April) + 31(May) = 92 days, which should be 2 July.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-01T07:18:26.563Z
Answers.Text: Bang on, thank you. I can reset to 91 days in there case.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-01T04:26:47.437Z
Answers.LastActivityDate: 2016-07-01T04:26:47.437Z
Answers.UserDisplayName: JoAnne
Body: <p>Wondering how civi calculates 3 months, given that month lengths vary, eg they could be between 89 to 92 days (I think).</p>
  
  <p>I am asking because we have End Date March 31, and then Grace for 3 months. Here, in NZ, it is July 1, but Grace members are still showing Grace, and not clear if something has failed (yes scheduled job is enabled and running and no log errors), or if the 'calculation' of 3 months might be a bit stretchy.</p>
  
Tags: <civimember>
Title: When does a '3 month' period in a membership status actually roll over
ThreadText: # When does a '3 month' period in a membership status actually roll over
  
  (Asked by: username_0 on 2016-07-01)
  
  Wondering how civi calculates 3 months, given that month lengths vary, eg they could be between 89 to 92 days (I think).
  
  I am asking because we have End Date March 31, and then Grace for 3 months. Here, in NZ, it is July 1, but Grace members are still showing Grace, and not clear if something has failed (yes scheduled job is enabled and running and no log errors), or if the 'calculation' of 3 months might be a bit stretchy.
  
  **Tags:** civimember
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-07-01. Score: 2 | Accepted answer
  
  The calculation of **next** or **past 3 months** was decidedly dodgy for relative dates in searches (which is why these have been replaced with 90-day intervals in v4.7). The same method may apply for the membership status update.
  
  If I remember correctly, it calulates the number of days in three calendar months starting with the current month.
  
  So I think you may find that for an end date of March 31, CiviCRM will change the status after 31(March) + 30 (April) + 31(May) = 92 days, which should be 2 July.
  
  > **Comments:**
  > **username_0**: Bang on, thank you. I can reset to 91 days in there case.  
  
  ---
  
  