September 3, 2026

A virtual assistant often receives work through several channels at once. A procedure sits in a shared folder, a manager adds detail in chat, and a task card carries an older example. Each source looks legitimate. When they disagree, a new assistant may choose the most recent message, follow the most detailed document, or combine parts of both. None of those choices is reliably safe.

Onboarding should teach a resolution protocol before the first conflict appears in live work. The protocol does not ask the assistant to judge which coworker is more credible. It defines how to recognize a conflict, contain the task, preserve the competing instructions, and reach the owner who can choose.

Show what counts as a source conflict

Two instructions differ without always creating a conflict. One document may explain the general process while a task card provides the customer-specific input. The sources can work together. A conflict exists when following one direction would break another, change the required outcome, exceed the assistant's authority, or make it impossible to tell what completion means.

Use examples from the role during onboarding. A customer support assistant might see a response guide that permits a replacement while a current account note says replacements require review. An administrative assistant might find a calendar rule that protects focus time while a direct message asks for an immediate booking inside that block. A recruiting assistant might receive one candidate status from the applicant system and another from a manager's spreadsheet.

Teach the assistant to name the exact disagreement. "The instructions are confusing" is too broad. "The task card says to send the file externally, but the folder label says internal use only" identifies the two sources and the action at risk.

Establish a source order without pretending it solves everything

Teams need a basic source hierarchy. It may place current policy above examples, system records above private notes, and approved task instructions above informal suggestions. The hierarchy should name source types, owners, and the place where the current version can be found.

A hierarchy speeds up ordinary choices, but it cannot answer every case. A supposedly authoritative document may be out of date. A manager may issue a valid exception. A system may contain a stale status because a handoff failed. Tell the assistant when the normal order applies and when the disagreement must be routed.

Avoid rules such as "always follow the newest message." Recency does not prove approval. A quick chat request can be newer than a reviewed operating procedure while still lacking the authority to replace it. The source order should depend on ownership and effective status, not convenience.

Give the assistant a safe pause action

Recognition is useful only if the employee knows what to do next. Define the smallest action that prevents the conflict from spreading. The assistant may save a draft, stop an upload, leave a record unchanged, or hold a message in the review queue. State which reversible preparation can continue while the decision is pending.

The pause should protect existing information. Do not delete one source, edit the task to make the instructions appear consistent, or overwrite a system value. Those actions hide the evidence that the owner needs. If the task involves customer data or access rights, the assistant should not copy material into an unapproved location merely to assemble a report.

Make the pause visible to affected teammates. A short status can say that the task is held because two named sources direct different actions and that an owner decision has been requested. This is clearer than allowing others to assume the assistant forgot the work.

Capture both instructions in context

A useful conflict record contains the source location, owner if known, effective date or version when available, relevant instruction, affected task, and action currently on hold. It should quote only the minimum necessary language and link to approved internal locations rather than duplicating sensitive content.

Context matters. A screenshot without its folder, record, or timestamp may mislead the reviewer. A copied sentence can lose a condition stated in the preceding paragraph. Ask the assistant to record enough surrounding information for the owner to inspect the original source.

The record should also state what the assistant expected to do before finding the disagreement. That reveals whether the conflict changed a planned action or merely raised a general question. It lets the owner respond to the immediate task without conducting a broad process review first.

Route the decision to the source owner

The nearest available manager is not always the right decision maker. Map common source categories to owners during onboarding. Policy conflicts may go to people operations, access conflicts to a system owner, customer handling conflicts to the account owner, and workflow conflicts to the process owner.

The assistant's request should ask for one decision. It can identify the competing directions, the held action, the deadline, and the proposed interpretation if the role allows recommendations. It should not ask the owner to reconstruct the entire task.

For example: "The current task asks me to add the new contact to the client mailing group. The access register limits this role to the internal update group. I have not changed either group. Please confirm which group applies to this task before the scheduled update window closes." The request shows containment and gives the owner a precise choice.

Handle urgent work without inventing permission

A deadline can make an unresolved conflict feel like permission to choose. It is not. Define an urgent route with a backup owner and response window. If no authorized owner responds, the default should identify which work remains held and which safe alternative, if any, is allowed.

The team may permit a temporary action that is reversible and carries less consequence. For instance, the assistant might prepare a draft without sending it or assemble non-sensitive inputs without updating the live record. This option must be part of the role guidance. The employee should not invent a workaround under pressure.

After an urgent decision, record who authorized it and whether it applies only to that case. A one-time exception should not quietly become the new procedure. The process owner can decide later whether the source hierarchy or standard instructions need revision.

Correct the sources after the task is resolved

Resolving the immediate assignment is only half the work. If both sources remain active, the next employee will meet the same conflict. Assign an owner to correct, retire, relabel, or connect the sources. The virtual assistant can flag the locations but should not rewrite controlled guidance without authority.

The correction record should say which source governs, when the change takes effect, and what happens to tasks already in progress. If an example remains useful, label it as an example rather than an instruction. If a chat decision changes a procedure, move that decision into the controlled source instead of relying on search history.

Close the assistant's conflict record only after the task decision and source follow-up have owners. The source correction may take longer than the task, so track the two outcomes separately.

Practice with conflicts that look plausible

A training case should not make one source obviously absurd. Give the assistant two credible instructions with a specific consequence. Ask them to identify the conflict, pause safely, collect context, and draft the owner request. Then change the source types in a second case so the exercise tests the protocol rather than memory.

Review the reasoning as well as the final choice. An assistant who guesses the governing source correctly but edits the record before approval has not followed the boundary. An assistant who pauses everything when the conflict affects only one field may need coaching on containment.

Finish onboarding practice by showing the actual source map for the role. Name the hierarchy, conflict routes, urgent backup, and allowed pause actions. Then ask the assistant to resolve one final case without hints and retain the resulting record as readiness evidence.

End the conflict with a reusable answer

The manager should return a decision that covers the current action, the authority behind it, and whether it creates a lasting rule. The assistant can then complete or reroute the work without treating a narrow answer as permission for future cases.

A good protocol makes disagreement visible before it becomes an unauthorized change. Add one plausible source conflict to the assistant's practice queue, assign its real decision owner, and confirm that the pause action works before live work begins.

Continue building the workflow

Connect this process to the virtual assistant role brief, then use the virtual assistant onboarding checklist for the next handoff. The U.S. Equal Employment Opportunity Commission explains that employment selection procedures should be job related and consistent with business necessity.