The short answer: yes. Ask alfred_, in the app or by text, “Draft a status update for Harbor Logistics from this week’s emails: what’s done, what’s next, and what we’re waiting on from them.” It reads the week’s threads about the project, drafts the update in the client’s thread, and shows it to you. Edit it, and it sends only when you say send.
“Can you send us a quick update?”
You’re a project manager at a civil engineering firm. Harbor Logistics is expanding a distribution center: new loading docks, a widened truck court, revised stormwater. This week alone there were twenty threads: the surveyor’s revised topo, a back-and-forth with the city about the curb cut, the geotech’s boring logs, the client’s question about phasing, and your structural lead’s note that the dock pit detail is done.
Friday at 3, the client’s facilities director writes: “Can you send us a quick update on where things stand?” The facts are all there. Turning twenty threads into one clear paragraph is half an hour you don’t have before the weekend.
The native ways, and where they stop
Writing it from memory. Fast, and you’ll forget the thing the client cares most about.
Project management software. A good place for the schedule and tasks. Most of this week’s news came by email and never made it in.
Ask for the draft
- Connect the inbox and calendar you run the project from. Sign in with Google or Microsoft; your password stays with them.
- Ask, in the app or by text: “Draft a status update for Harbor Logistics’ dock expansion from this week’s emails: what’s done, what’s next, and what we’re waiting on from them. Reply in Pat’s thread.”
- Read the draft. Ask for changes (“shorter”, “leave out the curb cut until the city answers”), and say send when it’s right.
What the draft looks like
Re: Dock expansion, quick update?
Hi Pat,
Here’s where things stand this week. Done: the structural team finished the dock pit detail, and the surveyor delivered the revised topo on Tuesday. In progress: the geotech boring logs came in Thursday; we’re reviewing them against the truck court pavement design and expect recommendations by next Wednesday. Waiting on you: a decision on whether the north docks are built in phase 1 or phase 2, which affects the stormwater sizing. Waiting on the city: their response on the curb cut, which they’ve promised by the 31st.
Next update Friday.
Illustrative example, not output from a real run. The project, client and firms are invented.
Or every Friday
Make a routine: “Every Friday at 2, email me a draft status update for each of my active clients from this week’s emails.” It emails the drafts to you, not the clients. You send each one when it’s right. See Make your own.
The honest caveat
alfred_ writes from the emails and calendar you connect, so news that only came by phone, or lives only in project software, needs adding. Name the project the way your emails do. Read the draft like you’d read a junior engineer’s: alfred_ writes it, you’re the one who signs it. Nothing goes to the client until you say send. alfred_ is a paid product; plans are on the pricing page.
