Set a Naming Rule for Temporary and Seasonal Employee Accounts

Separate the address rule from employment classification

Start by deciding what coworkers need to recognize: that the person is part of a temporary or seasonal staffing cycle, and which team or location they support. Do not encode a legal or employment classification in the email address. A short-term employee is still an employee; temporary duration alone does not make someone a contractor.

Use the organization’s existing HR or staffing process to determine the person’s status. The mailbox naming rule should identify an account for administration, not settle that question. Avoid labels such as “vendor” or “contractor” unless the person’s actual relationship has been determined through the appropriate process.

Choose a pattern people can apply consistently

A useful pattern is predictable, readable, and based on information the organization already manages. For example, a business might use a person’s normal name-based address and record the seasonal group or expected end date in its authorized account inventory, rather than adding a status label to the address. If the organization needs a visible marker in addresses, agree on one neutral marker and use it consistently.

Avoid putting a birth date, personal phone number, or other unnecessary personal detail into an address. Decide how to handle duplicate names, spelling variations, and employees returning for another season before accounts are created. Document who approves exceptions so that different administrators do not invent different conventions.

Possible address pattern: [givenname].[surname].[season]@example.com
Inventory entry: [employee name] | [team] | [manager] | [expected review date] | [account owner]

Record the details the address cannot carry

An address cannot tell an administrator who approved access, which manager is responsible for the work, or whether the person’s engagement has actually ended. Keep those details in an access-controlled inventory or the organization’s established identity-management record. Include an account owner, responsible manager, start date, expected review date, and the system or team responsible for follow-up.

Treat the expected end date as a reminder to review, not as proof that employment has ended. Dates can change, and an employee may return. Assign a person or role to reconcile changes with the appropriate HR or staffing record before account access is changed.

Create the account with its end review in mind

Before provisioning, check that the proposed address follows the rule, the correct manager is recorded, and the review date has an owner. Give the employee the access needed for the assigned work, following the organization’s normal approval and security procedures. Do not create a shared or secondary mailbox merely because an address needs a seasonal label; an alias is not automatically an independent mailbox or login.

For a BITTU Mail workspace, domain and mailbox administration is available to authorized workspace administrators, with controls depending on role, plan, and provisioning state. Confirm that the required administrative control is available to your role before relying on it. Server-side permissions and quotas still apply.

Run a deliberate end-of-engagement review

When the expected date arrives, confirm the person’s status with the responsible manager and the organization’s established process. If the engagement has ended, review account access and ownership rather than simply deleting the address. Consider whether messages or work need to be handed over, whether the account has approved ongoing business use, and who is authorized to make the change.

If the engagement continues or the employee returns, update the record and set a new review date. If it has ended, follow internal retention, access-removal, and account-closure procedures. Do not recycle an old address for another person without checking the organization’s identity and records rules; confusing two people’s messages can create operational and privacy problems.

• Confirm the engagement status with the responsible source.
• Identify the manager and any approved work handoff.
• Review access and account ownership under internal procedures.
• Record the decision, responsible person, and next review date if applicable.

Check that the rule works in practice

A rule is useful only if administrators can apply it and colleagues can understand it. Have the account requester verify that the address matches the documented pattern and that the directory or internal record identifies the right person and manager. Check that the expected review date has an assigned owner, not just a calendar entry with nobody responsible.

After an end-of-engagement review, confirm the recorded decision and account status through the authorized administrative process available to your role. If the account remains active, the record should explain who approved that status and when it will be reviewed again. If ownership or status is unclear, pause the change and resolve the discrepancy through the organization’s normal process.