Job Shadowing Guide: What to Observe, Ask, and Record

What a job shadow can tell you

A job shadow can reveal the sequence of work that disappears from a polished career description: preparing before a meeting, checking details afterward, waiting for information, switching between tasks, or adapting to a client's needs. It gives you a situated view of a role. It cannot show every season, employer, career stage, or responsibility, and watching someone perform a task is different from learning to perform it yourself.

UConn distinguishes informational interviews from job shadows by the opportunity to observe work over a longer period. [1] Choose observation when your uncertainty concerns what the working day actually feels like or how activities connect. Choose a conversation when you mainly need information about entry routes or qualifications. Often a short conversation first helps you decide what would be worthwhile to observe.

Define one learning goal before contacting a host. For example: “I want to see how an operations role moves from an unexpected problem to a documented decision.” A second goal might concern the environment: “I want to understand how much work is interrupted by requests.” These goals are more actionable than trying to determine whether an entire profession is right for you in one afternoon.

Write down what cannot be learned through this visit. You might not observe confidential interactions, rare emergencies, annual planning, or independent work carried out elsewhere. An explicit boundary protects the quality of your conclusion. The absence of a task during a short visit does not mean that task is unimportant or uncommon.

Find a suitable host and make a specific request

Look for a host whose setting matches your learning question. If you are exploring a customer-facing role, observing an internal planning team may answer the wrong question. If you want to understand entry-level work, a senior leader's schedule may be misleading. Ask whether someone in the relevant team or at the relevant career stage would be a better contact.

Start with people you can approach appropriately: an alumni contact, an instructor's suggested connection, a professional you have already spoken with, or an organization's published shadowing program. Avoid assuming that a personal invitation permits access to every part of a workplace. Some settings have formal processes, supervision requirements, or restrictions that the host cannot waive.

An illustrative request is: “I am exploring operations support and would value observing how your team receives and prioritizes requests. Would a short job-shadow visit be possible? I can work around your schedule and understand that some activities may be restricted.” State the desired scope without insisting on particular meetings or contact with clients. Make it easy for the person to suggest a smaller visit or a conversation instead.

Before accepting, confirm who will coordinate the visit, the date and duration, where to arrive, any preparation, and what you may bring. Ask about accessibility, physical demands, clothing, and transport if those affect your participation. Share only the information necessary to arrange the experience. If an organization has an application or clearance process, follow its current published instructions; do not infer eligibility from another person's account of a previous visit.

Agree on observation boundaries before the visit

A shadow is a learning opportunity, not permission to perform the job. Establish whether you will only observe, discuss anonymized examples, or try a supervised demonstration that the host explicitly permits. Do not handle equipment, access records, contact customers, or complete professional tasks simply because an opportunity appears. If you are invited to do something unfamiliar, ask what is appropriate and who is responsible for supervision.

Clarify how you may take notes. Written notes about generic workflows may be acceptable when photographs, recordings, or screenshots are not. Never assume that information visible on a screen can be copied. Avoid recording names, case details, internal passwords, or identifying information. If you accidentally encounter sensitive material, follow the host's instructions rather than retaining it as career-research evidence.

Ask when questions would be least disruptive. Some hosts welcome discussion during routine work; others need to concentrate and prefer a debrief. Agree on a signal or time to pause. You may need to step out of particular activities, and that is part of understanding the role's boundaries rather than a failure of the visit.

Prepare your own limits too. Know when you need to leave and how to communicate if the setting becomes physically uncomfortable or inaccessible. You can request a different observation arrangement without making a conclusion about your overall capacity for the occupation. A useful visit depends on a workable arrangement for both people. The goal is accurate learning, and neither privacy nor safety needs to be traded for a more complete view.

Observe tasks, transitions, and decisions separately

Use three observation lenses. First, record the task: what is being done and what output it creates. Second, record the transition: why the person moves to another activity, what they must wait for, and whether interruptions are planned. Third, record the decision: what they can decide independently, what requires approval, and what information they need before acting.

O*NET's occupational reports separate task information from work context. [2] That distinction gives your notes a useful structure without suggesting that an occupational profile predicts this particular workplace. You may see the same task performed under very different conditions across organizations. Drafting a report alone with a clear deadline differs from drafting it while responding to frequent urgent requests.

Notice invisible preparation and follow-through. A short presentation may require extensive checking. A brief customer interaction may generate documentation and coordination. Ask permission to learn about those surrounding steps. If you observe only the public-facing moment, you may overestimate how much of the job consists of that activity.

Record time carefully. A rough sequence can help reconstruct the visit, but do not convert a few observed hours into a confident weekly percentage. Instead write, “During this visit, I observed three interruptions while the host prepared a report.” Then ask whether that pattern was typical. Preserve both the observation and the host's explanation. They may differ because your visit was unusual, because the host's work varies, or because a small sample naturally misses important variation.

Questions for preparation, observation, and debrief

Before the visit, ask which work you are likely to see, what may be excluded, and whether the day is ordinary or unusual. These questions help you interpret what happens later. You can also ask which background material would make the observation easier to follow. A short glossary may be more useful than trying to read an entire technical manual.

