How we work
How we keep track of what we owe a client
A meeting can end with a decision, a document we owe, and a question we still need to answer. Our delivery workspace keeps each commitment with its owner, its due date, and the conversation where we made it.
What have we agreed to deliver?
Before we confirm a session, we check the signed agreement, the payment record, and the work already promised. Those records answer different questions. A receipt confirms a payment. The agreement tells us what the client can expect.
Keeping the records together gives the person preparing the meeting a clear place to start. They can see which sessions remain, what the client has shared, and which decisions are still open.
Give each promise a place to go.
When a session finishes, its record holds the decision and the work it created. Each deliverable has an owner, a due date, and a link back to the meeting. If we reopen the notes to make a correction, the original commitment stays in place.
The remaining sessions and the support window are tracked separately. When a client uses their last session, we can still see how long we have agreed to answer follow-up questions.
Close a meeting and follow the next commitment.
Follow an engagement from its source request to a reviewed follow-up. Payment, signature, sessions, delivery, and support are separate records.
About this example
Fictional data. Prebuilt outputs, not live AI. No client data is uploaded and no messages or changes are sent to a client system. Interactions stay in this page until reset or reload; where offered, downloads save only the authored sample files. The interface illustrates the working patterns described on this page.
Client delivery
Meru · implementation workspaceYou are Morgan, responsible for the next client deliverable.
The meeting ends. The commitments stay in view.
Step 1 of 3: Review the commitments
- Review the commitments
- Confirm the follow-up
- Prepare the handoff
Alder Field Services has finished discussing its quote handoff. Before closing the final working session, check what each person has promised.
MTG-028-02 · October 28 · 10:00–10:45 · Pacific
The decision: use one quote packet for site details, photographs, access instructions, and the next owner. Price approval stays with the estimator.
- Morgan’s commitment
- Pilot brief by October 30
- Nora’s commitment
- Example packet before November 2
Read the session and engagement records
MTG-028-02 · retained session notes
- Current handoff: A coordinator copies the site-visit notes into a quote request, then asks the estimator whether the photos and access instructions are complete.
- Decision: Start with one shared quote packet: site details, photographs, access instructions, and the next owner. Keep price approval with the estimator.
- Client commitment: Nora will supply an anonymized example quote packet before November 2. No client documents are included in this sample.
- Meru commitment: Morgan will prepare the pilot brief by October 30, with required fields, review rules, and a small test plan.
Agreement signed October 21. Payment received October 22. Two working sessions, a current-state map, and a written pilot brief. Follow-up questions remain in the support window after the sessions are used.
One engagement, without losing the work between meetings.
- 01Sources
Request + engagement + meeting
Keep the original scope beside the work. - 02Working record
1 session remaining
Support remains active independently of session balance. - 03Next owner
Morgan Lee
Pilot brief due October 30 after the session is completed.
Next actions
2 ready to reuse1 to review1 still to obtain
Check readiness without chasing receipts
BeforeFind the agreement, then separately check whether payment and a calendar entry exist.
Signature and payment are recorded. The second session is linked to the engagement.
ENG-028 · independent signature and payment fieldsIn the recordCarry the meeting into the next action
BeforeRead the notes, create a follow-up, and copy its due date and owner into a separate list.
The notes already identify the pilot brief, its owner, and its due date. Complete the session to create the linked item.
MTG-028-02 → DEL-028-02Review neededKeep support separate from session credits
BeforeRe-read the scope to determine whether using the last session also ended support.
Support through November 11, 2026 does not depend on session balance.
ENG-028 · support commitmentIn the recordAsk only for the missing working material
BeforeRepeat the request for context already captured, while the actual sample packet stays unassigned.
Nora owns the anonymized quote packet due before November 2. The business problem and proposed handoff are already in the record.
REQ-028 + WORK-028 · client actionFollow-up needed
These are work items in this fictional file, not a count of calls or hours saved. Reuse dated evidence; contact people for changes, missing facts, and decisions that still need a conversation.
Someone reviews the handoff.
The delivery owner checks the promised scope, reviews the session notes, and reads the follow-up before sharing it. If a request goes beyond the agreement, the owner takes it back to the client for a decision.
Where does context get lost in your delivery?
It might be the handoff from sales to onboarding, or the stretch between a review meeting and the proposal a client is waiting for. Tell us where your team has to piece the story back together.
Start a conversationFollow an account review from source records to brief in BloomChat
We use a local, single-user workspace for our own advisory engagements. The walkthrough uses fictional records and a prebuilt handoff preview.