Employee Job Shadowing Plan: Template and Checklist

An employee job shadowing plan should name the learning goal, host, work to observe, time and format, boundaries, and follow-up. Agree these before reserving a shared office day, then close the session with the employee explaining what they learned.

Use the plan below for an employee observing a colleague inside the organisation. It includes a copyable session brief, host checklist, suggested 90-minute agenda, request message, and reflection record. You can use it for a new starter or an established employee exploring another team’s work.

Decide what the employee needs to observe

The Australian Government’s staff development guidance describes job shadowing as learning a role or skills by observing another staff member. In this plan, turn that broad idea into one question and one observable piece of work.

Start with a question that real work can answer. “Understand the operations team” is too broad for one session. “See how an incomplete event request becomes a confirmed room plan” gives the host something specific to show.

Agree whether the session is observation, explanation, or supervised practice. LSE’s staff shadowing guidance distinguishes observation, focused briefings over time, and hands-on activity. Those are different commitments, so state the chosen mode in the invitation.

This template defaults to observation with questions. Watching a task does not establish that the employee can perform it independently. If the goal is to take over the work, arrange appropriate practice and a separate readiness check. If the goal is an ongoing development relationship, use a hybrid mentoring brief alongside, or after, the observation session.

Choose the work first, then the place and time

Ask the host when the relevant activity will actually happen. A shared Tuesday is useful only if the employee can observe the work they came to understand. Confirm the activity and a question window before treating an office-day match as a booking.

• In person: choose this when movement through the workplace, physical equipment, or interaction between people is central to the learning question. Agree where the observer can sit or stand without interrupting the work.
• Remote: choose this when the useful activity can be explained through a permitted shared document, screen, or conversation. Test what the observer will see and hear, and close unrelated material before sharing.
• Split format: use a short remote introduction, an onsite observation, and a later reflection when that fits the activity. Put each part in the plan rather than leaving the follow-up implied.

For a remote observer joining a room, use the hybrid meeting checklist to check participation. Build in a way to pause or ask a question without competing with the room conversation.

Copyable employee job shadowing plan template

Copy these fields into a shared document. The employee and host should complete it together, with any manager or organiser who needs to agree the time. A brief answer in each field is enough.

Purpose and session

1. Employee and host: [names, teams, and contact route]. Organiser, if different: [name].
2. Learning question: [one question the employee should be able to answer afterwards].
3. Work to observe: [specific activity, stage, or decision]. Why this activity answers the question: [reason].
4. Mode and participation: [observe / explanation / supervised practice]. The employee may [actions]; the host retains responsibility for [work].
5. Date, time, and format: [start, finish, time zone, office location or call link]. Time agreed with: [relevant people].
6. Session sequence: [introduction, observation, question window, reflection]. If a live task runs long, protect [closing time or revised finish].

Access, changes, and follow-up

1. Preparation: employee reviews [approved material]; host prepares [task or example] and tells [affected colleagues].
2. Access and boundaries: [workspace, document or call access]. Excluded activities or information: [items]. Notes or recording arrangements: [what is permitted].
3. Participation needs: [what each person needs to see, hear, move around, or use the materials]. Agree the practical setup directly.
4. Change route: [who notifies whom, by which channel, and by when]. If the task disappears or access is unsuitable, [reschedule / use an approved example / cancel].
5. Learning check: employee will explain [process or decision] back to the host; host will correct [misunderstandings].
6. Follow-up: [one action, owner, and review date]. Store the learning note at [shared location]; keep excluded information out of it.

These fields are a suggested operating template, not a research instrument. Keep permissions tied to the actual work. Joining a shadowing session should not automatically grant wider system access or permission to record colleagues.

Host checklist before the session

The University of Leeds’ new-starter shadowing guide asks hosts to consider activity timing, seating, briefing colleagues, questions, and understanding. Use the checks below to turn those planning concerns into a concrete session.

• Confirm that the chosen activity is still happening and that the employee’s question matches it.
• Tell anyone whose work or meeting will be observed, and resolve participation arrangements before the session.
• Prepare only the material the employee is permitted to see. Choose a suitable example if live work cannot be observed.
• Make the chair, route, audio, and shared material usable for this particular observer.
• Identify a natural pause for questions. Explain when the employee should watch quietly and when to interrupt.
• Reserve the closing discussion. Do not let observation consume the entire session.
• Check the fallback with the employee. A cancelled task should trigger a decision about the session, not an unplanned afternoon of watching unrelated work.

A suggested 90-minute job shadowing agenda

Use this as a starting point for one focused activity. The timings are editorial suggestions, not evidence of an ideal session length. Shorten or split the session around the real task, breaks, workload, and the participants’ needs.

1. Minutes 0 to 10: set the context. Restate the learning question, explain the activity and boundaries, and identify what the employee should pay attention to.
2. Minutes 10 to 45: observe the work. The host explains key choices at suitable pauses. The employee records questions without copying restricted information or interrupting a sensitive interaction.
3. Minutes 45 to 55: pause and clarify. Check what was visible, answer questions, and decide whether the next activity still serves the learning goal. Use this as a break if needed.
4. Minutes 55 to 80: examine one decision. Walk through an approved example or continue the relevant work. Ask what information changed the host’s next step and what would have changed the decision.
5. Minutes 80 to 90: explain back and agree a next step. The employee describes the process in their own words. The host corrects misunderstandings, then both choose one follow-up action.

If the activity cannot fit, observe a meaningful part of it rather than rushing through a whole role. A later short conversation can cover the outcome, with the revised time agreed explicitly.

Job shadowing request message template

Hi [host], I would like to understand [specific question] so I can [work or development purpose]. Would it be possible to observe [activity] and ask questions at a suitable pause?

I suggest [duration and format], subject to your workload and the activity’s timing. I can make [two options], and I have discussed the time with [manager, if relevant]. I am proposing observation only. Please let me know what preparation, boundaries, or alternative timing would make it workable.

After the host agrees, send the completed plan with the confirmed location or call link. A positive reply to an exploratory message is not enough to settle access, timing, or which work the employee may observe.

Worked example: follow one request across teams

This is a fictional planning example. An employee who organises team sessions wants to understand why workplace requests sometimes come back for clarification. The learning question is: “What information does the coordinator need before confirming a room setup?”

The host chooses an approved, completed request with identifying details removed. They agree a 90-minute office session to walk through the brief and inspect the relevant room. The plan excludes live requests containing information the employee should not see. Both confirm the session time separately from their usual office days.

During the walkthrough, the employee observes how the host checks the requested activity against the room and equipment. In the closing discussion, the employee explains the information they would include in their next request. The host corrects one misunderstanding about who confirms the final setup.

The follow-up is small: the employee revises their own request brief and asks the host to check the next suitable example. The learning result is a clearer account of the workflow. It does not certify the employee to operate equipment or independently approve bookings.

Copyable reflection record

Complete this while the session is still fresh. Share a short version with the host so they can correct the explanation. The prompts below are a suggested format; keep the note focused on learning rather than a transcript of the host’s work.

• Question: [what I wanted to understand].
• Observed sequence: [what happened, in order, without restricted details].
• Decision: [one choice the host made and the information behind it].
• Correction or uncertainty: [what the host clarified, or what I still need to ask].
• Application: [one thing I will change, explore, or practise in my own work].
• Next step: [action, owner, and date]. A separate practice or training session is needed if [remaining skill need].

Review the answer against the original question. “I attended the session” records participation. “I can explain which details the coordinator checks before confirming a setup” gives the host something specific to confirm or correct. Avoid treating a completed reflection as a performance rating.

When the plan changes

• The host changes office day: confirm whether the activity can move online and still answer the question. If its physical context matters, agree a new onsite time.
• The relevant task is cancelled: use an approved past example only if it serves the same goal. Otherwise reschedule instead of filling the time.
• Part of the work becomes unsuitable to observe: pause the observation. The host can explain the process at an appropriate level or choose another example.
• The employee needs more practice: record a separate next step with the responsible person. Do not silently turn an observation session into task ownership.

Coordinate the shared office time

When the activity benefits from being together, use the office-day planning worksheet to find a workable overlap. Confirm the host’s availability and the work itself before anyone plans a trip specifically for the session.

Officedays in Slack helps colleagues share their planned office days and supports scheduled weekly prompts. Use that visibility to find a possible day, then confirm the shadowing session directly with the host.

Sources and methodology

Sources checked on 30 October 2026. This guide combines public institutional guidance with original editorial templates and a fictional example. It contains no survey findings or measured outcome claims. The suggested agenda is not a duration benchmark.

• London School of Economics and Political Science, staff shadowing guidance. No publication date displayed. Used for distinctions between observation, briefings, and supervised activity.
• Australian Government, Staff development and training. No publication date displayed. Used for the employee-observation definition and learning-goal context. No employment-law or measured-effectiveness claims are drawn from this page.
• University of Leeds, Job shadowing for new starters. No printed publication date. Used for planning considerations, not evidence of outcomes for established employees.