How do I investigate how a role changes across different organizations?

Treat the title as a search clue, not as your comparison unit. Compare the responsibilities, tasks or skills named, apparent scope, and organizational setting. The Occupational Requirements Survey manual distinguishes an occupation—responsibilities, skills, and tasks common across establishments—from a job at a particular establishment. Its example contrasts registered nurses in a school district and a hospital. That illustrates why context matters, but it is not a complete account of how every role varies between employers. [S1]

Choose descriptions that appear to cover related work, even if their titles differ. Use the same headings for each organization, and leave gaps blank rather than guessing.

Capture concise notes rather than whole passages. Record the organization and setting, title, responsibilities stated, tasks or skills named, scope clues, and unknowns to verify. Keep exact wording where it could affect your interpretation.

Here is a compact grid you can copy. Use one set of notes for each organization:

Organization / setting: [name and context] Title: [title used] Responsibilities stated: [short notes] Tasks or skills named: [short notes] Scope clues: [exact wording or clue] Unknowns to verify: [question]

Repeat those fields for Organization A, Organization B, and Organization C. This keeps the comparison consistent without forcing the postings into identical descriptions.

Use the posting’s wording as evidence and label interpretations separately. A hypothetical example—not a claim about typical jobs—might compare three “operations coordinator” descriptions:

• Organization A: Responsibility stated: “coordinate weekly schedules.” Scope clue: one team is mentioned. Unknown: who sets priorities?
• Organization B: Responsibility stated: “manage scheduling across departments.” Scope clue: multiple departments are mentioned. Unknown: what does “manage” include?
• Organization C: Scheduling is listed. Scope clue: not specified. Unknown: who sets priorities and what work does the role cover?

These notes capture what the hypothetical descriptions say; they do not establish that one role is more senior or has more authority. Mark “broader authority,” for example, as an inference unless the description supports it. Keep the original wording available so you can check your summary.

Compare the descriptions across the same dimensions: responsibilities, tasks or skills, scope, and setting. A difference is better supported when the descriptions name different duties or boundaries. A difference based only on a title or vague adjective is less certain. Separate each note into “stated” and “inferred,” and mark missing information as unknown.

Turn important unknowns into neutral questions, such as: “Could you walk me through a typical project this role handles?” “Which responsibilities are owned by this role, and which are shared?” or “Who sets priorities for this work?” Tailor questions to the gaps in your grid. If you are comparing organizations, ask comparable questions at each one so the answers are easier to line up, while allowing each organization to explain its context.

A reusable process is to select related descriptions, fill the same grid fields, preserve meaningful wording, label interpretations, and ask about important gaps. Keep track of which description or conversation supports each note. The result is a grounded comparison of described work and open questions—not proof that roles with similar titles are equivalent.