Two Customers, One Asset: Link the Work Without Merging the Orders

Record the common asset and map each task to its own instruction before combining the visit. That makes it possible to share useful context, perform an assessment once and keep each customer's agreed work visible.

Start with the work each customer commissioned

A shared asset reference establishes a connection between the requests. It does not establish that they are the same order. The site address, an equipment-provider role or a familiar contact also leaves the charging question unanswered.

For each request, find the current scope, the person who confirms decisions about it and the source of the bill-to instruction. Record what is agreed and what remains a question. If one customer says another organization will pay, keep that statement attached to its source while the appropriate people confirm the arrangement.

The service coordinator also needs the delivery team's view: which tasks are distinct, which use the same evidence, and which depend on an earlier result? Two requests mentioning “assessment” might describe the same task, or different work. Compare their contents before removing one or scheduling both.

This is a working record for coordinating service requests. It does not determine legal ownership of an asset, responsibility for a charge or an accounting treatment.

Work through one asset and two confirmed orders

The organizations, people, documents and observations in this example are entirely fictional. They describe no actual customer or product demonstration.

North Quay Equipment supplies unit U-27, used at Fern Workshop's site. Both contacts have confirmed that their requests concern U-27. The asset match is already established; the coordinator is deciding how to organize the work.

North Quay's accepted quote NQ-06, referenced by order N-14, covers one condition assessment and an assessment note. Fern's accepted quote FW-03, referenced by order F-08, covers a maintenance-planning discussion and a follow-up action list using that assessment. Fern's scope does not commission a second condition assessment or any repair.

The coordinator initially has two provisional assessment appointments because both enquiries mention the same unit. Before confirming them, she compares the agreed outputs with the service lead. The lead identifies one assessment task under N-14 and a separate planning task under F-08.

There is still an evidence dependency to resolve. North Quay's decision contact confirms in N-15 that the assessment note can be supplied to Fern for this planning work. Fern's decision contact confirms in F-09 that the referenced note is the input to its discussion, with no second assessment included. These are instructions for this fictional case, rather than a general rule about sharing customer documents.

The delivery lead then confirms a visit sequence: assessment first, followed by Fern's planning discussion once the agreed note is available. Both customers confirm that sequence. If the note is not available as planned, the coordinator will review the timing of Fern's discussion with its contact; a second assessment is not automatically added to F-08.

Fill the task-to-order boundary matrix

The completed matrix records the agreed plan before the visit. It does not mark the assessment, discussion or billing as completed.

The coordinator now confirms one coordinated visit and removes the second provisional assessment appointment. She retains both customer requests and their agreed outputs. The removed appointment was duplicate scheduling work; F-08 remains an active, separate instruction.

That is the resolved decision: one assessment, two agreed outputs and two customer-specific instructions, connected through the asset and the visit. Actual delivery and the assessment-note handover remain to be recorded.

One visit; two separate orders

Fictional U-27 coordination plan

Shared unit U-27

One coordinated visit

North Quay · order N-14

One condition assessment and assessment note

Keep its scope and bill-to instruction here

Assessment first

Agreed note handover

North Quay N-15 and Fern F-09

Actual handover still to be recorded

Planning waits for the agreed note

Fern · order F-08

Planning discussion and action list

No second assessment or repair in this scope

Keep its scope and bill-to instruction here

Agreed plan. Assessment, discussion and note handover are not recorded as completed.

Keep shared evidence precise

Choose a clear reference for the assessment note and identify its actual version when it exists. Fern's record should show which note its planning work used, who supplied it and when. A reference to “the latest report” leaves a colleague unable to explain the input to an earlier decision.

An agreed handover is also different from a completed handover. Record when the note is actually supplied through the agreed process. Keep any remaining question visible if the recipient, intended use or current instruction is unclear.

If Fern later asks for a repair, capture that as a new request for a scope decision. The asset connection provides context; the existing planning order has not established an agreed repair scope, price or payer.

Check the customer boundary before preparing documents

Use the applicable quote, order and later confirmed instructions when preparing each customer's documents. A common visit reference can help someone find the evidence. It cannot supply missing acceptance, a missing bill-to instruction or a new charging agreement.

In the fictional case, the assessment preparation follows NQ-06 and N-14. Fern's planning preparation follows FW-03 and F-08. No cost split is inferred from time spent at the same site, and no single combined customer account is created to make the diary simpler.

If the actual work differs from this plan, record the difference and obtain the appropriate decision through your existing process. Preserve the original instructions so the reason for any later change remains understandable.

Copy the boundary check for your next shared asset

Start with the identifying evidence for the common unit and the two request references. Add one row for each task, shared input or proposed document instruction.

Ask a colleague to use the filled record to answer three questions: which task is performed once, what each customer has separately agreed, and what still needs to happen before the next task can proceed. They should be able to find those answers without treating the common unit as a single customer relationship.

When evaluating Konekt CRM, use this fictional two-customer case to test your intended setup. Check how colleagues would retrieve the shared asset or visit reference alongside each customer's scope, source documents, responsible person and bill-to instruction. Verify the actual functions, access and plan required, and any proposed connection to your service or billing tools.