A mailbox plan decision can become hard to explain later: someone may remember the reason for changing, but not which account details were checked or what still needed confirmation. A short decision log keeps those pieces together without turning a simple choice into a report. Record the decision and its reason, distinguish confirmed facts from assumptions, and leave unresolved questions visible for review. This is especially useful when comparing mailbox storage, checking current terms, or handing a decision to another account owner or workspace administrator.
The useful bits
- Write down the decision, its reason, and the account or mailbox it applies to.
- Record confirmed details with the date and place they were checked.
- Keep unanswered questions open until someone verifies them.
Start with a small, repeatable record
Use one entry for each decision, rather than keeping a running note that mixes several mailboxes or plan changes. Give the entry a short subject, such as “Review storage for team mailbox,” and identify the account or mailbox it concerns. If the decision affects several mailboxes, list them or describe the scope clearly.
A useful compact format has five parts: decision, reason, confirmed account details, check date, and unresolved questions. Add an owner or next review date only when someone has agreed to take that responsibility. A blank field is better than filling a gap with a guess.
Decision: [keep current plan / change plan / defer] Applies to: [mailbox or workspace] Reason: [need or constraint] Confirmed details: [fact — where checked] Checked on: [date] Open questions: [question — who will verify, if known]
Separate the reason from the decision
State what you chose, then explain why in a separate sentence. For example, “Defer a plan change” is the decision; “the expected storage need is not yet confirmed” is the reason. This distinction helps a later reviewer see whether the original need still applies.
Keep the reason specific and operational: an expected increase in mailbox use, a need to compare available plans, or a request to confirm renewal terms. Avoid writing only “best option” or “more space.” If the decision is provisional, label it as provisional and say what information could change it.
Record facts with their source
Use the confirmed-details field for facts that were actually checked, not estimates or recollections. For BITTU Mail, free personal @bittumail.tech mailboxes start with 500 MB. Business Starter, Standard, and Premium provide 10, 20, and 50 GB per mailbox respectively. Note which mailbox type and plan apply before using those figures in a decision.
Live prices, the upfront term total, taxes, availability, and renewal terms can change or depend on the offer. Check current information at /pricing or in authenticated checkout, and record the date and what was confirmed rather than copying a price into a long-lived log. If considering a Starter trial, note that it is limited to one trial claim per eligible domain; eligibility and availability are checked by the server.
Use a brief source label such as “/pricing checked” or “account details reviewed by authorized admin.” Do not record passwords, one-time codes, or unnecessary personal information. Account sign-in and account actions go through mail.bittuicloud.com.
Make the check date meaningful
Write the date beside the details it qualifies. A date on the top of a document may not make clear whether the plan terms, mailbox assignment, or storage figures were checked that day. If different facts were verified at different times, give each its own date.
A decision log is a snapshot, not a guarantee that terms remain unchanged. Before acting on an old entry, revisit the details that could have changed, especially pricing, availability, renewal terms, and the mailbox’s current plan. Update the entry with the new check date and preserve the earlier decision if it explains why the plan was chosen.
Leave open questions visible
Write unresolved items as questions that can be answered, not vague warnings. “Does the current checkout show the expected renewal terms?” is more useful than “check terms.” If no one is assigned, say “owner not assigned” rather than implying that follow-up is underway.
For a workspace, role, plan, and provisioning state can affect which controls are available; do not assume that every administrator or mailbox has the same options. An authorized workspace or domain administrator should confirm details for their own domain where needed. Admin permissions and quotas are enforced server-side, so a note about intended access is not proof that a change has taken effect.
Example: a decision that is not ready yet
Suppose a team is considering a different mailbox plan because it expects to need more storage. Rather than selecting a plan from an old note, record the current need, the details checked, and what remains unknown. This makes it clear whether the next step is gathering usage information or reviewing current terms.
Decision: Defer plan change; review after storage need is confirmed Applies to: [team mailbox], [workspace] Reason: The team expects a change in storage needs, but has not confirmed the amount. Confirmed details: Business plan storage options are 10/20/50 GB per mailbox; current mailbox plan: [confirmed value or not yet confirmed]. Checked on: [date] Open questions: What storage capacity does this mailbox currently use? Which plan and renewal terms are available at checkout? [Owner, if assigned] Next review: [date or trigger]
Close the loop after review
When the open questions are answered, update the same entry with the verified facts, their check date, and the resulting decision. If the plan is changed, confirm the account’s resulting plan through the appropriate authenticated account or workspace view, where available to your role. If you cannot confirm the change, leave it marked unverified and ask an authorized account or workspace administrator to check.
The log has worked when another responsible person can tell what was decided, why, which details were confirmed and when, and what still needs attention. Keep it brief enough to maintain, and revise it when facts—not merely opinions—change.
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