Tag and flag clients and jobs
Mark the things you need to know at a glance — VIP, rush, no socials.
A tag records something true about a client or a job that isn't a workflow step — “VIP”, “Rush”, “No socials”, “Pays late”. Statuses tell you where the work has got to; tags tell you what to remember about it.
Making a tag
Give it a short label and a colour, and drag the list into the order you want. Short wins: a tag is read in half a second on a crowded screen, so “No socials” beats “Client prefers no social media sharing”.
Flags
Turn a tag into a flag when it's something you can't afford to miss. Flags sort to the front and are the only tags shown in tight spaces — pipeline cards, gallery cards and the gallery header — where there's only room for one or two.
“No socials” is a flag: publishing a photo you weren't allowed to publish is a real problem. “Repeat client” is a tag: nice to know, but nothing goes wrong if you notice it a minute later. If everything is a flag, nothing is.
Where a tag turns up
You tag two things — a client or a job — and everything attached inherits them. Tag a client and their enquiries, bookings, galleries, invoices and contracts all carry it. Tag a job and it rides along with that job's work.
That's why there's no tag button on a gallery or an invoice: the tag belongs to the person or the work, so it stays right when you add a gallery six months later.
Before you share a gallery
If a flag is present, the gallery's Share screen says so before you hand the link over. Handing out a link is the moment a “No socials” or “Surprise gift” flag actually matters, so that's where it interrupts you.
Deleting a tag removes it from every client and job that carried it, and that can't be undone. If you've outgrown a label, rename it rather than deleting and starting again.