Generate versus apply: two separate Alfie steps for a construction week plan

A planning suggestion and a changed live schedule are not the same thing. Alfie’s current action contract reflects that distinction. generate_week_plan prepares a proposal without side effects; apply_week_plan writes the chosen proposal and carries a higher risk level. Keeping those steps separate lets a construction manager inspect capacity, deadlines and conflicts before crews see a changed plan.

Define the planning window

Specify the week, projects and teams in scope. Confirm holidays, absences, site access and fixed appointments. A useful proposal needs boundaries; “plan next week” may include projects that should remain untouched.

State priorities and hard constraints separately from preferences. A contractual inspection is not equivalent to a preferred sequence.

Generate a proposal without changing records

The current generate_week_plan action uses planning read permission and is classified as preparation with no side effect. Alfie can assemble available context and return a proposal payload. This is the appropriate place to explore alternatives.

Treat the output as a draft. The model can organise information, but it cannot create missing crew capacity or verify an unrecorded client promise.

Review conflicts and practical feasibility

Check double bookings, travel, skills, equipment, delivery dates and task dependencies. Ask site leads whether the proposed sequence is workable. Review what is left unassigned, not only what fits neatly.

Compare the proposal with current commitments. A visually balanced plan can still move a crew away from a critical unfinished task.

Apply through the separate controlled action

apply_week_plan requires planning write permission and consumes the proposal payload returned by generation. It is a medium-risk internal write and requires confirmation on web, WhatsApp and voice under the current action contract.

The confirmation should identify the week, assignments and affected projects. If the proposal changed after review, generate or prepare the final version rather than confirming an outdated payload.

Communicate the applied plan

After execution, verify that assignments appear in the live schedule. Notify each crew about changes relevant to them and give project leads the conflict resolutions. Do not send a screenshot as the only source of truth.

Record late changes through the same controlled process so the schedule and communication remain aligned.

Learn from overrides

Track which generated assignments were changed and why: missing skill, travel, client access, delivery or local knowledge. Use those reasons to improve source data and planning rules. Alfie is Enfin’s governed execution layer here: models structure a proposal, while the business context, permissions and confirmation gate determine what becomes real.

Read also construction crew scheduling and meet Alfie.