A plan change can affect more than the person who clicks the button. A mailbox may have its own storage allocation, while a workspace may include several addresses managed by different people. Before updating anything, write down what is in place, what you intend to change, and what still needs confirmation. This worksheet helps you compare the two states, identify affected mailboxes, and keep unanswered questions visible. It does not determine eligibility or guarantee that a particular change is available; confirm those details through the account’s authorized settings or checkout before proceeding.
The useful bits
- Record each mailbox separately, including whether it is an independent mailbox or an alias.
- Compare current and intended plans alongside storage needs and affected addresses.
- Verify availability, total cost, taxes, and renewal terms before confirming a change.
Start with the account and decision
First identify the account or workspace you are reviewing and who is authorized to make the change. Do not put passwords, one-time codes, or other sign-in secrets in the worksheet. If you are not sure whether you have permission, ask the workspace administrator rather than assuming that access to an address also grants administration rights.
Write down the reason for the review in one sentence: for example, “We need to check whether the current mailbox storage fits the intended use.” A clear reason helps prevent unrelated changes from slipping into the same session.
- Account or workspace identifier: [non-secret label]
- Person coordinating the review: [name or role]
- Reason for review: [specific need]
- Decision owner and approver: [person or role]
Make one row for every affected address
List each address that could be affected, including addresses used by people, teams, or services. For each one, record whether it is an independent mailbox or an alias. An alias is not automatically a separate mailbox or login, so do not count it as one unless the account details confirm that it is an independent mailbox.
Include the person or process that depends on the address and whether it is actively used. This makes it easier to spot a mailbox that looks unimportant on a plan list but still receives messages someone needs.
Address: [team address]@example.com Type: [independent mailbox / alias / verify] Used by: [person or process] Current plan: [plan or not confirmed] Change intended: [yes / no / verify]
Record current and intended plans separately
For each independent mailbox, note the plan and storage allocation you can currently confirm. Then record the intended plan as a proposal, not as a completed change. If the plan is unknown, write “not confirmed” instead of guessing. This distinction gives you a useful baseline if you need to pause or compare account information later.
BITTU Mail’s public plan information lists Business Starter, Standard, and Premium storage as 10, 20, and 50 GB per mailbox. Free personal @bittumail.tech mailboxes start with 500 MB. These published figures can help you frame questions, but your account’s actual plan, eligibility, and available changes should be verified for the mailbox in question.
- Current plan and storage: [confirmed details]
- Intended plan and storage: [proposed details]
- Reason the intended allocation may fit: [expected use or requirement]
- Uncertainty to resolve: [specific question]
Check dependencies before you submit anything
Ask who relies on each affected address and whether a change could require coordination. Check with mailbox users and relevant administrators about shared workflows, service sign-ins, and any existing instructions that refer to the address. Do not assume that changing a plan changes an alias into a mailbox, or that an alias has an independent storage allocation.
If you are reviewing a business workspace, available controls can depend on your role, plan, and provisioning state. Administration and quotas are enforced server-side. If an expected option is unavailable or a detail is unclear, stop and have an authorized administrator verify it rather than trying to infer the account’s configuration.
Affected address: [orders]@example.com Dependency to check: [who receives or uses messages] Person confirming: [name or role] Status: [confirmed / waiting / not applicable]
Keep a verification list for cost and availability
Before approving a change, write down the questions that need an authoritative answer. Check current pricing and the full upfront term total, including applicable taxes, availability, and renewal terms. Do not rely on an old note or assume that a displayed plan is available to every account. Live details are provided at /pricing or in authenticated checkout.
A 30-day Starter trial is limited to one trial claim per eligible domain, and availability and eligibility are checked server-side. Treat the trial as a question to verify, not as an entitlement. A one-time checkout does not by itself imply an automatic charge or mandate; read the actual checkout terms for the transaction you are considering.
- Is this change available for this account and domain?
- What is the full upfront term total, including taxes?
- What renewal terms apply?
- Does the account meet any stated trial eligibility conditions?
Use the worksheet to confirm the result
When the worksheet is complete, compare the affected-address list with the proposed changes. Resolve any “verify” entries before continuing. Account actions, including sign-in and registration, go through mail.bittuicloud.com; use the authenticated account flow and review its current details before confirming. If you are not an authorized administrator, ask one to perform or verify workspace changes.
After an authorized change is made, check the account’s displayed plan and mailbox details against your recorded intention. Confirm each affected address individually, then update the worksheet with the confirmed outcome and date. If the displayed information does not match, or an address appears to have a different status than expected, pause further changes and ask the account administrator or support channel to clarify. A completed worksheet is a record of what you verified, not proof that every dependent service has been updated.
Address checked: [team address]@example.com Displayed plan after change: [confirmed plan] Storage shown: [confirmed allocation] Remaining issue: [none / describe] Verified by: [authorized person or role]
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