Update a planning assignment with Alfie after checking the site time window
Compare worker, crew, task, dates and site dependencies before confirming a planning-assignment change that affects delivery.
Moving one worker or crew can leave a task uncovered even when the calendar still looks occupied. A request to shift Monday to Tuesday needs the exact assignment, project and time window before any change is proposed.
Verify the source, identity and current state
The current Alfie product page positions Alfie as a governed execution layer where context, permissions and confirmations work together. Current application source registers update_assignment; it is classified as medium risk and WhatsApp confirmation. This page does not promise an external integration, autonomous outcome or availability beyond what the source supports.
Turn the request into one bounded decision
Resolve the assignment, worker or crew, project, task, start and end time. Compare access, skills, travel, equipment and dependent tasks, then show the before-and-after schedule to the confirmer.
Keep evidence and separate the next actions
Keep the requester, previous window, new window and confirmation together. A schedule update does not complete the task, notify the customer or remove another assignment; each is a separate governed action.
Test exceptions before daily use
Test a missing identifier, two records with the same name, insufficient permissions, stale source data and a temporarily unavailable system. Alfie should stop with a focused question or a proposal that has not executed. Keep the original request, selected record, relevant source fields, user, timestamp and confirmation without copying more personal or payment data than needed.
Repeat the check when the party, amount, scope, schedule, recipient or document version changes. An earlier result is context, not automatic permission. Define who can correct an error, who must be informed and when the exception is genuinely closed.
Make the result readable to a colleague who did not prepare the record. They should see which facts were established, what uncertainty remains and which action was executed or blocked. Free text can explain the evidence, but it does not replace identity, source or confirmation.
Before rollout, rehearse correction as well as success. Record how the team finds an incorrect selection, which dependent records need review and who may confirm the repair. This keeps one mistake bounded to its record instead of copying it into a schedule, quote, purchase decision or invoice.
Connect preparation to governed execution
Enfin connects the customer, supplier, quote, project, task, item, cost item and invoice in one construction record. Alfie can prepare information and propose an action within available permissions; an authorised user confirms consequential actions. Explore Enfin, compare pricing or discuss your workflow.
Remove one planning assignment with Alfie after checking the site impact
Separate the worker or crew assignment from the underlying task, then confirm coverage, dependencies and notifications before removal.
Update a construction lead status with Alfie after checking the evidence
Change a lead status only after matching the right enquiry, recording the evidence and assigning a separate next step.
Complete a site task with Alfie only after checking evidence and blockers
Match the correct task, distinguish done from verified and confirm a status change with the supporting site evidence.