# SkillBridge Weekly Check-In Format

Builds a weekly progress update for both your SkillBridge host supervisor and your command so everyone stays informed and on the same page. Use it each week of your internship to keep communication consistent and protect yourself if questions arise later.

## Prompt

## Context
You are helping [YOUR NAME], a service member in week [WEEK NUMBER] of a SkillBridge internship at [HOST ORGANIZATION], produce a weekly check-in update. Your military rank and occupational specialty: [RANK AND MOS/RATE/AFSC]. The role or department at the host organization: [HOST ROLE AND DEPARTMENT]. Your command point of contact: [COMMAND POC NAME AND TITLE]. This week's work activities: [THIS WEEK'S ACTIVITIES]. Any challenges or blockers encountered: [CHALLENGES OR BLOCKERS]. Goals for next week: [NEXT WEEK'S GOALS]. Hours worked this week: [HOURS WORKED].

## Task
Produce two short documents from the information above:

1. Host supervisor update (plain professional format): a one-page update that covers what was accomplished this week from [THIS WEEK'S ACTIVITIES], any challenges from [CHALLENGES OR BLOCKERS] and how you addressed them, and the plan for next week from [NEXT WEEK'S GOALS]. Written for a civilian supervisor in a professional workplace tone.

2. Command check-in message (concise, military-workplace appropriate): a brief message for [COMMAND POC NAME AND TITLE] covering that the internship is progressing, what type of work is being done, hours completed, and any issues that need command awareness. Written to inform, not to impress.

## Standards
- Both documents must reflect only the activities in [THIS WEEK'S ACTIVITIES]. Do not add accomplishments, projects, or outcomes not stated there.
- Do not include any classified information, operational details, or sensitive unit information in either document.
- Do not exaggerate scope or impact. These are working documents, not performance evaluations.
- The host update should use professional civilian language. Avoid military-specific acronyms unless you spell them out.
- The command update should be brief. Two to three short paragraphs at most.
- Hours must match [HOURS WORKED]. Do not round up or adjust.
- If [THIS WEEK'S ACTIVITIES] is too thin to write a useful update, ask for more detail before drafting.

## Variables

- YOUR NAME
- WEEK NUMBER
- HOST ORGANIZATION
- RANK AND MOS/RATE/AFSC
- HOST ROLE AND DEPARTMENT
- COMMAND POC NAME AND TITLE
- THIS WEEK'S ACTIVITIES
- CHALLENGES OR BLOCKERS
- NEXT WEEK'S GOALS
- HOURS WORKED

## Input checklist

- [ ] Write down what you actually worked on this week before running the prompt. Vague input produces vague updates.
- [ ] Confirm hours worked match what you will report officially. Do not adjust them here.
- [ ] Remove your Social Security number and personal data before pasting any record, and never paste classified or operationally sensitive details about your unit, mission, or equipment.
- [ ] Note any challenges honestly. A blocker reported early is easier to address than one that surfaces at the end of the program.
- [ ] Confirm the spelling and title of your command point of contact before sending the command update.

## Verification checklist

- [ ] Read the host update and confirm every accomplishment listed is something you actually did this week, not a future goal or past week's work.
- [ ] Check that no military acronym appears in the host update without being spelled out first.
- [ ] Confirm no classified details, unit designators, or operationally sensitive information appears in either document.
- [ ] Read the command update. Confirm it is informative and brief, not a performance narrative or a complaint.
- [ ] Confirm the hours in the update match what you are reporting through official channels.
- [ ] Check that the challenges section, if present, describes the situation accurately without assigning blame or making legal claims.

## Sample output

Sample output. Generated by AI from sample inputs:

--- HOST SUPERVISOR UPDATE ---
Week 4 Update: Marcus Hale, Logistics Operations Intern
Redstone Logistics Partners, Operations Planning Department

This week I completed the draft standard operating procedure for inbound shipment staging, incorporating feedback from the Tuesday walkthrough with the operations lead. I attended the carrier reconciliation meeting on Wednesday and took notes that the team used to update the tracking spreadsheet. I also completed the company's required safety orientation for warehouse access.

One challenge: I ran into a gap in the shipment data from a vendor portal I do not have full access to yet. I flagged it to you on Thursday. That access request is pending IT review.

Next week I plan to finalize the SOP draft, shadow the import team for the Thursday inbound cycle, and complete the required compliance module the team assigned during onboarding.

Hours this week: 40

---

--- COMMAND CHECK-IN ---
Subject: SkillBridge Week 4 Update, SSG Marcus Hale

Master Sergeant Chen,

Week 4 is complete. I am working in the operations planning department at Redstone Logistics Partners, focused on logistics coordination and standard operating procedure documentation. This week I completed 40 hours and have had no issues requiring command attention.

One minor access request is pending at the host site, which is being handled through their IT process. No action needed on your end.

I will check in again at the end of week 5. Let me know if you need anything from my end.

Respectfully,
SSG Marcus Hale

## Customization notes

Adjust the format of the command update to match your unit's communication norms. Some commands want a simple email; others use a form or a tracker. If your host supervisor prefers a verbal check-in, use the host update as notes to guide that conversation instead of sending it as a document. For longer SkillBridge programs, consider tracking cumulative hours in a separate log so the final report is easy to compile.

---

From The Military Transition & SkillBridge Library at vetslearn.com/libraries/transition