B2B handoffs and subcontracting

A B2B handoff creates local work for the provider Company while preserving the original report in the client Company. The two coordinate only through information and updates published for that direct relationship.

Availability: Company only; starting or canceling requires Delegate work to external providers and report access; the provider decides with network permission. Level: Advanced.

Purpose

Use a handoff when another connected Company must perform part of the work with its own report, assignees, and workflow without entering the client organization.

Create and accept

1. On an active report, select a current agreement and offering.
2. Write the subject and select authorized categories to share. Unselected data is not copied.
3. Send the handoff. The source report waits for a decision.
4. For manual acceptance, the provider accepts or rejects; the source can withdraw while pending. Automatic acceptance creates local work immediately.
5. On acceptance, the provider receives a newly numbered report with its own workflow.

Collaborate and resolve

• Both parties can publish notes or progress in Spanish and/or English.
• The provider can request information; the handoff waits for the source until it responds.
• The provider proposes a resolution after its work and any downstream handoff have ended.
• The source accepts or rejects with observations. Rejection makes provider work active again. Acceptance closes the handoff and resolves the original report or requests a signature under the source policy.
• Either side can cancel an active handoff with a reason when no downstream handoff is active.

Subcontracting

The provider can hand its report to a third Company only if incoming authorization permits subcontracting, its local role can delegate, and another valid agreement exists. Each pair sees only its neighbor: the source does not discover the third Company, and the third Company does not see the source. Cycles, repeating an organization in one case, and more than one active outgoing handoff per report are blocked.

Required and optional information

Required: active report, permission, agreement, offering, subject, and conscious data selection. Rejection or cancellation needs a reason; every resolution needs text. Optional: automatic acceptance, additional translation, data categories, and authorized subcontracting.

Practical example

A hands a diagnosis to B. B accepts and receives its report. It needs a measurement from C and can hand it off only if A→B allows this and B has an agreement with C. C sees B, not A. After C closes, B proposes a resolution and A accepts it.

Current limits

• A converted external assignment never permits subcontracting and creates no permanent agreement.
• Updates do not automatically copy internal messages, inventory, or unselected real attachments.
• If downstream work is active, the earlier stage cannot be canceled or propose resolution.
• Ending an agreement prevents new handoffs, but accepted work must be completed or canceled separately.