Skip to content
Interface language: English
Imperium / Signal

Unused subscription allowance: did the customer buy access, time or the right to submit work?

What happens to the unused part of a service subscription? Define carryover, expiry, acceptance of work and access to files after a plan change or pause.

Article language: English

A woman beside three circular pieces mounted on a supported axle.
In this article

“We have half of our subscription left. Can we use it next month?” That question can reveal two different products sold under the same name. The company believes it made a team available for an agreed period. The customer believes they bought a supply of work waiting for their request. Both remember the price. They understand the remainder differently.

Consider a subscription for proofreading a company's materials. Each month, a language team accepts texts up to an agreed limit. In the first period, the customer sends little. In the next, they plan a larger publication and want to combine the two allowances. This hypothetical example lets us follow an entitlement from the start of a period until it is used or expires.

The unit in which a service is sold (in Polish) determines whether the customer orders time, an outcome or access. Here we go further: even after choosing the unit, you need to establish when the customer can use it, what triggers the work and what happens to the unused part. That is a decision about how the offer works. Legal assessment of the terms belongs to someone familiar with the relevant contract and relationship with the customer.

Start with a month without a single request

Ask the team a simple question: what did we deliver if the customer never contacted us? One answer might be that we maintained the agreed readiness to accept their materials. Another might be that we granted a defined allowance for them to use. Sometimes the company actually performed ongoing work even though the customer sent no new request. Each case needs different evidence of delivery and a different explanation of what was left unused.

If the product is the team's availability, do not imply that every page the customer did not send sits in storage. If the customer bought an allowance, do not silently count the remainder as work already done. In our subscription, the company must choose what underlies its monthly promise. A text limit can be a condition for accepting work, rather than a stock of completed proofreading.

Zero activity does not explain why the allowance went unused. The materials may never have been created, the person ordering may not have known how to send them, or the proofreading team may have been unable to accept the request. The last case concerns the provider's ability to deliver on its promise. It should not be confused with a customer voluntarily postponing publication.

In a study published in 2006, DellaVigna and Malmendier analysed contract choices and visits by 7,752 members of three US health clubs. The authors identify overestimated expectations of future attendance as one of the leading explanations for the behaviour they observed. The original research abstract concerns consumers in that particular market; it does not establish how buyers of B2B proofreading behave.

When discussing your own subscription, examine the plan and the conditions needed to carry it out separately. “We will send texts regularly” sounds credible until someone asks who approves them before proofreading. If internal approval holds up publication, a larger allowance will not remove that obstacle. It may only leave more unused capacity for the next conversation.

There is no need to persuade a customer to consume a service for the sake of using it. Ask for an example of the next piece of material and when it will be ready to send. If the customer cannot identify one, discuss whether they need ongoing availability, a single assignment or a different collaboration period. This is a conversation about matching the service to the need, without inventing a need to use it.

Carrying the remainder over changes the next period

In the example, the team accepts up to 20 pages per period. The customer sends 8, leaving a difference of 12. If the company adds the entire remainder to the next allowance, the customer can submit 32 pages in the following period. Those 12 pages are not an accounting error. They are an additional entitlement the company has decided to accommodate later.

First decide what the carryover covers. It might apply only to the immediately following period, have a fixed upper limit or depend on the subscription remaining active. The company might also offer no carryover. The terms should match how work is actually accepted. The word “carries over” alone does not say how long the remainder is available or whether it accumulates with every later payment.

If the 12 carried-over pages are due to expire after one period and the customer commissions 15 pages during that period, before the carried-over pages expire, the order in which allowances are used must be clear. Do the older 12 come off first, followed by 3 from the current allowance? Or does the company use the current allowance first and leave the previous one to expire? This apparently small decision changes the result the customer sees at the end. Do not leave it to the person updating a spreadsheet by hand.

In the first case, accepting 15 pages leaves 17 from the current allowance. In the second, 5 current pages and 12 older pages remain, with the latter about to expire. The number visible before the period ends may be the same, but the customer's later ability to commission work will differ. A “17 remaining” message should therefore also show where each portion came from and when it expires.

In documentation updated on 6 October 2026, Teamwork.com describes a periodically renewed budget with separate options for adding unused hours and subtracting overruns from the next period. Its retainer budget guide shows that carryover is a configurable rule. It does not follow simply from recurring billing.

TrackingTime, by contrast, says unused hours do not automatically transfer to the next period. If an agreement provides for carryover, they must be accounted for manually when configuring the next period. That is what the tool's own guide, dated 3 September 2026, says. The team should therefore check that the application behaves as promised to the customer.

Accepted work should not disappear with the counter

