diff --git a/reference/charter.rst b/reference/charter.rst
index f679400ca..bba427d4e 100644
--- a/reference/charter.rst
+++ b/reference/charter.rst
@@ -123,9 +123,11 @@ Election for PTL seats
 ======================
 
 PTL seats are completely renewed every development cycle. A separate election
-is run for each project team. These elections are collectively held no later
-than 3 weeks prior to each cycle final release date (on or before 'R-3' week)
-and should be held open for no less than four business days.
+is run for each project team. The election nomination as well as the voting
+period should be open for fourteen days (2 weeks for each phase). These
+elections are collectively held (from the nomination start date until the
+voting end date) no later than 2 weeks prior to each cycle final release
+date (on or before 'R-2' week)
 
 If a PTL seat is vacated before the end of the cycle for which the individual
 was elected or after the election (means leaderless project), the TC will
@@ -165,9 +167,11 @@ The TC seats are partially renewed twice a year using staggered elections.
 Members are elected for a term that expires at the conclusion of the second
 scheduled election after the start of their term or after 14 months, whichever
 is shorter. For this election we'll use a multiple-winner election system
-see below). The election is held no earlier than 6 weeks and no later
-than 4 weeks prior to each cycle final release date (between 'R-6' and 'R-4'
-week), with elections held open for no less than four business days.
+see below). The election nomination as well as the voting period should be
+open for fourteen days (2 weeks for each phase). The election is held
+(from the nomination start date until the voting end date) no earlier than
+8 weeks and no later than 2 weeks prior to each cycle final release date
+(between 'R-8' and 'R-2' week).
 
 If required, TC and PTL elections can be held as combined election.