Running several jobs means keeping track of who has the brief, who has returned a price and who still needs to suggest a start date. Daniel Reed, the AI Operations Manager in Plan@Job, supports those follow-ups within the operator's configured workflows.
The operator is the contractor business managing delivery. Daniel works inside that account; he is not a separate company supplying the project or a person taking responsibility for the site.
Four parts of the operations role
Daniel can support eligible job-sharing with matching vetted subcontractors in the operator's existing network. He can follow up on an outstanding quote, ask an awarded subcontractor for proposed dates and provide a morning summary of work needing attention.
Each action has conditions. A job's status and age, existing assignments, matching information, contact eligibility and account settings can affect whether it proceeds. A new job does not automatically mean a message will be sent to everyone in the network.
Sharing work needs the right scope
The sharing workflow is intended to put an eligible brief in front of appropriate people. That includes checking the relevant network relationship and matching information. It should not create a new commercial commitment or bypass the operator's supervision settings.
Projects split into stages need the appropriate stage workflow. Do not assume a whole-job sharing action will make separate trade decisions for a multi-stage project. The operator still organises the scope and decides how the work should be packaged.
Follow up on a price, then make the decision
In an illustrative example, a subcontractor has received a brief but has not returned a quote. When the follow-up conditions are met, Daniel can send a reminder. If a price comes back, the authorised person reviews it and makes the award decision.
Daniel does not accept a price or award the work on his own. An activity marked proposed is awaiting a decision; a failed action is not a completed follow-up. Use the activity history to distinguish those outcomes.
Proposed dates are not confirmed bookings
After award, asking which dates a subcontractor could start is a coordination step. It does not mean the client has agreed, the payment conditions are satisfied or the booking is confirmed.
Keeping that distinction clear protects the plan. The operator reviews proposed dates, satisfies the relevant requirements and confirms the commitment through the supported workflow.
Set up and supervise Daniel
Open AI staff in your operator account, choose Daniel and appoint the supervisor. Review autonomy, quiet hours and the available operating limits. Writing instructions can shape the wording of routine follow-ups but cannot grant extra permissions.
After configuration, review the action history. Start by checking whether matching, sharing and follow-up actions are useful on your actual job types. Resolve missing prerequisites rather than repeatedly attempting the same action without understanding the cause.
Common questions
Does Daniel find unlimited new subcontractors?
This role's matching uses the operator's existing eligible network. Separate sourcing or recruitment workflows should not be confused with this capability.
Can Daniel promise a date or accept a price?
No. The operator retains the commercial and booking decisions.
How should I judge whether it helps?
Look at useful returned prices, clearer proposed dates and fewer unresolved follow-ups, alongside failures and required human edits. No fixed time-saving or staffing-replacement claim is implied.
Explore Daniel's role and settings, or see how project stages organise the delivery.