Shared family inbox vs forwarding

The difference, in one sentence

Forwarding is about delivery. A shared inbox is about state.

Forwarding moves a copy of a message from one mailbox to another. That is the whole mechanism, and it works — the school's email about Thursday's excursion lands in your inbox and your partner's, and neither of you is dependent on the other to relay it.

A shared inbox does that too, and then keeps one extra thing per message: a small amount of information about what has happened to it. Whose job is this. Has anyone answered it. Is it done, or is it waiting on the school to write back. That information is what makes "did you reply to the swimming thing?" a question you can answer by looking rather than by asking.

Everything below is an elaboration of that one difference. If you take nothing else: a forwarded setup can tell you that a message arrived. It structurally cannot tell you that it was dealt with, because there is nowhere for that fact to live.

What forwarding actually does, and does well

This page is not an argument that forwarding is bad. Most households that have solved anything at all have solved it with forwarding, and the thing it solves is the biggest single problem: household mail addressed to one person, and therefore known to one person.

The Third Shift's write-up of the family-email setup puts the win plainly:

“Now you both see everything. What you do with it is up to you — but at least the information isn't trapped in one person's inbox anymore. No more "I didn't see that email" or "I didn't know they changed the pickup time."”

Read that carefully, because it is exactly right and exactly bounded. "What you do with it is up to you." Forwarding delivers the information and hands the coordination problem back to you, unsolved and unaided. Everything this page is about lives in that sentence.

It is also worth knowing what forwarding costs to run, because people underestimate it. In Gmail, the basic setting forwards to one destination; Google's own instructions say that "to forward messages to multiple accounts, create a filter for every forwarding email address" (Gmail Help, checked 14 September 2026). So a two-parent household is one setting plus one filter; add a grandparent who does Tuesday pickups and it is one setting plus two. Each destination address has to be verified by clicking a link Google emails to it, and each rule is invisible from the receiving end — if one breaks, the symptom is silence.

None of that is fatal. It is just worth counting honestly before deciding forwarding is the free option and everything else is the expensive one. The family email address guide has the full set-up, including the send-as step that stops your reply putting your personal address on the thread.

Why email can't hold "who's got this"

This is a limitation of the format, not of your setup, and it is worth understanding because it tells you which problems are fixable by trying harder and which are not.

Email's own specification gives a message a short list of flags. In RFC 9051, the current standard for how mail apps read a mailbox, section 2.3.2 defines them in a few words each:

• \Seen — "Message has been read"
• \Answered — "Message has been answered"
• \Flagged — "Message is “flagged” for urgent/special attention"
• \Deleted, \Draft — housekeeping

Two things follow. First: there is an "answered" bit in email. Your mail app sets it when you hit reply, which is why replied-to messages show a little arrow. Second, and this is the whole problem: those flags belong to a message as it sits in one mailbox. They are not a property of the conversation, or of the household. They are a property of your copy.

A forward creates a second, unrelated message in a second mailbox. When you answer the excursion email, your copy gets \Answered and \Seen. Your partner's copy gets neither, and there is no mechanism by which it ever could — the two copies have never heard of each other. Their inbox goes on showing a bold, unread, unanswered message about an excursion that has already been dealt with.

So the household falls back on the only channel it has left, which is asking. "Did you reply to the swimming thing?" three times a week. And the two failure modes people describe — both of you replying to the same email, and neither of you replying because each assumed the other had — are not two problems. They are the same missing bit of information, seen from two sides.

The test. Pick any household email from last week. Is there anywhere — anywhere at all — that a third party could look and learn that it was handled, by whom, and when? If the answer is "in one of our heads", that is the gap. Everything below is about closing it, and the first option costs nothing.

The four things a shared inbox adds

"Shared inbox" is a category name from business software, and underneath the marketing it is a very small idea: one mailbox, plus four things kept about each message that ordinary email does not keep. Email triage for households is the same four moves as email triage for a support desk, with the jargon taken off.

1. Assignment — this one is yours

A message can be given an owner: taken by someone, or assigned to someone else. That is the field forwarding has no room for. It converts "someone should ring the dentist back" into "you are ringing the dentist back", which is the entire difference between a household where admin is shared and one where it is theoretically shared.

The version that matters most at home is assignment by sender rather than message by message. Nobody wants to triage forty messages a term into two piles by hand. But "the school is mine, the sports club is yours, the health stuff is mine" is a decision you make once, and it is a real way to split school admin between parents without a weekly negotiation.

2. Status — this one is finished, this one isn't

Read/unread means "I have looked at this". It does not mean "this is dealt with", and using it as though it does is why family inboxes become guilt piles. A shared inbox replaces it with a status you set deliberately: in progress, waiting on a reply from them, resolved, snoozed until the day it matters.