During permitted question periods, connect questions to events. “What information did you check before deciding that?” “What would make you escalate this issue?” “Which part of that task requires the most experience?” “How would a new colleague begin learning it?” Specific questions are less likely to produce vague statements about being organized, adaptable, or good with people.

During the debrief, ask about what you did not see. “Which important tasks were absent today?” “How does a busy period differ?” “What responsibilities would someone entering this role have?” “Which conditions depend on this organization?” Yale's informational-interview guidance emphasizes questions about daily work and the work environment; those themes also provide useful debrief prompts. [3]

Avoid asking the host to interpret your personality or endorse your suitability. Instead describe a specific reaction and invite clarification: “I enjoyed following the problem-solving, but the number of interruptions surprised me. Is that typical here?” The host can comment on the conditions; you remain responsible for evaluating your needs. If their explanation challenges your first impression, record both rather than silently replacing what you observed with what you expected to hear.

Worked example: a shadow that changes the next question

Consider Daniel, an illustrative student exploring community-program coordination. He imagines a role centered on planning events and speaking with participants. His learning goal is to see how a coordinator balances direct contact with behind-the-scenes work. He arranges a short visit through an appropriate contact, with no access to confidential participant information.

The host begins by reviewing a schedule and resolving a room-booking conflict. Daniel then observes preparation of materials, a permitted team discussion, and follow-up with another department. He enjoys the practical problem-solving. He is less enthusiastic about updating several records after decisions have been made. His initial note says, “Too much administration,” but he replaces that interpretation with a description of the specific tasks he saw.

In the debrief, the host explains that the visit occurred before an event and that delivery days are different. Daniel asks which records are routine and why they matter. He learns that some support coordination while others meet organizational requirements. This does not make him enjoy the work automatically, but it helps him distinguish necessary follow-through from an inefficient process he had imagined.

Daniel's conclusion is conditional: he wants to explore coordination where direct delivery remains a substantial responsibility, while checking the documentation load. His next step is to compare another setting and organize a small permitted student activity from planning through follow-up. The shadow has not established that coordination is right or wrong for him. It has identified an assumption, supplied a more detailed picture, and produced a better experiment.

A job-shadowing worksheet you can reuse

Prepare a page with these fields: learning question; host role and setting; activities observed; activities discussed but not observed; working conditions; your reactions; missing evidence; and next action. Keep the record compact enough to complete shortly after the visit. A detailed diary is less useful if you cannot distinguish the facts that matter to your choice.

For each activity, write an action and an output: “checked a schedule to identify a conflict,” rather than “did planning.” Add what preceded the task and who used the result. Under conditions, note pace, interaction, location, supervision, and interruptions only where you have actual evidence. Mark your confidence as limited when the observation is brief or the host says the day was unusual.

For your reactions, separate three questions: Was I curious? Would I want to practice this? Could I tolerate the accompanying conditions? Watching an expert can be engaging even when the task would not suit you repeatedly. Conversely, unfamiliar terminology can make appealing work look inaccessible. A reaction is useful evidence about your experience today, not a permanent capability verdict.

End by writing one expectation that was supported, one that was challenged, and one still untested. For example: “I expected frequent teamwork and observed it; I expected mostly public-facing work and saw substantial preparation; I still do not know whether I enjoy doing the documentation myself.” This form turns a memorable visit into a usable research record and makes the next step specific.

Turn the visit into a proportionate next step

Send a brief thank-you that mentions something you learned and any agreed follow-up. Do not ask the host to review a large personal career plan unless that was explicitly offered. If they recommended a resource, use it before requesting further help. A thoughtful response shows that their time informed action without implying an ongoing mentoring obligation.

Review your notes alongside other evidence. A shadow can clarify work processes, while occupational sources help situate them and current job descriptions reveal employer-specific expectations. If the sources disagree, identify the likely reason before choosing a conclusion. A broad profile, a senior host, and an entry-level advertisement may describe different layers of the same field.

If access is limited, ask about alternatives: a walkthrough of a fictional case, a demonstration using public material, a discussion of an anonymized workflow, or a virtual observation that the organization already supports. These alternatives answer narrower questions, and you should label them accordingly. A recorded career video can introduce tasks, but it does not provide the same opportunity to ask why a decision occurred.

Choose a next action that matches the uncertainty. Observe another setting if the environment is unclear. Try a small practice task if your interest in doing the work is unclear. Check official requirements if access depends on credentials. Keep exploring when an important question remains, but avoid repeating visits simply to seek reassurance. A useful shadow ends with a clearer question or a better-supported action, even when the answer is to investigate a different role.

Sources and source roles

Sources and evidence limits

1. University of Connecticut: Informational Interviewing & Job Shadowing. Definition and preparation for job shadowing.
2. O*NET OnLine: Details Report Help. Separation of occupational task information and work context.
3. Yale Office of Career Strategy: Informational Interviewing. Questions about daily work and workplace conditions.

Research and official resources support the concepts identified beside each source. The worked examples and suggested exercises are educational illustrations, not validated prediction rules. Citing a framework does not establish the validity of a LifeByLogic assessment or predict an individual career outcome.