When Daniel Reed, Plan@Job's AI Operations Manager, drafts a quote follow-up or nudges a client about a proposed start date, that message waits in an approval queue rather than going out on its own. Reviewing it properly before you approve is what makes an AI approval workflow useful rather than risky - it is the difference between a colleague who saves you a chasing phone call and one who quietly sends something you never actually agreed to. Here is what to check, in what order, and when to edit rather than simply wave a draft through.
What Daniel Reed actually drafts
As the operator - the contractor business managing the client relationship, project delivery, subcontractors and any in-house operatives - you are the one accountable for what leaves your business, even when an AI colleague wrote the first draft. Daniel supports three things: quote follow-ups (chasing a client who has gone quiet after a quote), proposed-date follow-ups (confirming or nudging a proposed start date), and eligible sharing of jobs with your existing vetted subcontractor network. He also compiles a morning brief so you can see what is queued and what has moved without digging through every job.
It helps to know what Daniel does not do. He does not set or change a price, award work, move money, or promise an outcome on his own initiative - those stay fixed workflows that need a person's decision. He is also a different colleague from Sophie Bennett, the AI Enquiries Coordinator, who checks existing job briefs for missing information and chases clarification (with a two-attempt handoff before it lands back with you), and from Ask Plan@Job, which only acts when you are the one driving the conversation. If you are looking for how missing job details get chased, that is Sophie's queue, not Daniel's.
Where the review actually sits
Drafted follow-ups queue for approval rather than sending automatically, which matters most for first contact with a new client - that step normally needs a person's sign-off. Quote and date follow-ups to a client you already have an open job with move through the same queue, so you see the exact wording before anything reaches an inbox. If more than one person in your business needs to see this queue - an office manager covering while you are on site, for instance - set that access up through your Plan@Job account rather than sharing a login.
What to check before you approve
Run through these five checks before you tap approve, not just when something looks off:
- Does the price match what was actually agreed? Daniel references the quote already on file - he does not recalculate or round it. If the figure in the draft does not match the agreed quote, something upstream has drifted and needs fixing before the message goes anywhere.
- Is the date still real? A proposed-date follow-up is only as good as the stage dates in your project plan. If a trade has slipped or materials are delayed, confirming the old date in writing creates a problem you will have to walk back later.
- Is this the right client and the right job? A quick name and job reference check catches the rare mismatch before it becomes an awkward call.
- Does it read like your business? The tone should sound like something you would actually send, not a generic template. Edit anything that reads stiff or oddly formal for how you talk to that client.
- Is it a genuine follow-up, not an unintended commitment? Watch for phrasing that tips from "checking in" into "we can definitely start Monday" - Daniel is not meant to guarantee outcomes, but wording can still land firmer than intended, and that is exactly what your review is for.
For subcontractor sharing, add a sixth check: is this job genuinely eligible to share with your vetted network - right trade, right region, right scope - and is the subcontractor it is proposing to reach actually one you have vetted for that kind of work, not simply the next name in the list.
Approve, edit, or pick up the phone
Every drafted follow-up ends in one of three places:
- Approve as-is, when the draft is accurate and reads naturally. This is the fast path and should be most of them once your job briefs and project plan are kept current.
- Edit and send, when the substance is right but a date, figure, or line of wording needs fixing. This is quicker than rejecting and rewriting from scratch, and it is the most common outcome when a stage date has moved since the brief was set.
- Reject and call instead, when the relationship is sensitive, there is an unresolved dispute, or this is first contact with a client you have not dealt with before. Some conversations genuinely need your voice, not a written nudge.
Illustrative example: say a bathroom refit job has a quote follow-up queued for a client who went quiet ten days ago. The project plan shows the strip-out stage has already slipped a week because of an access issue with the building's managing agent. Approving the draft as written would confirm a date that is no longer true. Editing it to reference the revised date, or rejecting it in favour of a call to explain the access delay directly, are both better calls than approving on autopilot.
Building a habit that scales with your business
The approval queue only earns its keep if it gets checked regularly, not batched up once a week. A few things that make this stick:
- Review the queue at a set point each day - alongside the morning brief is a natural moment, since you are already looking at what has moved across your jobs.
- Name one person per job as the reviewer, even if several people in your business can technically see the queue, so nobody assumes someone else already checked it.
- Keep job briefs and project plan stage dates current. Most of the edits above trace back to a plan that has drifted from what is actually happening on site - fix that at the source and Daniel's drafts get more accurate on their own.
- If you manage subcontractors and want to compare notes on how other contractor businesses are handling AI-assisted client communication, the Contractor Club community is worth a look - it is a space for UK contractors trading practical advice, Plan@Job's own included.
None of this needs to be a large time cost. A handful of drafts reviewed properly each morning is a small habit that keeps client communication accurate and keeps the decision that matters - what actually gets said to a client - with you.
If you want the fuller picture of what each AI colleague does and does not do, Plan@Job's AI staff page covers Daniel Reed, Sophie Bennett and Maya Collins together, including what always needs your approval. If you are not yet running your jobs on Plan@Job, you can see how operators use the platform or set up your account to start building project plans with stages, scope and costs that keep these follow-ups grounded in something current, as covered on the project management page.
FAQ
Does Daniel Reed ever send a follow-up without my approval?
First contact with a new client normally needs a person's approval, and drafted quote and proposed-date follow-ups sit in your approval queue rather than sending on their own. Daniel does not award work, set prices, move money, or guarantee an outcome unsupervised - those decisions stay with you.
Can I edit the wording before it goes out?
Yes. Editing a draft before sending is the normal and often quickest path - it is faster than rejecting and starting again, and it is exactly how small drift between the draft and the current job (a slipped date, for instance) gets corrected before a client ever sees it.
What happens if I do not review the queue for a few days?
Drafts wait for a decision rather than expiring into an automatic send, but a backlog of unreviewed follow-ups means quotes go unchased and clients hear nothing when they might be expecting an update. Reviewing daily, even briefly alongside your morning brief, keeps the queue from becoming a second inbox you dread opening.