A customer may send a text on the last day of a period, while proofreading finishes later. Decide which event determines when the allowance is used. It might be acceptance of complete material for the agreed work, or another clearly defined stage. What matters is being able to identify that event for a particular request, rather than fitting the result to a report date.

Aeneia conceptual photography

If sending an incomplete file alone reserves an allowance, the customer may expect the work to be done after supplying the missing content several weeks later. If only the finished result counts, a delay on the proofreaders' side can change the period in which the allowance is used. The team should examine both cases before publishing the short claim “20 pages per month”.

For an accepted proofreading request called K-18, you can record the period it draws on, the agreed scope and its progress. Closing the period should not delete that information. The customer can then distinguish text already accepted for work from unused pages still available to submit. The proofreader does not have to guess whether the start of a new month means earlier commitments have been abandoned.

For requests accepted for a shared release (in Polish), there is a separate calendar boundary: which release the text reached in time. A subscription period and a release can overlap. Material may use an earlier allowance but enter a later batch. The confirmation should state both, rather than replacing them with a single label such as “this month”.

K-18 might also be withdrawn before the proofreader starts. The company then needs a rule for releasing the part of the allowance assigned to it: does it return to the same pool with the same expiry date? If the customer withdraws the text after the period has ended, subtraction alone will not determine how long they have to order a replacement. Decide this case alongside the acceptance rule, rather than waiting for the first complaint.

A different situation arises when the customer replaces the text in a request already accepted. The new file may contain a different number of pages, and some proofreading may already have been done. The team should be able to say what was previously accepted and what new work the change created. Keeping the same K-18 number does not make every later version part of the original scope.

When proofreading a revised file that replaces an earlier one, keep it linked to the previous material. The customer should see what they have used and what they can still submit, without manually comparing old messages. The request number helps locate the history. It should not work like a bag into which new texts can be added indefinitely just because the label still has the same number.

Using an allowance does not by itself set the pace of all the work. Carried-over pages may give the customer a greater ability to place orders, but they do not necessarily mean everything will be completed at once on the same day. If there is an agreed order or schedule for delivery, show it alongside the allowance. Otherwise, carryover may be understood as reserving the team's immediate availability.

Account access can continue without the service being performed

In a guide dated 17 June 2026, Design Pickle separates its creative-services subscription from its platform-only plan. With the latter, customers can retain access to files and create draft requests, but cannot submit new requests for execution. Its Platform-Only plan description thus distinguishes access to resources from an active service.

In our proofreading subscription, the customer may still need old files and the history of agreements after a break. That is separate from whether the team accepts new texts. If the company offers a pause in the relationship, it should establish what remains accessible during it and what happens to the unused allowance. The single word “pause” answers neither question.

Ending a subscription also requires identifying work already accepted. Does a question awaiting the author's answer still concern proofreading covered by the previous period? Who completes that material, and how will the customer receive it? The answers must follow the approved terms of the engagement. A person designing the screen should not invent them while arranging a cancellation message.

It is useful to separate the business decision from the design of a plan change and pause in the service (in Polish). The former defines what the company actually maintains. The latter lets the customer recognise the consequences before confirming the change. A clear button helps only when the team knows what state it should produce.

If you need to present already approved rules in your service, Aeneia Design helps arrange the offer and the customer's path between options. The work starts with concrete cases: no requests, part of an allowance used, text accepted before the period ends and a pause. They make it possible to test whether a short description reflects the actual promise.

Answer the customer's question instead of showing a single balance

A B2B service price list on a website (in Polish) may include a limit, but a large highlighted number does not explain when it expires. A customer with 12 carried-over pages needs to know how many they can still submit, until when and in what order the allowances will be used. An internal abbreviation for the plan cannot replace that information.

Besides the balance, show the allowance assigned to work already accepted. If K-18 is awaiting the author's answer, the customer should know that this portion is not a free allowance for ordering something else. At the same time, a pending request should not be presented as completed proofreading. Different states can be brief and clear as long as they correspond to actual events.

Before renewing the engagement, compare the expected way of using the service with what actually happened. The customer may need less ongoing availability and a separate order for a larger publication. They may instead need help sending completed materials. The assumptions behind the service price (in Polish) will then rest on a defined way of working, rather than on hope that this time the counter will be used up.

In that conversation, do not treat every remaining page as proof of dissatisfaction or every fully used allowance as success. Ask about a specific request the customer wanted to make but did not send. Perhaps the content was not ready. Perhaps they did not understand the expiry date. The same change to the offer will not fix both causes.

As a test, give someone new the subscription description and this history: 20 pages per period, 8 accepted, and the remainder carried over for one following period. Ask them what happens after a further request for 15 pages and after a pause. If they have to add a rule of their own, you have found a decision that needs making. Make it before the customer starts calculating for themselves what they can still use.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear