Another Check-In · S01
Field work plans
35 minutes. · 10 slides
Lesson video coming soon. The player below contains a sample video, not this lesson. You can use the written lesson and slide guide now.
Work through the lesson
Use these explanations alongside the slide guide. Expand any section to read its full explanation.
Before the demonstration
- Your assigned responsibility
- The correct training record
- Evidence of the result
Today’s outcome
A submitted plan and pending change request are identifiable without claiming approval.
Read the full explanation
Before we begin, check these prerequisites: C01; first linked staff ID correct; training locations and dates. The intended outcome is: A submitted plan and pending change request are identifiable without claiming approval. Keep a note of the training identity and date so that you can recognize the result. We will pause before any action that your role or the exercise does not authorize.
A draft period
- Open Work > My Itinerary and create a dated draft period with a title
In this step
Start with the dates and purpose of the planned work. A draft gives you time to check the plan before requesting review. It does not authorize the proposed trip or imply that a reviewer has seen it.
Read the full explanation
Open Work > My Itinerary and create a dated draft period with a title. Start with the dates and purpose of the planned work. A draft gives you time to check the plan before requesting review. It does not authorize the proposed trip or imply that a reviewer has seen it. I will pause here so you can identify the control or result that tells us where we are in the workflow.
A planned stop
- Add a stop with date, arrival/departure, sequence, expected location and purpose
- departure must follow arrival
In this step
Check the stop date, sequence and expected arrival and departure. Departure must follow arrival. The expected location and purpose help the reviewer judge whether the plan describes the intended work.
Read the full explanation
Add a stop with date, arrival/departure, sequence, expected location and purpose; departure must follow arrival. Check the stop date, sequence and expected arrival and departure. Departure must follow arrival. The expected location and purpose help the reviewer judge whether the plan describes the intended work. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Location proposals
- If needed create a private location proposal with valid pin/radius, inspect its status and duplicate suggestions
In this step
A private proposal lets you describe a place that is not yet in the shared location list. Check its pin and radius and review possible duplicates. Proposing a place does not automatically make it an approved master location.
Read the full explanation
If needed create a private location proposal with valid pin/radius, inspect its status and duplicate suggestions. A private proposal lets you describe a place that is not yet in the shared location list. Check its pin and radius and review possible duplicates. Proposing a place does not automatically make it an approved master location. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Submission and review
- Submit the nonempty period and confirm awaiting review
- approved/rejected records are locked and returned records can be revised
In this step
Submit only when the period contains the required stops. Read the resulting state. Returned work can be revised, while approved or rejected records have different editing restrictions. A submission confirmation is not an approval.
Read the full explanation
Submit the nonempty period and confirm awaiting review; approved/rejected records are locked and returned records can be revised. Submit only when the period contains the required stops. Read the resulting state. Returned work can be revised, while approved or rejected records have different editing restrictions. A submission confirmation is not an approval. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Changes to approved work
- For a changed approved assignment, use Itinerary Changes, select the relevant entry and request a reasoned deviation
- await a reviewer
In this step
Explain the requested deviation and select the affected entry. Keep the approved plan as the reference until an authorized reviewer decides the change. A changed operational need should leave a visible request and decision history.
Read the full explanation
For a changed approved assignment, use Itinerary Changes, select the relevant entry and request a reasoned deviation; await a reviewer. Explain the requested deviation and select the affected entry. Keep the approved plan as the reference until an authorized reviewer decides the change. A changed operational need should leave a visible request and decision history. I will pause here so you can identify the control or result that tells us where we are in the workflow.
Common problems
- Assuming a private proposal is an organization location
- submitting an empty period
- choosing a wrong first linked staff ID
- treating a request as approval
A useful support report
The task and record
The expected result
The actual message
The authorized next step
Read the full explanation
Let us consider the mistakes that can disrupt this workflow. Assuming a private proposal is an organization location; submitting an empty period; choosing a wrong first linked staff ID; treating a request as approval. Describe what you expected and what the application actually showed before choosing a remedy. Preserve the relevant record and error. The role responsible for a review or configuration change should make that decision. Do not borrow broader access simply to finish the exercise.
Guided practice
- Create a two-stop training itinerary, submit it and request a change to a separate prepared approved stop
- Explain the difference between draft, submitted and approved
Evidence to show
The correct training case
The result or permitted decision
Your explanation of the next step
Read the full explanation
Now it is your turn. Create a two-stop training itinerary, submit it and request a change to a separate prepared approved stop. Explain the difference between draft, submitted and approved. Work within the assigned training role. When you finish, show the result and explain which identity and date it belongs to. If the exercise includes a restricted action, explain the decision and its authorized owner rather than carrying it out without approval.
Practice debrief
- Correct context and permitted action
- A result you can trace
- A clear next step if blocked
Expected result
A submitted plan and pending change request are identifiable without claiming approval.
Read the full explanation
The expected outcome is: A submitted plan and pending change request are identifiable without claiming approval. Walk me through the record you used and the result you found. Explain these workflow checkpoints in order: Open Work > My Itinerary and create a dated draft period with a title. Add a stop with date, arrival/departure, sequence, expected location and purpose; departure must follow arrival. If needed create a private location proposal with valid pin/radius, inspect its status and duplicate suggestions. Submit the nonempty period and confirm awaiting review; approved/rejected records are locked and returned records can be revised. For a changed approved assignment, use Itinerary Changes, select the relevant entry and request a reasoned deviation; await a reviewer. For an exception, name the evidence you would preserve and the person with authority to take the next action.