Draft created in the lab's draft area.\n\nTo: jess@fieldstonecreative.com\nSubject: Case Study Template - Status Check\n\nHi Jess,\n\nPer our agreement, the case study template and 2 populated examples were due by end of Week 4, which was this past Friday. I haven't seen anything come through yet and wanted to check in.\n\nCan you give me a specific status update by end of day tomorrow? If something's come up on your end, that's completely fine, I just need to know now so we can adjust the rest of the timeline if needed. We're still on track for the Week 5 final handoff on our side, but this piece is a dependency for that.\n\nLooking forward to hearing from you.\n\nPriya

Summary  
This chapter covers how to read an external agreement excerpt and use its specific commitments to generate a context-aware, professional follow-up message via a language model.

General domain of usage  
Vendor management communication

Still Priya on the Alderwood relaunch. Remember **Fieldstone Creative** — the outside design agency, where **Jess** is your designer? They signed an agreement (a **SOW**, or Statement of Work — the document that lists exactly what they'll deliver and when). One of their deliverables, the case study template, was due this week. It hasn't arrived, and Jess has gone quiet.
 
The first message you send now sets the tone for whether this gets fixed fast or turns into a bigger problem. In this chapter Claude drafts that message, using the actual agreement so it references real commitments, not a vague complaint.

Fieldstone's signed agreement (`fieldstone-agreement-excerpt.txt`) is in this chapter's file tree — open it from **Show File Tree** to see exactly what they committed to. This is what makes the chase-up message land: you're pointing to a specific promised date, not just saying "where is it?"

Note

>### Task
> 
> Ask Claude to read `fieldstone-agreement-excerpt.txt` and draft a firm-but-professional message to Jess about the missed deliverable, referencing what was actually agreed.
 >
>**Prompts to Try**
 >
>><b>Read fieldstone-agreement-excerpt.txt and draft a chase-up message to Jess at Fieldstone. The case study template was due this week per our agreement and we haven't heard anything. Firm but professional, and ask for a specific update by tomorrow.
 >
> Chasing your own vendor instead? Describe the situation and upload your agreement, then ask: 
>
>><b>Draft a chase-up message referencing what we agreed and asking for a specific update by [date].
> 
>**What you're aiming for:** a short draft that names the specific deliverable and its agreed date (from the SOW), asks for a status update by a specific time, and leaves room for a real reason without assuming bad faith — a first chase-up, not a final warning. It should end with one clear question that needs a real answer. When you have a message you'd actually feel comfortable sending, you're done. (The draft appears in the lab's draft area — you don't send anything real.)

Discover how to keep a real project from falling apart: turn a messy brief into an actual plan, catch budget and schedule problems before they bite, push back on scope creep, and keep your team coordinated under a hard deadline. You'll practice it all through a live website relaunch, with Claude helping you plan, defend, and coordinate the work end to end.

Get hands-on experience turning a scattered project brief into a task list, then checking that plan against a real calendar and a real budget before you commit to a deadline.
 

Discover how to defend a deadline against scope creep, find the task that's quietly stuck, and chase down a vendor who's gone quiet — before any of it becomes a crisis.

Master the skills needed to research the competitive landscape, update stakeholders clearly, track the whole team's progress in one place, and coordinate a final sprint under pressure.