Project teams change while a project is running. People leave the firm, join halfway through, move to another job or go on long leave, and each change can take project emails with it. The approvals, instructions and queries that explain why a project looks the way it does often sit in the inbox of whoever dealt with them.

Team email management is how a project team keeps its emails in one shared record, so the work carries on whoever is in the team. It matters most in architecture, engineering and construction (AEC) firms, where projects run for months or years. Several people work from the same emails.

A shared record fixes this. Email management software that works inside Outlook adds emails to the record as people work, so the team can still find them after someone leaves.

What happens to your project emails when the team changes

Email sits in personal mailboxes by default, so project knowledge sits there too. When someone leaves or moves on, the team can lose track of:

  • The reason behind a decision: the email chain where a client approved a change or a consultant confirmed a detail
  • The latest position on open queries: such as requests for information (RFIs) still waiting on a response
  • Who was told what, and when: which matters if there is a dispute later
  • The context a new colleague needs: to pick up the work without asking around

Some of this can be recovered from a leaver's mailbox, depending on your IT policy, but that takes time from IT and from colleagues who already have project work to do. It is far simpler when the emails are already in the project record. This is the filing gap showing up at the worst moment: the space between an email arriving and that email being saved where everyone can find it.

How team email management makes every handover routine

Each change in the team needs a short step that people repeat every time. Agree these once and the project record stays complete however often the team changes.

Make sure a leaver's project emails stay with the project

Before their last day, check that their project emails are in the shared record. Ask them to flag any open queries or pending approvals and to name the colleague who takes over each one. If the record builds as people work, this is a quick check and not a mailbox clear-out.

Give a new starter the full project history from their first day

A new starter on a live project needs the history, and the quickest route is the shared record. Point them to the project's location and show them how to search it. Colleagues no longer need to forward old threads one at a time, and the new person sees the same history as everyone else.

Move colleagues between projects without losing their earlier emails

Their earlier emails stay in the first project's record, and they start filing to the new project from day one. Anyone who picks up the first project can find what that colleague handled. It is also a good moment to check they have access to the new project's location.

Start each new project phase with the full email history

Handing a project from bid or design to delivery, or from delivery to close-out, often changes who is involved. A shared record lets the next team start from the full email history, including the client brief and agreed scope. They no longer rely on what the previous team remembers to pass on.

Let colleagues cover an absence without waiting for anyone to return

Annual leave or a long absence can stall a project when one person holds the only copy of a key email. With a shared record, the colleague covering the role can search for the client's latest instruction without waiting for the person to return.

Questions that show whether your project emails depend on one person

Think about the last time someone left your team or moved projects. Your answers to these questions show how much of your project record sits in one person's mailbox:

  • If your project manager were away from tomorrow, how long would it take someone else to find what the client last approved?
  • Could a new starter learn the history of a live project without asking colleagues to forward emails?
  • When your last colleague left, did their project emails stay with the project or go with them?
  • Do you know which important project emails exist only in one person's mailbox right now?
  • Who is responsible for checking this when someone leaves?

The leaver question is simple: if this person left today, where would their project emails be? If the answer is their own mailbox, those emails are at risk the day they go.

How to set up a shared project record your whole team uses

Handovers become routine when the project record is already complete, so there is little to chase when someone moves on. Four things make that happen:

  • Someone accountable for the record: the project manager for each project. A coordinator can run it day to day where you have one. IT looks after the set-up, such as Outlook versions and access to project locations
  • A clear view of what counts as the project record: client instructions, approvals, scope changes and requests for information
  • One structure everyone files to: the same project locations and naming, so any colleague can find an email without asking who filed it
  • A way of filing that does not rely on memory: suggestions as emails arrive. Filing by hand slips when deadlines tighten, so it helps when it fits how people already work in Outlook

A short monthly check keeps it honest. Look for a few recent decisions in the record and see whether they are there.

How Ideagen Mail Manager gives everyone the same project email history

Ideagen Mail Manager is email management software built for project teams. It works inside Outlook and files emails and attachments to your connected locations. The record builds as people work, so every colleague sees the same history, including emails from people who have moved on.

  • Prompt & Predict: learns how your team files and suggests where each email should go, so everyone files to the same structure
  • Filing from Outlook: files an email and its attachments from inside Outlook, with the location suggested
  • Advanced Search: finds filed emails across your connected locations, including emails from people who have left, so new starters can learn the history themselves
  • Migration tools: bring in historical project emails from earlier systems or messy folders, so a project already under way has its history in one place
  • Classic Outlook and New Outlook support: suggestions and search work in both
  • Integrations: SharePoint, OneDrive, ProjectWise, network drives, Microsoft Teams, Procore and Viewpoint

To see how it handles a real handover, start a free trial of Ideagen Mail Manager. Your team files real project emails from their own Outlook and anyone can search the record. You can then check that a project would carry on smoothly if a colleague moved on. You can start in under a day. See the full list of features.

Frequently asked questions about team email management

Who should be responsible for the project email record?

The project manager is accountable for the record on each project. A coordinator can run it day to day, IT looks after the set-up and directors or department heads set the standard across projects. Being responsible does not mean filing every email by hand.

What happens to a leaver's emails when they leave a project team?

That depends on your firm's IT policy. A leaver's mailbox may be kept, passed to a manager or removed after a set time. Whatever the policy, project emails are easier to find and safer when they are already in the shared project record.

Do we have to stop using Outlook to manage email as a team?

No. Good email filing software works inside Outlook. Your team keeps its inboxes and its way of working, and the software adds a shared project record on top.

How does a shared mailbox differ from a shared project record?

A shared mailbox is one address that several people can read and send from, and it only holds mail sent to or from that address. Team email management covers the emails in everyone's own mailboxes, which is where most project emails sit.

What to ask vendors before you choose email filing software

How your team files email is worth choosing carefully, because the record needs to last longer than any one project team. The buying guide, How to choose email filing software for project-based firms, gives you the questions to ask. Inside you will find:

  • Eight things that separate the right tool from the wrong one, so you judge vendors on what matters beyond the feature list
  • Five red flags to watch for in any vendor evaluation, so you spot a weak fit before you sign
  • A 30-point vendor evaluation checklist across six categories, ready to take into your next vendor call
  • An honest assessment of who Ideagen Mail Manager is for, and who it is not, so you can rule it in or out quickly

The guide gives you one checklist to hold every vendor on your shortlist against. Download the buying guide and compare them on equal terms.

Keep your project emails complete however often your team changes

Team changes are a normal part of project work. With a shared project record, a handover becomes a short routine and the emails stay with the project. Put someone in charge of the record, agree what goes in it and make filing part of how people already use Outlook.

Want to try it on a real handover? Request a free trial of Ideagen Mail Manager, file real project emails from your own Outlook and search them as a team. Still choosing? Download the buying guide for the 30-point checklist, the five red flags and the questions to ask before you shortlist.

Ready to see how Ideagen Mail Manager can help?

Get a free, personalised demo at a time that works for you.

See how it handles a real handover

Start a free trial, file a live project’s emails from Outlook and see whether a new team member can pick up the record without asking anyone.

How to choose email filing software for project-based firms

Get eight criteria for judging email filing software, five red flags to watch for and a vendor assessment checklist to use in every demo.