Workflow overview
The purpose is to automate repetition without removing control over the underlying engagement or completion status.
Engagement position
Use the engagement area to record the live authority to act. Where an older client already has a valid engagement, a manual engagement date may represent that history. If Balansix e-signature is used, the electronic signature timestamp is retained as its own event.
Recurring task creation
Once a service is active, the system can derive recurring obligations from client/service data. Staff should review exceptions, ownership and due dates rather than manually recreating routine work.
Reminder rules
Firm-level reminder-day rules should determine when scheduled reminders are sent. A completed/submitted obligation should stop further reminders. The next recurring obligation should be created once, not duplicated by repeated completion actions.
Ending an engagement
When the relationship ends, use the controlled disengagement/archive route. The historic audit trail should remain intact even though future recurring work is no longer active.