How do I handle a couple who disagree about a selection?

Get both opinions recorded separately before you mediate, so you know whether you are dealing with a genuine split or one person speaking for both. Then move the conversation off text — a call with a third option resolves far more of these than another round of messages, because neither party has to publicly reverse a written position.

Should both clients get their own portal link?

Yes, wherever the software allows it. It costs nothing, it keeps each answer attributed, and it means a lost or forwarded link can be revoked without cutting off the other person. A shared link is only equivalent when there is genuinely one decision-maker.

Can a client portal show who approved what?

Only if answers are stored per person. Systems that store one answer per project item can tell you what was decided but not by whom, which is precisely the detail that matters when a decision is later disputed. Test it rather than assuming it.

What if the two clients never agree?

Escalate the decision rather than the item: ask them, jointly, who has final say on this category. Most couples have an implicit answer already — one cares about kitchens and the other about the study — and making it explicit converts a stalemate into a process. Record the answer.

GuideUpdated August 12, 20266 min read

When two clients disagree: running approvals with more than one decision-maker

Most client portals put both spouses on one link and record one answer, so the later click erases the earlier one. Why that loses the most useful thing a client ever tells you, and how to set approvals up instead.

By Idan Mann, founder of NYA

The short answer

Send each decision-maker their own link. Most portals put several clients on one shared link and record a single answer, so the second person to click overwrites the first and the disagreement disappears. Separate links keep both answers attributed, and a split verdict becomes visible information rather than a silent overwrite.

Nearly every residential project has two clients, and they do not agree. That is normal, and handling it is a large part of the job. What is not normal — and what almost nobody checks before buying software — is that most client portals are built as though there were only one.

The shared-link problem

The usual setup sends one project link that both spouses use. Programa lists "Multiple clients on one link" as a feature of its client dashboard, and it is a reasonable convenience. But one link generally means one stream of answers, and one stream of answers means the last click wins.

So one partner approves the pendant on Tuesday. The other opens the same link on Thursday, dislikes it, and clicks decline. The record now shows: declined. Or it happens in the other order and the record shows approved, with no trace that anyone objected. Either way the studio sees a settled verdict, and the disagreement — the thing that was actually going on — is gone.

The failure is silent, which is what makes it expensive. Nothing errors and nothing looks wrong. You find out at delivery, when the partner who never got their objection recorded says they never wanted it — and you have a record that says they approved it.

A disagreement is information, not a mess

It is tempting to think of the split verdict as something to be resolved before it enters the system. It is the opposite. Knowing that one client loves the pendant and the other does not is the most valuable thing a portal can hand you, because it tells you exactly where to spend a phone call — and it tells you before the order goes in rather than after.

An approval process that only records consensus is really an approval process that manufactures it. It hides the two-thirds of the project that needs your judgement and shows you only the easy part.

One link, one voice

The fix is structural rather than procedural: give each decision-maker their own named link, and let the system keep one answer per link. Now both verdicts exist at once, each attributed, and the studio can see at a glance which six items they agree on and which two they do not.

This is how NYA is built, and the reason is worth stating plainly: a vote belongs to the link it was cast through. Send one link to each person and each keeps their own answer. Share a single link between two people and it still collapses to one answer — because when two people use one link the system genuinely cannot tell them apart, and inventing a tally would be worse than admitting the limit.

There is a second, subtler rule that goes with it: a client should not be shown the other person's verdict before casting their own. A partner who opens the link and sees "Approved ✓" is being asked a different question than the one you meant to ask. Independent answers first; the comparison is for you.

Setting it up on a real project

Ask at kickoff who signs off. The answer is often not the two people in the room — a parent funding the project or an absent partner may hold a real veto.
Create one named link per decision-maker rather than one per household, so the record carries who as well as what.
Scope each link to what that person needs. A client's sister advising on fabrics does not need the budget.
Say out loud that you are asking them separately and on purpose. Framed as wanting both opinions rather than as surveillance, clients like it.
When answers split, call rather than message, and bring a third option. Two people defending stated positions in writing tends to harden them.
Revoke the extra links at handover. An advisor's link should not outlive the advice.

What to check in any tool you are evaluating

Take a trial, create one project, and have two people answer the same item differently. Then look at the studio side. If it shows one verdict, that product will lose your clients' disagreements for the life of every project you run in it. If it shows both, with names, you can work with it. This takes ten minutes and no feature page will tell you the answer.

The other decision-makers nobody sets up for

A couple is the common case, not the only one. Most stalled approvals trace back to someone who was never given a way to answer, and who therefore answers through whichever client will listen:

The absent partner. Travels, never opens the link, and vetoes by phone at the worst moment. Give them their own link anyway — an unopened link is at least visible evidence of who has not engaged.
The parent funding the project. Holds a real veto and no formal role. A scoped link that shows selections but not your fee structure often keeps this relationship workable.
The builder or GC. Needs the finish schedule and lead times, has no business in the budget, and will otherwise ask your client to forward things. A scoped link ends the forwarding.
The landlord, HOA or board. Approves a narrow slice — usually exteriors, windows or anything structural — on their own timeline. Send only that slice, and start earlier than feels necessary.
The friend with opinions. Not a decision-maker, and should not receive a link that can approve. Naming this politely at kickoff saves a difficult conversation later.

The common thread is that each of these people needs a different slice of the project, which is the argument for per-link scope rather than one project link forwarded around. It also means a link is the unit you revoke: when the builder leaves the job, one link dies and nobody else notices.

Common questions

How do I handle a couple who disagree about a selection?: Get both opinions recorded separately before you mediate, so you know whether you are dealing with a genuine split or one person speaking for both. Then move the conversation off text — a call with a third option resolves far more of these than another round of messages, because neither party has to publicly reverse a written position.
Should both clients get their own portal link?: Yes, wherever the software allows it. It costs nothing, it keeps each answer attributed, and it means a lost or forwarded link can be revoked without cutting off the other person. A shared link is only equivalent when there is genuinely one decision-maker.
Can a client portal show who approved what?: Only if answers are stored per person. Systems that store one answer per project item can tell you what was decided but not by whom, which is precisely the detail that matters when a decision is later disputed. Test it rather than assuming it.
What if the two clients never agree?: Escalate the decision rather than the item: ask them, jointly, who has final say on this category. Most couples have an implicit answer already — one cares about kitchens and the other about the study — and making it explicit converts a stalemate into a process. Record the answer.

Sources

Programa — Client dashboards for designers and architects