The important word is deliberately. Read/unread happens to you as a side effect of opening something on the train. A status is a decision, and a decision made once is a decision the other person can rely on.

3. Visible history — who did what, with a name on it

Every action leaves a line: who marked it in progress, who replied, who forwarded it to the grandparents, when. It is unglamorous and it is the single most useful part. "Who replied to the school email" stops being a conversation and becomes a thing you read off the message.

It also does something quieter that matters in households where one person carries most of the admin: it makes the work visible. An archive that records forty handled messages, thirty of them handled by the same person, is a fact rather than an argument.

4. Collision avoidance — nobody replies twice

Business shared inboxes take this seriously enough to have a name for it. Front's help centre describes what their version does:

“If a teammate is working on a message in a shared inbox, you will see indicators that they are replying.”

At a support desk that prevents two agents sending a customer two different answers. At home it prevents the pettier but more corrosive version: both of you writing to the class teacher about the same absence, twenty minutes apart, saying slightly different things.

Worth being precise about what is on offer here, because it comes in two strengths. The live-typing indicator is the strong version, and it needs both people looking at the same screen at the same moment. The weak version — the message already carries a status and a name, so you can see before you start that someone has this — costs nothing to run, works asynchronously, and catches nearly all of the household cases. Most households need the weak version. It is fine to want only that.

Why every article about this is written for support teams

Search for a shared inbox for families and what comes back is business software: Front, Missive, Hiver, Zoho, Help Scout. The mechanics are exactly the ones a household needs. The language is from another planet, and the pricing is per seat per month because it assumes you have seats.

It translates cleanly, though. If you do read the B2B material — and it is the best-written material on this subject, because those companies have thought about it for a decade — here is the dictionary:

The differences that actually matter between a support desk and a household are worth naming, because they change what a good tool looks like. A household has two or three people, not thirty — so round-robin distribution is pointless and a standing per-sender rule is everything. Volume is tens of messages a term, not hundreds a day — so anything that demands per-message triage will be abandoned by week three. And there is no manager: nobody is going to audit an unhandled queue, so the queue has to be short enough that its own length is the alarm.

Three ways to get ownership without buying anything

Before any product: here is how far you can get for free, done properly. All three are real answers, and the first one is the one we would push hardest.

1. The house rule — handle it or tag it

No tooling, ten seconds to explain, and it captures most of the value on this page: if you open a message in the family account, you do not get to put it back. You either deal with it now, or you put the other person's name on it. A star, a label with their name, a two-word reply in the thread. The mechanism does not matter. What matters is that nothing you touch leaves without an owner.

In a shared Gmail this is genuinely workable. Make a label per adult, and make a habit of applying one before you close anything. The inbox becomes a to-do list rather than a filing cabinet. There is more on the habit itself in the family email address guide.

The catch is that nothing enforces it. There is no field in Gmail for "this is Alex's", nothing stops a message being read by both of you and owned by neither, and the whole scheme depends on two people remembering a rule while standing in a school car park. It decays quietly. If you are going to try exactly one thing from this page, try this — and notice whether it survives a term.

2. A Google Group as a Collaborative Inbox

This is the free option people do not know exists, and it is a proper shared inbox with real assignment and real resolution states. A Google Group already gives you an address that fans out to everyone's normal inbox; turning on Collaborative Inbox adds the state on top.

A group owner or manager turns it on from Group settings → Enable additional Google Groups features → Collaborative Inbox, and conversation history has to be on first (Google Groups Help, Workspace Learning Center). Once it is on, members with the right permission can:

• Take a conversation they are volunteering to answer, or assign it to another member by entering their email address.
• Mark it complete, no action needed, or a duplicate of another conversation.
• Filter the list by "Assigned to me", "Assigned to anyone", "Not assigned", or by whether it is still unresolved.
• Unassign — which removes any assignment regardless of who made it (Google Groups Help).

That is the shared-inbox feature set, free, from a company you are probably already using. If this page talks you into a Google Group and nothing else, it has done its job.

The honest catches, and there are four. The state lives in the Groups web interface, not in your mail app — so you get the assignment and the resolution only when someone goes and looks, and "went and looked" is precisely the habit households are bad at. Taking, assigning and marking complete need the Who can moderate metadata permission, which an owner has to grant. Who can post must be opened up before a school's bulk-mail system can deliver to the group at all. And a group is a mailing list underneath, so each member's own copy still has its own independent read state — the ownership is shared, the reading is not.

Settings paths checked against Google's own documentation on 14 September 2026. Products move.

3. A real shared mailbox — if you already pay for one

