A learning plan template should connect one chosen skill gap to a practice artifact, a useful reviewer question and a next attempt. Keep planned work, observed evidence and illustrative examples separate so a guided rewrite cannot become an invented claim of mastery.
This original LP01 packet uses fictional handoff writing. Use it to prepare a learner-owned DOCX plan with a separate example/key and blank personal record, not an employee evaluation, credential or completed learning outcome.
Choose a goal with visible evidence
Princeton HR's learning-plan page links goals and development areas to practice, experience, feedback and revisited reflection. Use those structural concepts without copying its examples or treating its benefit statements as guaranteed outcomes. The page's template area contains a draft placeholder; this article does not claim to have downloaded a finished template. Princeton HR: Create Your Learning Plan
For fictional LP01, the goal is Write a client handoff that states the deliverable, due date and unresolved dependency. A real learner's chosen need, strengths and baseline reference remain fields to supply; this example does not establish that learner's ability.
Use three original presence criteria:
| Criterion | What the handoff must state | Evidence to retain |
|---|---|---|
| C1 | Named deliverable | Artifact named from the supplied brief |
| C2 | Exact due date | Date traced to the brief |
| C3 | Unresolved dependency, or confirmed none | Dependency/status traced to supplied evidence |
These are local practice criteria, not a complete client-scope standard. Presence does not establish clarity for every reader, correctness of the underlying brief, approval or quality. Confirmed none cannot be inferred from a blank dependency field.
Keep the baseline attached to its source
The fictional baseline B1 is Send the draft soon. It does not name the required artifact, give an exact date or state the dependency/status.
Treat B1 as an illustrative writing sample. Do not record that an actual learner produced it or failed an assessment. A real baseline requires the learner's own artifact and its source/context.
For the original practice brief, use:
| Brief ID | Supplied fictional requirement |
|---|---|
| R1 | Deliverable: two-page event outline |
| R2 | Due date: October 23, 2026 |
| R3 | Room capacity is unconfirmed |
Nothing here identifies an actual client, approved event, capacity owner, confirmation date or full scope. The plan uses those three supplied facts to make the writing task inspectable.
Make the first rewrite traceable
Fictional H1 reads: Deliver the two-page event outline by October 23, 2026; room capacity is not confirmed.
| Presence check | B1 | H1 | Source for H1 |
|---|---|---|---|
| C1 named deliverable | Missing | Present | R1 |
| C2 exact due date | Missing | Present | R2 |
| C3 dependency/status | Missing | Present | R3 |
H1 satisfies three presence checks. That count does not establish skill transfer, actual approval or a complete event handoff. It is a worked example derived from a supplied brief.
Retain B1, H1 and R1–R3 together. Otherwise the comparison can appear to show a person's improvement when it only shows that the article supplied a better illustrative sentence.
Plan practice that produces an artifact
| Original planned action | Resource/input | Expected evidence | Actual completion field |
|---|---|---|---|
| P1: Read current supplied handoff guidance | Learner's own guidance reference/version, TO CONFIRM | Note of applicable expectations | Blank |
| P2: Rewrite the original practice brief | R1–R3 | Learner's H1 attempt | Blank |
| P3: Request review of the starting information | Reviewer/question fields | Actual response with date/source | Blank |
| P4: Revise, then try a different brief | Received feedback, then independently supplied material | H2 revision and H3 transfer attempt | Blank |
The example H1 is not the learner's actual P2 result. Keep the supplied model separate from the blank practice-artifact field. Time spent reading and resource completion can be noted as activities, but neither substitutes for the handoff evidence.
Leave the reviewer and review date unassigned until supplied. A planned question can be specific without claiming anyone has answered it: What would you need to start the room layout?
Distinguish mock feedback from a received response
The actual feedback area remains blank. For teaching the revision step only, use clearly labeled Mock feedback F1: Who will confirm room capacity, and when?
An original illustrative H2 can retain H1 and add: Capacity owner and confirmation date: TO CONFIRM.
H2 keeps the deliverable, due date and unresolved capacity. It exposes an additional information gap without inventing a person, date or resolution. It does not claim the reviewer responded, approved the handoff or accepted responsibility.
Store actual feedback with its artifact reference and date when it arrives. Then record what changed in the next attempt and why. Do not copy F1 into the actual response field or record P3 Complete because the prompt includes a reviewer question.
If actual feedback requests information not supplied by the brief, the learning response can be to identify that gap. A polished sentence that guesses the missing owner would change the evidence, not solve the writing task.
Require another brief before claiming transfer
H3 is the next independent attempt on a different brief. Leave both its source material and the learner's actual answer blank until supplied. Reusing H1 with the same three facts cannot demonstrate independent application to a new task.
At review, compare the new artifact against the goal and supplied inputs. Record what the learner could do independently, what needed prompting and what information was unavailable. Any reviewer confirmation remains actual evidence to obtain, not a prefilled success status.
The review decision can be Continue practice, revise the next task, or request missing evidence, as supported by the actual record. It does not need to be Goal achieved merely because H2 follows a model or a course attendance box is checked.
Keep the plan and example key in separate areas
The native plan should retain chosen need, baseline reference, goal, criteria, action/resource, practice artifact, reviewer question, actual feedback, next attempt and review date. Give each area a clear Planned/Observed/Mock label where applicable.
LP01's example/key contains B1, R1–R3, H1, F1 and H2. The personal record contains blank baseline, actual attempts, received feedback and independent H3. This separation lets the reader copy a usable plan without accidentally adopting fictional outcomes.
The HTML overview uses phase sections to show the goal/evidence/practice/revision relationship. They do not grade writing, send reviewer requests, record LMS completion or save learning activity. Actual layout, accessibility and native printing remain unverified.
Copy this prompt to prepare the native plan
Create one complete, self-contained US-English HTML companion for “A learning plan for clearer handoffs”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for First rewrite; Apply mock feedback; Select text. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Write a complete original US-English learner-owned learning plan in editable DOCX content, with a separate fictional example/key and blank personal record. Reference https://hr.princeton.edu/create-your-learning-plan for goals, development need, practice/feedback and revisited reflection only. No copied examples, benefit guarantee, downloaded-template availability, employee evaluation, credentials, compliance or automatic mastery/grading.
Fictional LP01 goal: write a client handoff naming deliverable, exact due date and unresolved dependency or confirmed none. C1/C2/C3 are local presence criteria, not full quality/client-scope/approval standards. B1 “Send the draft soon.” lacks the three criteria; it is an invented baseline, not actual learner evidence.
Original brief R1 two-page event outline; R2 due October 23, 2026; R3 room capacity unconfirmed. H1 “Deliver the two-page event outline by October 23, 2026; room capacity is not confirmed.” traces C1/R1, C2/R2, C3/R3. Three presence checks do not prove quality, approval, completed event scope or skill transfer.
Planned P1 read learner's current supplied handoff guidance with source/version TO CONFIRM; P2 rewrite R1–R3 into actual attempt; P3 ask a reviewer “What would you need to start the room layout?”; P4 apply actual feedback to H2, then try a different independently supplied brief as H3. Actual resource completion, reviewer identity/date/response and learner artifacts remain blank. Attendance/time spent do not establish goal achievement.
Separate teaching-only Mock feedback F1: “Who will confirm room capacity, and when?” Illustrative H2 retains H1 and adds “Capacity owner and confirmation date: TO CONFIRM.” Never invent owner/date, resolve capacity, claim received response or approval. Keep mock/example artifacts separate from actual feedback.
Independent H3 material and answer remain blank until supplied; guided revision alone does not establish transfer. Review decisions depend on actual artifacts/feedback and may request evidence or change next practice, not automatically mark success. Preserve fields: chosen need/baseline reference/goal/criteria/action/resource/practice artifact/reviewer question/actual feedback/next attempt/review date, with Planned/Observed/Mock distinctions.
Native plan and example key first. Optional later read-only HTML phase/comparison overview may use useful disclosures, no Send/Approve/grade/LMS/reminder/storage buttons. Actual DOCX pagination/print, article width/360 px and hosted/navigation/accessibility need checks; no native file, HTML or captured outcome built claim. Provide complete plan/key/blank-record content and meaningful review criteria.
No saved learning activity, private workflow, export, reminders, automated grading or automatic source updates without evidence.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# Learning Plan Template: Connect Practice to the Next Independent Attempt
You finish a course and mark the goal complete, but the next client handoff still says Send the draft soon. Attendance shows that a resource was used. It does not show whether the writer can identify the deliverable, due date and unresolved dependency when someone else needs to begin work.
A learning plan template should connect one chosen skill gap to a practice artifact, a useful reviewer question and a next attempt. Keep planned work, observed evidence and illustrative examples separate so a guided rewrite cannot become an invented claim of mastery.
This original LP01 packet uses fictional handoff writing. Use it to prepare a learner-owned DOCX plan with a separate example/key and blank personal record, not an employee evaluation, credential or completed learning outcome.
## Choose a goal with visible evidence
Princeton HR's learning-plan page links goals and development areas to practice, experience, feedback and revisited reflection. Use those structural concepts without copying its examples or treating its benefit statements as guaranteed outcomes. The page's template area contains a draft placeholder; this article does not claim to have downloaded a finished template. [Princeton HR: Create Your Learning Plan](https://hr.princeton.edu/create-your-learning-plan)
For fictional LP01, the goal is Write a client handoff that states the deliverable, due date and unresolved dependency. A real learner's chosen need, strengths and baseline reference remain fields to supply; this example does not establish that learner's ability.
Use three original presence criteria:
| Criterion | What the handoff must state | Evidence to retain |
|---|---|---|
| C1 | Named deliverable | Artifact named from the supplied brief |
| C2 | Exact due date | Date traced to the brief |
| C3 | Unresolved dependency, or confirmed none | Dependency/status traced to supplied evidence |
These are local practice criteria, not a complete client-scope standard. Presence does not establish clarity for every reader, correctness of the underlying brief, approval or quality. Confirmed none cannot be inferred from a blank dependency field.
## Keep the baseline attached to its source
The fictional baseline B1 is Send the draft soon. It does not name the required artifact, give an exact date or state the dependency/status.
Treat B1 as an illustrative writing sample. Do not record that an actual learner produced it or failed an assessment. A real baseline requires the learner's own artifact and its source/context.
For the original practice brief, use:
| Brief ID | Supplied fictional requirement |
|---|---|
| R1 | Deliverable: two-page event outline |
| R2 | Due date: October 23, 2026 |
| R3 | Room capacity is unconfirmed |
Nothing here identifies an actual client, approved event, capacity owner, confirmation date or full scope. The plan uses those three supplied facts to make the writing task inspectable.
## Make the first rewrite traceable
Fictional H1 reads: Deliver the two-page event outline by October 23, 2026; room capacity is not confirmed.
| Presence check | B1 | H1 | Source for H1 |
|---|---|---|---|
| C1 named deliverable | Missing | Present | R1 |
| C2 exact due date | Missing | Present | R2 |
| C3 dependency/status | Missing | Present | R3 |
H1 satisfies three presence checks. That count does not establish skill transfer, actual approval or a complete event handoff. It is a worked example derived from a supplied brief.
Retain B1, H1 and R1–R3 together. Otherwise the comparison can appear to show a person's improvement when it only shows that the article supplied a better illustrative sentence.
## Plan practice that produces an artifact
| Original planned action | Resource/input | Expected evidence | Actual completion field |
|---|---|---|---|
| P1: Read current supplied handoff guidance | Learner's own guidance reference/version, TO CONFIRM | Note of applicable expectations | Blank |
| P2: Rewrite the original practice brief | R1–R3 | Learner's H1 attempt | Blank |
| P3: Request review of the starting information | Reviewer/question fields | Actual response with date/source | Blank |
| P4: Revise, then try a different brief | Received feedback, then independently supplied material | H2 revision and H3 transfer attempt | Blank |
The example H1 is not the learner's actual P2 result. Keep the supplied model separate from the blank practice-artifact field. Time spent reading and resource completion can be noted as activities, but neither substitutes for the handoff evidence.
Leave the reviewer and review date unassigned until supplied. A planned question can be specific without claiming anyone has answered it: What would you need to start the room layout?
## Distinguish mock feedback from a received response
The actual feedback area remains blank. For teaching the revision step only, use clearly labeled Mock feedback F1: Who will confirm room capacity, and when?
An original illustrative H2 can retain H1 and add: Capacity owner and confirmation date: TO CONFIRM.
H2 keeps the deliverable, due date and unresolved capacity. It exposes an additional information gap without inventing a person, date or resolution. It does not claim the reviewer responded, approved the handoff or accepted responsibility.
Store actual feedback with its artifact reference and date when it arrives. Then record what changed in the next attempt and why. Do not copy F1 into the actual response field or record P3 Complete because the prompt includes a reviewer question.
If actual feedback requests information not supplied by the brief, the learning response can be to identify that gap. A polished sentence that guesses the missing owner would change the evidence, not solve the writing task.
## Require another brief before claiming transfer
H3 is the next independent attempt on a different brief. Leave both its source material and the learner's actual answer blank until supplied. Reusing H1 with the same three facts cannot demonstrate independent application to a new task.
At review, compare the new artifact against the goal and supplied inputs. Record what the learner could do independently, what needed prompting and what information was unavailable. Any reviewer confirmation remains actual evidence to obtain, not a prefilled success status.
The review decision can be Continue practice, revise the next task, or request missing evidence, as supported by the actual record. It does not need to be Goal achieved merely because H2 follows a model or a course attendance box is checked.
## Keep the plan and example key in separate areas
The native plan should retain chosen need, baseline reference, goal, criteria, action/resource, practice artifact, reviewer question, actual feedback, next attempt and review date. Give each area a clear Planned/Observed/Mock label where applicable.
LP01's example/key contains B1, R1–R3, H1, F1 and H2. The personal record contains blank baseline, actual attempts, received feedback and independent H3. This separation lets the reader copy a usable plan without accidentally adopting fictional outcomes.
The HTML overview uses phase sections to show the goal/evidence/practice/revision relationship. They do not grade writing, send reviewer requests, record LMS completion or save learning activity. Actual layout, accessibility and native printing remain unverified.
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Review: an overview of the practice and evidence
Maintain the learner-owned DOCX plan and actual practice/feedback artifacts separately from LP01's fictional key. Use the companion to place the goal, presence criteria and next-attempt evidence together.
Verify actual phase navigation, disclosures, layout and hosted behavior before presenting a working example. The overview does not supply a reviewer response or turn a model sentence into demonstrated skill.
The useful plan tells the learner what to try next and what actual artifact would make the next review informative.