The point where work gets scattered
A client may have several projects, invoices and payments at once. A contact name alone is not enough to explain which work a payment covers or which proposal version a new request refers to.
Give the engagement a recognizable reference
Choose a short project reference such as ‘NORTH-WEB-01’ and use it in the scope, relevant messages, invoice descriptions and handover index. Add a plain-language title so neither person has to decode the identifier. For recurring work, include the service period as well as the client name. Do not reuse one vague ‘monthly work’ label across several distinct engagements.
Build a small project index in your existing working process. It should point to the current accepted scope, open change requests, payment requests, confirmed payments, delivery location and next decision. Keep sensitive source material in the appropriate access-controlled location rather than copying it into every summary. The index is a navigation aid, not a replacement for the originals.
Keep the document and payment states distinct
Describe the actual stage using ordinary labels: proposal under review, scope accepted, invoice sent, payment unfinished, payment confirmed, delivery ready or client inspection pending. More than one can be true at once. An accepted scope can have an unpaid invoice; a confirmed initial payment can precede final delivery.
For example: ‘NORTH-WEB-01: scope v2 accepted; $900 initial payment confirmed; Homepage v1 awaiting feedback; final payment not yet requested.’ This is more useful than ‘project active.’ It tells the next person what happened, which source to inspect and which action would be premature. Do not infer client acceptance from the presence of a receipt.
- Document version and its actual review decision.
- Payment request, amount and purpose.
- Confirmed payment result and allocation.
- Delivery status and the next open question.
Resolve mismatches before continuing
If the invoice requests a different amount from the accepted schedule, inspect the documents and any accepted change before sending another reminder. If a payment has the right client but no clear project reference, ask which work it covers and confirm your allocation. If the status is unfinished, check that exact payment result before asking the client to attempt it again.
Sample clarification: ‘I can see the confirmed $500 payment, thank you. We have two open projects. Is this intended for the July support invoice J-07 or the website initial payment W-02? I’ll update the project record after we confirm.’ Avoid silently assigning the payment to whichever balance you would prefer to reduce.
Prepare a concise client-facing update
Use a short message that states the relevant work, what is confirmed and what needs a response: ‘Website scope v2 remains the current version. The initial $900 payment is confirmed. Please review Homepage v1 by Thursday or suggest another date. The booking-page addition is still a separate open change.’ Link only to material the recipient is allowed to see.
At closeout, keep the final delivery index, actual accepted versions and payment records discoverable under that same reference. Retain the history appropriate to your work rather than replacing everything with a single ‘complete’ summary. When a later question arrives, inspect the relevant record and continue the relationship with its context intact.
Keep the context with the conversation
Use Messages with the selected client and payment context you want to discuss. Business can help summarize that context and prepare an update for review. Keep ordinary documents in your established document process, inspect confirmed Bankeiz payment records for payment status, and use Calendar for a separately confirmed next appointment. The shared reference connects the work without merging its approvals.
Understand your Twin · See Business access and metered AI usage