Missing notification or missing work? Check before repeating an action
Read the guide →Guide preview
An absent email is not proof that a request, comment or invoice was never created.
Keep records, permissions and billing decisions coherent when plans change.
Keep records, permissions and billing decisions coherent when plans change.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
An absent email is not proof that a request, comment or invoice was never created.
Find the existing client record before creating another account or changing access.
Check identity, filters, service and recorded outcome before asking the client to submit again.
Separate the payment pause, the client’s access and the agency’s obligation to unfinished work.
Match the payment evidence to the original invoice and service before changing status or requesting payment again.
Review delivered value, unresolved work and capacity before changing the offer or renewal promise.
Transfer work and authorized access deliberately; do not delete history to make the staff list look tidy.
Keep authentication and permissions separate from search-indexing preferences, and verify ambiguous settings before relying on them.
Start with a reversible, representative workflow and preserve the old records until the new process is verified.
An exported request list is useful evidence, but it is not proof that the entire client workspace can be restored.
Settle unfinished work, agreed files and access changes separately from ending recurring billing.
Automate stable rules with observable outcomes; keep consequential ambiguity with an accountable person.
Preserve original work identities and distinguish known records from uncertain actions before continuing elsewhere.
Judge the portal by observed coordination improvements and remaining costs—not by how much setup effort you have invested.