Give Your Whole Team the Same Digital Card

One person making a digital card is easy. Forty people making their own is how you end up with four versions of the logo, three spellings of the company name, and someone's personal mobile on a card that went out to clients.

The fix is not stricter instructions. It is making the shared parts genuinely shared.

One template, many people

A template holds everything that should be identical: the page design, the company details, and the QR style. A member is one person on that template — their name, title, direct line, photo.

Each member gets a real card of their own, with its own address, its own QR code, and its own scan numbers. They are not copies of a master file; they are individual cards that read their shared parts from one place.

You build the template once in the Employee vCards builder, then add people to it.

What changes once, changes everywhere

This is the part worth understanding, because it is where most systems quietly fail.

The public card is assembled when someone opens it, from the template plus that person's details. Nothing is copied into the individual cards. So when you change the office address, the logo, or the colour of the page, every card is already different the next time it is opened.

Because nothing is copied, nothing can half-update. There is no state where twelve cards have the new address and twenty-eight still show the old one — which is the usual outcome when a system copies settings down to each record and one of the writes fails.

• Move office: change it once.
• Rebrand: change it once.
• Change the main switchboard number: change it once.

And none of it requires reprinting a single QR code, because the codes point at addresses that have not changed — only what sits behind them has.

What stays personal

Name, job title, direct line, email, photo. The things that are genuinely about one person stay with that person, and they can be edited individually without touching anybody else.

The line between shared and personal is worth drawing deliberately before you roll out. A department name in the template means reorganising becomes one edit; a department name typed per person means forty.

Rolling it out to forty people

You almost certainly already have the list — in a spreadsheet, in your HR system, in an email signature generator.

• Build the template and get it right with two or three real people on it first.
• Import the rest from your spreadsheet rather than typing them in.
• Export it back out when you need a record, or to hand to someone else.

Check a couple of cards on an actual phone before you send anything out. A card that looks right in a builder and wrong on a 375-pixel screen is the one complaint you will get forty times.

When someone leaves

Worth deciding before it happens rather than during a handover.

• Remove the card if it was only ever theirs and the contact should stop working.
• Reassign it if the role matters more than the person — a "Head of Sales" card that a client already saved keeps working for whoever holds the job.

Printed cards are the argument for reassigning. A departed employee's card in a client's drawer is a dead end at exactly the moment someone is trying to reach you.

Who this is actually for

The threshold is not headcount, it is churn. Five people with stable details do fine making their own cards. Fifteen people where titles change, someone joins every quarter and the office moved last year is where managing them separately stops being tenable.

If you are still deciding whether digital cards are worth it at all, the case against paper comes first — this post assumes you have made that call.

Decide what is shared before you add anybody. Everything else about running forty cards follows from that one line.