Renewals use two date windows: Closed Won is allowed no more than 30 days before the renewal date, and a 15-day window follows it.
Key takeaways
- Keep a stage for deals waiting on signatures, so a ready renewal stays visible without being marked won.
- Let early paperwork show readiness, not a won date.
- Set the close date to the approval submission date for a renewal achieved within 15 days after the renewal date.
- Mark a renewal Closed Lost if it is not achieved within that 15-day window, and set a reminder for its end.
Why renewals need two windows
A renewal looks simple on a calendar. The subscription ends on a date, the customer signs, and the deal moves to Closed Won. In a CRM, though, the stage often changes before the paperwork is final, or it stays open long after the renewal date has passed. Either way, the numbers drift. Forecasts count deals that are not yet booked, quota credit lands in the wrong month, and the lost-deal list misses renewals that quietly died.
Two date windows can keep most of this in check. The first window sits before the renewal date and controls how early a renewal may be marked Closed Won. The second sits after the renewal date and controls two things: how late a renewal can still count as won, and when a renewal that never arrived must be marked Closed Lost.
The rules in this post come from one public example: the sales order processing page in GitLab's handbook, which states its renewal timing rules in specific terms. We use it because it is concrete enough to test against. It is one company's policy, not a standard that applies to every firm. Your windows may be shorter, longer, or measured from a different date. Write yours down, then apply them the same way every quarter.
The sections below follow one example renewal from start to finish, then turn the example into CRM settings you can copy.
Our example renewal
Throughout this post, we follow one customer. Their subscription has a renewal date of May 1, 2026. At each step, we decide two things: what the stage should be, and which date belongs in the close date field.
The timeline has three moments that matter:
- Early in the cycle, the renewal is worked out and all necessary booking documents are received on March 1, 2026.
- The renewal date itself is May 1, 2026.
- Suppose the customer signs a few days after May 1, still inside the 15-day grace period.
The third moment is where most teams get stuck. Did the deal close on the signature day, or on the day someone submitted the approval? Did the March 1 paperwork make the deal won? The two windows answer those questions, and the rest of this post walks through each one.
Each of these moments should leave a trail in the CRM. If a rep cannot tell from the record which step a deal is on, the stage is carrying too much of the load, and the dates are doing too little.
Window one: Closed Won cannot start too early
The first window is about the start. The GitLab page says that renewal opportunities will be Closed Won no more than 30 days prior to the Quote Start Date, which it identifies as the renewal date. Read that carefully. The rule limits how early a renewal can be marked won. It does not stop the work from starting early.
For our customer, the earliest Closed Won date falls 30 days before May 1, 2026. Anything before that point stays open, even when the paperwork is complete. A deal can be ready and still not be won.
The March 1, 2026 documents fall well outside that window. The GitLab page describes this same pattern: the renewal is worked out early, and all necessary booking documents are received on March 1, 2026, in an example where the renewal date is May 1, 2026. Early paperwork is valuable. It means the deal is ready when the window opens, and the team is not chasing paperwork at the last minute. But receiving documents early does not, by itself, move the opportunity to Closed Won.
Early approval does not change credit either. The page states that quota credit and commission will align to the booking policy even if approvals are obtained to invoice the transaction earlier than 30 days prior to the Quote Start Date. For a revenue leader, that is the most important sentence in the window. A rep who gets approval early should not assume commission timing moves with it. Decide now whether your plan works the same way, and write it into the comp plan so nobody has to guess later.
The GitLab page also describes the path to approval. Before a renewal is submitted, the opportunity stage needs to be changed to 6 - Awaiting Signatures, and then the Submit for Approval button should be clicked. You do not need GitLab's stage numbers. You do need a stage that means "waiting on signatures," so a ready deal stays visible without being marked as won. If your team builds its stages from scratch, name that stage in plain words and write down what has to be true to enter it. Use the stage to show what is waiting on the customer, not to show a date.
Store the dates in fields that are separate from the close date. Two CRMs show how this works in practice. HubSpot lets you create custom deal properties for the information your business needs, and Close lets you create custom fields for opportunities under Settings > Custom Fields > Opportunities. Make one field for the document-received date and one for the signature date. The close date then has a single job: showing the date the window rules say it should show.
Window two: the 15 days after the renewal date
The second window starts on the renewal date and runs 15 days. The GitLab page says that if a renewal is achieved within 15 days after the Subscription Renewal Date, the opportunity will be Closed Won on the date of approval submission. Two parts of that sentence need attention.
First, the grace period is short and fixed. For our customer, it ends 15 days after May 1, 2026. A signature on the first day of that period and a signature near the end get the same treatment. The window does not stretch because the customer is slow, and it does not shrink because the rep was early.
Second, the close date is the date of approval submission, not the date of signature. Suppose the customer signs inside the window, but the approval goes into the system a day later. Under this policy, the close date is the submission day. The signature day is still useful, so record it in its own field, but it should not drive the close date.
The same rule covers a renewal that closes on the first day of the grace period and one that closes near the last day. In both cases the rep records the signature date, submits the approval, and lets the approval submission date set the close date. A review that treats the two differently will produce close dates that are hard to explain later.
This is a policy choice, and other teams choose differently. Some prefer the signature date because it matches what the customer's records show. The GitLab approach has a practical advantage: the approval submission is a date your own team controls, so the close date does not depend on when a customer's signed copy reaches your inbox. Pick one approach, write it down, and make every rep follow it. Mixed approaches make the report hard to trust.
The page ties the Closed Won date to approval submission, but the sources in this post do not define what "achieved" means. Ask your team to settle that before the window opens. Is a signed order achieved? Is a verbal yes? Once the definition is written, a rep can check the record against it instead of arguing about it after the fact.
When a renewal must be Closed Lost
The other side of the second window is a hard deadline. The GitLab page states that renewal opportunities must be Closed Lost if the renewal is not achieved within 15 days after the Subscription Renewal Date. The word "must" matters. If the renewal is still open after the window closes, the stage is wrong, and a rep does not get to keep it open while hoping.
For our customer, the question on the day after the window closes is simple. Was the renewal achieved within 15 days after May 1, 2026? If yes, the opportunity is Closed Won with the approval submission date. If no, it must be Closed Lost.
No one can hold a 15-day clock for every renewal in their head, so set a task. When the renewal date is entered, create a reminder for the end of the window on that renewal record. Have the task say what to check: whether approval was submitted, and what stage the deal sits in. The task is what makes the rule happen on time. A rule nobody is reminded of is only a suggestion.
A renewal that sits open past its window inflates pipeline. It makes the forecast look healthier than it is, and it hides churn that a revenue leader needs to see. Closing it on time is what turns the lost list into a reliable record of what went wrong, rather than a list of deals that someone forgot to update.
Illustrative example: a renewal dated 1 June
Take a renewal dated 1 June. Closed Won can be set from 2 May, which is 30 days before the renewal date. The grace period runs 15 days after 1 June, to 16 June. If the customer signs on 8 June and the rep submits approval on 10 June, the close date is 10 June. If the renewal is not achieved by 16 June, it must be marked Closed Lost.
Setting up the CRM so the windows show
The setup is simpler than it sounds. Everything else is a report.
Here is the full timeline for our example, with the stage and the date each step should produce.
| Point in time (example) | What the stage should show | What to record |
|---|---|---|
| March 1, 2026: documents received | Waiting on signatures, not won; Closed Won is not yet allowed | Document-received field |
| 30 days before May 1, 2026 | Closed Won can first be set | Close date set only when the deal is won |
| May 1, 2026: renewal date | Grace period starts | Renewal date field |
| Within 15 days after May 1, 2026 | Closed Won if achieved | Close date equal to the approval submission date |
| After 15 days, not achieved | Closed Lost | Lost reason recorded |
The March 1 row is worth a second look. The documents are in hand, which is good news for the renewal, but the 30-day rule means the deal cannot be marked won yet. The easy mistake is to let early paperwork pull the stage forward. The stage column keeps the two facts apart.
For the reporting side, a monthly export is the simplest check. Pipedrive's help page gives "All lost deals" as an example of selecting only lost deals when exporting. If the export shows a gap, fix it in the CRM rather than noting it in the report.
The same idea works in any CRM. Filter for renewals that are still open with a renewal date already past the 15-day window. Filter for Closed Won renewals that have no approval submission date. Filter for renewals in the waiting-on-signatures stage whose renewal date is inside the 30-day window but whose documents are missing. Each of these filters is a small question with a clear answer, and together they show whether the windows are being followed.
Using the windows in forecast meetings
The forecast meeting is where the two windows earn their keep. Sort open renewals by renewal date, and the window status is visible at a glance. A renewal more than 30 days before its date, with documents in hand, should sit in the waiting-on-signatures stage and should not appear in committed revenue as won. A renewal inside the 30-day window can move to Closed Won once it is won. A renewal inside the 15-day grace period should show the approval status and how many days are left in the window. A renewal past the window with no win should already be Closed Lost.
This sorting changes the conversation. Instead of asking a rep whether a deal will close, you ask whether it is inside a window, whether the approval has been submitted, and what the stage says. Those questions have answers in the record. The rep's confidence is useful, but the record is what you report upward.
It also helps with rep behavior. When a rep learns that early paperwork does not move credit, the incentive to push a deal into Closed Won before its window goes away. If the commission plan follows the booking policy, as the GitLab page describes, the payoff for moving a stage early is smaller. Make sure your comp plan says this in plain words, because a rep who reads it in a handbook is more likely to believe it than one who hears it in a meeting.
Finally, watch for renewals that move between windows. A customer may ask to move a renewal date, or a contract may change after the documents are in. Those changes should update the renewal date field and the window dates, then the stage should follow the new dates. Do not leave the old dates in the record, because the reminder tasks and the export filters depend on them. For how to trace a moved close date, read Close date change log: why the date moved.
Setting your own windows
Your team should answer the same questions for itself. How many days before the renewal date can a deal be marked won? How many days after it can a late renewal still count? Which date sets the close date, the signature or the approval submission? What stage means waiting on signatures? Who owns the Closed Lost reminder, and who checks the monthly export? Write the answers in a short document, put them in the CRM field descriptions, and link the document from the renewal pipeline so every rep can find it.
The numbers in this post belong to one company's handbook. Use them as a model for the questions to answer, not as answers for your team. For a related look at the same GitLab rules, see GitLab order processing rules. If your business renews on different terms, or with a different billing schedule, the windows may need different lengths. The method stays the same: one stage for what is waiting, one date for when a win is allowed, one date for when a loss is required, and a reminder that makes the rule happen on time.
Renewals are predictable. A renewal's end date is usually known well ahead, and much of the work is done before the signature arrives. Two windows turn that predictability into clean stages and clean dates. The result is a forecast that tells you what is actually booked, a quota report that matches your comp plan, and a lost list you can trust.
Your next step today: write your two windows and your waiting-on-signatures stage name in one place, then add them to the field descriptions in your CRM.
Related guides: Open, won, and lost stage rules in 4 sales tools · Reopen a won or lost deal in 5 CRMs: what to re-check · Compare close dates: 3 rules for date and time fields.
Frequently asked questions
Can a renewal be marked Closed Won early?
Only within 30 days before the renewal date. Early paperwork does not change that limit.
Which date sets the close date for a renewal won within 15 days?
The approval submission date, under the GitLab policy this post follows, not the signature date.
What happens to a renewal that is not achieved within 15 days?
It must be marked Closed Lost, as the GitLab page states.