Some work always follows other work — a tax return follows annual accounts, an AML re-assessment follows ongoing monitoring. Instead of point-to-point dependencies between individual workflows, the platform models these chains through Related Services, which makes them easier to set up once and re-apply every period.
Step 1 — declare the relationship between services
- Open Settings > Services.
- Click the service that will trigger the follow-up (the "primary" service).
- In the Related Services section, add the service(s) that should follow.
- For each related service, set the period and any lead time so the platform knows when the follow-up is expected.
- Save.
Step 2 — generate the follow-on workflows
- Click Workflows in the sidebar.
- Open the three-dot menu in the top right and choose Bulk Related Services.
- Pick the primary service — the page lists eligible "parent" workflows.
- Optionally narrow by related service to focus on a single follow-up chain.
- Review the suggested follow-on workflows. The platform auto-links each one to the right parent workflow using a strategy you choose:
- By exact period — match dates precisely.
- By period overlap — match overlapping periods.
- Previous / next period — match one period before or after.
- Most recent — fall back to the latest workflow for that client / service.
- Tick the rows you want to create.
- Click Create workflows.
The follow-on workflows are generated for each client and linked to their parent.
Step 3 — keep an eye on coverage
Open Reports > Service Obligations to see, for every client, which services are owed this period and whether the corresponding workflow has been created. This is the easiest way to spot a follow-up that has not been generated yet.
Tip: Related Services replaces the older "point-to-point dependency" model. If you used dependencies before, modelling the same relationship at the service level keeps it consistent for every client that uses both services — no per-workflow setup required.