Collect what the matter needs. Answer the question before they call.

The question in the room

“My client rings me every Thursday to ask what is happening, and I still do not have the three documents I asked for in March.”

The client-facing reads are default-deny and screened again on every read. One write path is not yet at that standard, and it is named in the repository rather than here for the first time: publishing an invoice notifies every enabled portal client on the matter instead of the one principal it belongs to, and it writes its thread message without the exact-recipient receipt the client feed reads. Until that writer carries a receipt, a co-client on the same matter can learn from the notice that an invoice exists.

Refusals

What it will not do, and why.

Show a client a document whose privilege review never happened.

The classification gate is a positive allow-list of two reviewed values. Blank, unrecognized and never-classified are not clean, and a subtractive filter over an empty lookup removes nothing and leaves the document sitting in the client's room. The set of ids a client may see is built up, never narrowed down.

Read a designation it could not fetch as no designation at all.

An absent attorneys-eyes-only marking and a failed read of that column are different facts. Silence is not a restriction; a failed read is not determinable and refuses the whole candidate set rather than a quietly smaller one. A page returning at the database row cap counts the same way, because a truncated screen loses restricted ids quietly. The asymmetry is the control.

Let one portal client see another's own upload.

Two principals on one matter are two clients, and what one hands the firm is the firm's to read and not the other's. The uploader exclusion runs strict on the paths that serve document text, so a denylist that cannot be computed refuses the read rather than falling back to no exclusion.

Reclassify a document to get it around a protective order.

The refusal names the axis on purpose, so nobody reaches for the wrong one. Attorneys-eyes-only is a court-ordered access restriction, not a privilege verdict, and an adversary's production can be correctly classified confidential, which the privilege gate admits, and still be forbidden to the party under the order. The remedy is recoding the designation in discovery review or obtaining relief from the order, and the message says so instead of leaving the attorney to improvise.

Tell a client their upload was reviewed because it arrived.

Reviewed is a claim about a lawyer's attention. Each state is the reading of a receipt that already exists, and a status the code could not read reports as unknown. A file sitting in a folder and a file an attorney has read must not render as the same sentence.

Assemble the matter's weak spots for the client.

The plain-language outlook is theirs to have. The strategy, the vulnerabilities, the arguments the other side would use and the internal settlement figure are work product, and no tool may be used to reassemble them. The question is answered by naming the attorney who handles it and is flagged for that attorney rather than quietly dropped.

Give every line of the bill the same tick.

A client who learns that the tick beside a gated receipt is the tick beside a hand-typed entry has been taught, by us, that our ticks are decoration. Four results, four sets of words: passed, failed, checked and absent, and could not check. The last two never converge. A line whose amount could not be read says so rather than showing zero.

Hand a client a directory of everyone else on their matter.

Item delegation is one grant, for one current item, authorized by firm staff. What the client sees is a frozen, attorney-approved label on that exact grant. The request's original recipient never changes, so the co-client privacy boundary stays where it was drawn.

Put a deadline's description in front of the client.

What is due and when is the client's. The description column carries the engine's authority and tolling caveats and, on a hand-entered date, free-text attorney strategy, so it is not on the list a client-facing deadline row is copied from. Two client reads once forwarded the whole row. The matter timeline is screened the same way, joining the published record with a separately screened chronology.

Ask a client to decide the same thing twice.

An exact retry returns the immutable row already recorded; a retry that changes the option or the note is refused as a conflict instead of overwriting the first answer. A transient failure in the task that tells the lawyer is repaired on the next close, not by putting the question back in front of the client. The stored option is a key and a label and nothing else, so no extra field rides along into the client payload.