Why we built TagBack

Every meaningful product begins with a moment.

For TagBack, there wasn't just one moment, there were two. Two very different school days, lived from opposite sides of the gate, that collided and revealed the same problem in different ways.

The parent's story: hundreds of messages in the class chat

It started in a living room, scrolling.

One of us is a parent of school-age children, and like every parent, a member of the class WhatsApp group. Over three years the same message kept arriving, in slightly different words:

"Has anyone seen a navy jumper? Name's washed out."
"PE bag missing again. Green drawstring, anyone?"
"Wrong coat came home tonight. Who's got ours?"
"Second blazer this term. Do they just vanish?"

In one year group's chat we counted the navy jumper message more than 200 times in eight weeks.

The cost added up quietly. A primary school uniform runs to about £343, a secondary uniform to £442, and a single branded prep school blazer to £119. Nine in ten children lose clothing at school every year. We bought the same blazer twice. Everyone we knew had bought something twice.

And the thing that nagged most: the jumper was almost never lost. It was sitting in a pile in a corridor, twenty metres from the child it belonged to, with a name label that had faded in the wash.

The head teacher's story: the pile that never gets smaller

The other one of us has spent twenty years in education and today leads a mainstream school of 1,700 pupils.

From that side of the gate, lost property looks different, and it looks worse.

Staff giving up lunchtimes to sort a pile nobody could match to a child.
Parents queuing at the office, often for something that had been there for weeks.
"Has anyone seen…?" emails to form tutors who had better things to do.
The end-of-term pile going to the second-hand shop or the donation box, blazers and all.

Nobody was doing anything wrong. Staff were kind, parents were patient, the office did its best. The process simply wasn't designed. There was no way for a found jumper to say whose it was, and no way for the family to find out it had turned up.

A head knows what a school can take on, and what it can't. Any answer that added work for staff was no answer at all.

Where two paths crossed

The two of us had the conversation at our own kitchen table.

One of us had spent another evening scrolling the class chat for a missing jumper. The other had spent the day watching a lost property pile refuse to shrink. We realised we were describing the same problem, just from opposite ends.

And we agreed on what a fix had to do:

Give parents a way to label once and know the moment something turns up.
Give schools a lost property process that runs itself, costs nothing and makes no work for staff.
Keep children out of it entirely: no names on labels, no tracking, no child accounts, ever.

The birth of TagBack

TagBack isn't just a label, and it isn't just an app.

It's a washable label with a code on it, a lost property station in the school that reads that code when a found item is dropped in, and a parent app that gets a message within a minute. Label it once. It comes home.

We built it to:

Put certainty where there was guesswork: the family knows, within a minute, and collects with a PIN.
Put quiet where there was noise: the class chat can finally go silent on the subject of jumpers.
Put time back where it was being spent: the school's part ends at the station.

Our mission is simple: if it's labelled, it goes home.

We're not here to add a gadget to the school day. We're parents and we're teachers, and we've built it the way we'd want it built for our own children, because they're the first ones wearing it.

That's why we built TagBack.

In the next post, we'll walk through How TagBack works: the label, the station and the app, and what each one does for parents, schools and nurseries.