Field workflow guide

Responsible follow-through starts with a human decision

A clear internal draft can make an unresolved question or resource need easier to review. It does not decide what to send, whom to contact, what content is approved, or whether a next action should occur.

Scope boundary. This guide does not authorize clinical advice, content approval, compliance decisions, HCP or employee profiling, patient/EHR handling, or automatic external action.

01

Keep the draft internal

An internal draft organizes only the limited, permitted material that was available for the defined purpose. It is not an approval, conclusion, profile, or instruction.

02

Review the boundary first

A designated person checks whether the material and stated purpose remain within the organization-defined workflow. If not, stop or use a separate established process.

03

Record a human disposition

The organization’s decision owner may keep, revise, narrow, pause, escalate, or discard the draft. The decision belongs to the organization, not the tool.

04

Authorize any next action separately

A message, meeting, CRM update, publication, submission, or other state-changing action needs its own human authorization path outside this guide.

A useful review prompt

Ask whether the next action has its own owner, authority, and evidence.

A recurring resource need, unresolved operational question, or stated follow-up topic may be useful internal context. It remains context. Before the organization acts, a designated person should decide whether the action is within the organization’s process, what information is needed, and who is accountable for it.

A separate action check should identify:

Action owner
The person authorized to decide whether the action occurs.
Purpose
The narrow reason for the action.
Permitted basis
The material or process that supports it.
Stop condition
The fact that pauses or prevents the action.

Plain-language answer

“Route it” is not the same as “send it.”

An organization can use an internal review process to determine whether a topic belongs with a particular accountable owner. That does not authorize an automated email, a system update, a customer or HCP communication, a marketing decision, a content approval, or a business decision. Each of those actions needs its own authorization and applicable organization process.

Related guide

See the common workflow core for MSL, pharmaceutical, and medical-device teams.

Read the field roles guide