Microsoft 365 has shared mailboxes, and they are the closest mainstream thing to "one inbox two people are actually both in". Members send as the shared address, so replies do not carry a personal address onto the thread, and there is one archive rather than two forwarded copies.

It is also, unambiguously, business software. Microsoft's own documentation says you need "a Microsoft 365 for business plan that includes email", that "only people inside your organization can use a shared mailbox", and that you cannot give access to "people outside your business, such as people with a Gmail account" (Microsoft Learn, checked 14 September 2026). So it is an option if your household already has a business tenancy lying around — a family business, a sole trader, a shared domain — and it is not an option otherwise.

The same shape applies to the B2B shared-inbox products. They work. They are priced per user per month against a business's budget, and their onboarding, vocabulary and defaults all assume a support queue. A two-person household can absolutely run one. Most will find they have bought a lot of machinery to solve one question about a permission slip.

There is also the option the family email guide covers in detail: Gmail's mailbox delegation, where both of you are in the one mailbox and read state is genuinely shared. It gets you the single archive. It still gives you no field for "this is yours".

When forwarding is genuinely enough

We sell a shared inbox, so treat the following with the appropriate suspicion — and then read it anyway, because a household that switches tools it did not need has made its admin worse, not better. Stay on forwarding if most of these are true.

• One adult. Ownership is not in question. What you want is household mail out of your work inbox, and that is a forwarding-and-filters job, not a shared-inbox job.
• You have already agreed who does what, and it holds. If "school is mine, sport is yours" has survived two terms without renegotiation, a tool that records that agreement is recording something you already both know.
• Low volume. One school, one activity, a few messages a week. At that size the queue you would be managing fits in your head, and managing it in a tool is more work than the work.
• You use Gmail delegation, not forwarding. Both of you in one mailbox means one archive and shared read state — you have already solved the duplicate-reply problem, if not the ownership one.
• Nothing has actually gone wrong. No missed form, no duplicate reply, no "I thought you did that" this year. Do not fix that.
• Mid-term, and it is working. Changing where household mail lands in week six of a term is a bad trade against a problem that is annoying rather than urgent. January and August are the natural moments.

And two things a shared inbox will not fix, so do not buy one expecting them. It will not make an unwilling partner engage with school admin — a queue with their name on it that they never open is the same problem with better instrumentation. And it will not reduce the volume of mail: fourteen emails a week from one school is fourteen emails a week however they are organised.

The signs it has stopped being enough

The other direction. None of these is dramatic, which is the problem — they are all things a household absorbs rather than notices.

• "Did you reply to…" is a recurring conversation. Once a week is a signal; three times a week is the whole argument on this page. Every one of those is a query against a database that does not exist, run by interrupting a person.
• You have both answered the same email. Or worse, sent conflicting answers. Once is funny. Twice means the mechanism is missing, not that someone was careless.
• Something was missed that both of you received. The classic failure: two copies delivered, two people each assuming the other one had it. The delivery worked perfectly. The delivery was never the problem.
• One of you is the household's project manager by default. If one person is the only one who could answer "what is the school asking for this week?", the mail is shared and the load is not.
• New senders keep arriving and the rules don't keep up. Every new club, specialist and bulk-mail provider is another filter to write in a mailbox someone opens twice a year. The decay is silent; the symptom is a form that gets missed.
• You cannot answer "what is outstanding?" without reading. If the only way to know what is left is for one of you to re-read the inbox, the inbox is not a queue and nothing is ever finished.

If several of those are true, the fix is not more discipline. It is somewhere for the state to live. That can be a Google Group, and it costs nothing — see above. Or it can be what we built.

How we do it, and what we don't do yet

household.email is a shared inbox for families. Your household gets its own address — thesmiths@household.email — and you hand it to the school the way you would have handed out a shared Gmail address. The difference from the forwarded setup is everything in this section.

