A renewal estimate can go stale when people join, leave, or change how they use email. A total copied from an old invoice or planning note may no longer match the number of mailboxes on the workspace—or the plan assigned to them. Keep a dated snapshot that records those facts separately, including storage per mailbox. Then, when renewal time approaches, you can compare a current account view with the terms available at that time instead of treating an old estimate as current.
The useful bits
- Date every snapshot and record where each fact came from.
- Count independent mailboxes, not aliases, and note the plan and storage per mailbox.
- Recheck the workspace and current pricing or checkout details before making a renewal decision.
Choose a consistent record
Use a spreadsheet or another record your team can maintain. Keep one dated summary for the workspace and, if plans differ among mailboxes, a separate row for each plan group or mailbox. Record the snapshot date, the person who checked it, and the source used for the count and plan details. This makes it easier to tell a fresh observation from a number carried forward from an earlier review.
Keep facts distinct: mailbox count, plan name, and storage allowance per mailbox are not interchangeable. A count alone cannot show which plan applies, and a storage figure alone cannot show how many mailboxes it covers.
Count mailboxes, not addresses
For the count, use the workspace’s mailbox administration information if your role, plan, and provisioning state provide access. Count independent mailboxes, and note the scope—for example, the workspace or domain included in the snapshot. A mailbox alias is not automatically a separate mailbox or login, so do not add every address or alias to the mailbox total. If the account view is unclear, mark the count as needing confirmation rather than guessing.
Avoid counting from an old contact list or a list of addresses someone remembers. Those lists may omit a mailbox or include aliases. Record any uncertainty and ask an authorised workspace or domain administrator to verify the relevant account information.
Capture the plan and allowance
For each plan group, write the plan name and its stated storage per mailbox. BITTU Mail business plans list 10 GB per mailbox for Starter, 20 GB for Standard, and 50 GB for Premium. Free personal @bittumail.tech mailboxes start with 500 MB. Note which account type and plan the figure describes; do not apply a business-plan allowance to a personal mailbox.
If your workspace has mailboxes on different plans, keep them in separate rows instead of averaging their allowances. A change in plan assignment or provisioning may make a prior snapshot outdated, so add a new dated record when you confirm a change rather than silently overwriting the old one.
Use a small, auditable table
A compact table is enough for a useful review. For grouped mailboxes, include a short label that identifies the group without exposing unnecessary personal information. If you calculate a combined stated capacity, show the count and per-mailbox allowance beside the calculation. Treat that total as the sum of stated allowances—not as measured usage or proof that all of that space is available or consumed.
For example, a record of 12 Standard mailboxes at 20 GB each gives a stated combined allowance of 240 GB. That arithmetic does not tell you how much storage is currently used. Keep actual usage separate, and include it only if you have a reliable account view for it.
Snapshot date: 2025-10-15 Scope: Example workspace Plan group: Standard Independent mailbox count: 12 Storage per mailbox: 20 GB Combined stated allowance: 240 GB Count source: workspace mailbox administration, checked by authorised admin Notes: Aliases excluded; plan assignment confirmed
Compare facts with renewal terms
When a renewal review begins, make a new snapshot rather than assuming the last one still applies. Compare it with the older record and investigate differences in count, plan, or storage allowance. Then check live pricing, upfront term total, taxes, availability, and renewal terms at /pricing or in authenticated checkout. These details can change, so a stored estimate should not be presented as a current quote. Articles and spreadsheets should not contain guessed or carried-forward numeric prices.
A mailbox count and plan record supports planning; it does not itself confirm a renewal amount or establish that a particular term is available. Keep the date of the pricing check with the renewal notes, and distinguish verified account facts from details that still need confirmation.
Confirm the snapshot is usable
Before relying on the record, have an authorised administrator confirm the mailbox count and plan assignment in the workspace, subject to role, plan, and provisioning state. Check that aliases have not been counted as independent mailboxes, that each plan group has its own storage-per-mailbox figure, and that the snapshot date is visible. If the account information does not match the record, correct it and note what was rechecked.
The record is working when another reviewer can tell what was counted, when it was checked, which plan and allowance apply, and which renewal details still need a live check. Keep prior snapshots for comparison, but label them clearly as historical so an old estimate is not mistaken for current facts.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction