Assign requirements to a group
Build a group of companies that keeps its own membership up to date, and attach the requirements and frameworks its members owe.
Screenshots are retaken from IQ Entities on every release. Updated 14 October 2026.
A requirement reaches a company only through a group. IQ Entities keeps a group for every jurisdiction, and for every jurisdiction and entity type, and your own groups cover the sets only you can define: the UK subsidiaries, one client's companies, the dormant ones. A group is a rule, not a list. Say once what belongs in it, and every company that matches, today's and next year's, joins it on its own.
The question that decides the rule is what the companies you mean have in common in their records: where they are registered, what kind of entity they are, a tag, a client number, or a parent they sit under.
Create the group
In Administration, open Requirement assignments and choose New group.
Give the group a Name and say in What is it for? (optional) why it exists, then choose Create group. The group opens on its rules.
Say who belongs in it
Under Membership rules, choose Define rules.
Choose what the rule reads. Each kind says what it matches beneath its name.
Pick the values, then read how many companies match right now and which ones. Choose Save rules. Membership is recalculated when you save.
England and Scotland are separate jurisdictions from the United Kingdom, so pick each part of the country your companies are registered in.
Every condition must hold for a company to join. When you need one or the other, make two groups. A company owes what is attached to every group it is in, so nothing is lost by having both.
Attach what the group owes
On the group's Requirements tab, choose Attach.
Under What to attach, choose A requirement and pick it from the list, or A whole framework to attach every duty the framework imposes, including any added to it later. Choose Next.
Under Effective dates (optional), leave From blank for the duty to apply straight away. The panel beneath says how many companies will owe it. Choose Attach.
The requirement is listed on the group, and every member now owes it.
To write a duty of your own first, see Write your own requirement.
Tips from practice
- Do not back-date From without a reason. A start in the past can raise occurrences that were already missed.
- To stop one company owing a group's duties, remove it from the group on the Members tab. The reason you give is recorded, which is the evidence an auditor asks for.
- Prefer a rule over picking companies by hand. A hand-picked group does not grow when the group acquires or incorporates a company.
- Attach a whole framework rather than its duties one by one when the group follows all of it, so duties added to the framework later reach the group too.