--- title: "Stopping tasks firing on a loan" slug: "58-stopping-tasks-firing-on-a-loan" updated: 2026-11-02T18:42:39Z published: 2026-11-02T18:33:57Z canonical: "docs.thebigpos.com/58-stopping-tasks-firing-on-a-loan" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.thebigpos.com/llms.txt > Use this file to discover all available pages before exploring further. # Stopping tasks firing on a loan Task lists are generated by rules, not chosen loan by loan, so a file that should not have them gets them anyway. This comes up most often on loans being moved in from another point of sale, and on branches or workflows that do not use tasks at all. ## On a single loan There is no per-loan bypass. Open the loan, go to **Tasks**, select all and delete. The borrower's needs list goes with them. Do this before the borrower is invited where you can, so no needs-list email goes out. ## For a whole branch Tasks can be turned off at branch level in the branch settings. The setting carries down to any loan officer sites tied to that branch, so there is nothing to repeat per officer. If the branch has no loan officer sites, the branch setting is all you need. For finer control than that — targeting particular branches or loan officers — the route today is **Encompass field triggers and DDM rules**, keyed on branch or org ID or on a custom field. Your Encompass admin builds these, not POS support. Branch-level and LO-level task rules inside the POS itself are in development, with no date. ## Switching tasks off for one loan officer Tasks can be turned off for a specific loan officer, with two limits worth knowing before you ask: - It is all-or-nothing across that loan officer's whole pipeline. You cannot pick which of their loans are affected. - It only affects new loans. Loans already open keep the tasks they have. No "you have new tasks" notifications are generated for that loan officer's borrowers while it is off. ## Milestones and notifications Milestone and notification configuration is company-wide only. There is no per-branch or per-loan-officer version. The cap is ten purchase milestones and ten refinance milestones. ## Building a workflow that excludes tasks The advanced task filters are include-only — there is no "does not equal" condition. A rule cannot be written as "every workflow except this one". Build the rule from the workflows and conditions you do want the task to fire on, and leave the rest out. ## Before a migration If files are coming in from another system in bulk, agree the task position first. Clearing task lists after the fact means deleting them file by file, and borrowers may already have been emailed. ## What support will ask for The branch or workflow, and whether you want no tasks at all or a reduced set.