• Every message has a status, not a read flag. Unhandled, in progress, waiting on their reply, resolved, archived, snoozed until a date and time, or spam. Setting one is a deliberate act, and it moves the message out of the queue.
• It is a queue, and it empties. Marking a message handled takes you to the next unhandled one rather than back to a list. Each of you carries a count of what is still yours to deal with, and getting it to zero is a thing that can happen.
• Snoozing is built in. A message about a form due in three weeks can leave the queue now and come back on the day, instead of sitting in it looking urgent for twenty days.
• Ownership is per sender. Assign the school to one adult, and from then on the school's mail lands in that adult's queue. No rule to write, nothing to rewrite when the school changes mail provider, and no per-message triage. This is the "you take the school, I'll take the clubs" agreement, written down where the software can act on it — and a single message that needs a different owner can be handed over from the picker on it, without touching the rule.
• Mail nobody has claimed goes to everybody. A message from a sender with no assigned handler, or from no recognised sender at all, appears in every adult's queue rather than falling into a gap. Unowned mail is visible, not lost.
• Every message carries its own history, with names. Who marked it in progress, who replied and to whom, who forwarded it on, and when — listed on the message itself. "Who replied to the school email" is answered by opening the email.
• Replies go out as the household. Sent from the household's own mailbox, so your personal address never joins the thread and the school keeps writing to the address both of you read. There is no per-device send-as setting in either parent's Gmail to get right and keep right.
• One archive, searchable by both of you. Full text plus from:, to:, subject: and body:. Email history is unlimited on both plans.
• Noise gets turned down per sender, not per household. Each sender has its own notification setting — immediate, daily, weekly, or ignore — so the school's bulletin can stop pinging two phones without anyone unsubscribing from the school.
• The household has one activity log. Mail triaged, replies sent, and everything else the household did, in one reverse-chronological page, each line naming who did it.

Questions people ask

Who replied to the school email?

On a forwarded setup, there is no way to find out except to ask, or to go looking in the other person's Sent folder, which you cannot do. On a shared inbox the reply is recorded against the message with a name and a time on it. This is the single question the whole category exists to answer, and it is a fair way to judge any tool you are considering: open a message and see whether it tells you.

Can I assign emails to my partner?

In a Google Group with Collaborative Inbox turned on, yes, conversation by conversation — you enter their email address and it is theirs. In household.email you can do either: assign the school to them once and the school's mail lands in their queue from then on, or hand over a single message from the picker on it, which overrides the sender's rule for that message alone. In plain Gmail, the honest answer is no — a label with their name is a note to a human, not an assignment.

How do we stop forwarding emails to each other?

The search people actually type is "stop forwarding emails to my husband" — or my wife, or my partner — and it is usually not about the forwarding at all. It is about being the relay: reading everything first, deciding what the other person needs, and passing it on. That is the household project manager job, and forwarding is how it is performed.

The way out is a mailbox both of you receive from directly, so nobody has to relay. Then, if you also want to stop asking each other what has been done, you need somewhere for the state to live: a house rule, a Collaborative Inbox, or a shared inbox. Getting the address set up is step one and it is covered in full in the family email address guide.

Isn't a shared inbox overkill for two people?

Often, yes — and the list above is there to say so. The size that matters is not the number of people but the number of open loops. Two adults, two children at different schools, four activities and a house is a couple of hundred messages a term carrying about thirty things somebody has to actually do. That is not a lot of email. It is a lot of unfinished business, and unfinished business is what a queue is for.

What about a grandparent or a nanny who does pickups?

This is where forwarding degrades fastest: a third destination is a third rule, and the person you added has no way of knowing what the other two have dealt with. It is also where shared-inbox thinking pays off most, because "who owns this" stops being a two-way guess. Whichever route you pick, decide deliberately what a third person should see — a household inbox contains medical and school mail about children, and "everyone sees everything" is a choice, not a default to drift into.

Do we lose the mail we already have?

No, and do not let anyone talk you into a migration. Keep your existing mailbox exactly where it is. A shared address only starts collecting from the day you hand it out, and the switch is gradual — change the school first, then the clubs, then the rest as renewals come round. If it does not suit you, you have changed some addresses back, and nothing was ever only in the new place.

Sources

• The Third Shift — The Best Time to Set Up a Family Email Account Is Before Birth. The Second-Best Time Is Now., quoted above on what a forwarded family address does and does not settle.
• RFC 9051 — Internet Message Access Protocol (IMAP) — Version 4rev2, §2.3.2, for the system flags a message carries and what each one means.
• Front Help Center — Front's real-time collision detection, quoted above on what collision detection shows.
• Google Groups Help — Create a group & choose group settings, for the Collaborative Inbox setting, Who can post, and Who can view conversations.
• Google Workspace Learning Center — Make a group a Collaborative Inbox, for the settings path and the conversation-history prerequisite.
• Google Groups Help — Take & assign conversations, for taking, assigning, unassigning and the permission it needs.
• Google Workspace Learning Center — Use a group as a Collaborative Inbox, for marking complete, no action needed and duplicate, and filtering by assignee and resolution.
• Microsoft Learn — About shared mailboxes in Microsoft 365, for the subscription requirement and the organisation-only limit.
• Gmail Help — Automatically forward Gmail messages to another account, for forwarding to more than one address.

Every source above was fetched and read before it was quoted, and the menu paths in other people's products were checked against those pages on 14 September 2026. Products move — if a step here has gone stale, tell us and we'll fix it.