Try to ensure that all Business Rules are documented consistently and that this documentation is accessible to all that are likely to work with them (use the additional info. section under details). This will ensure that any specific rule details are shared and that the intention/purpose of the rule is made clear.

The documentation should be clear and easy to follow, breaking down the rule logic and components used as well as how they are used and any 'watch outs'.

Avoid technical jargon and/or acronyms as this will make it difficult for other people to understand. Use common words for all users accessing the documentation.

The structure of data tables can have a big impact in how data is accessed. If possible, try to make your tables as simple and straightforward with clear columns and as little duplication.

Be clear on the columns you intend to use for filters/outputs.

Always try to include an active/inactive column where applicable.

Be careful using values that have additional captions and these can be difficult to map to in a rule.

Make sure you name your components, so it is clear what they do and be consistent in your naming.

Also be consistent in the construction of your rules. Try to reuse components and avoid duplication.

Refer to the rule performance tips here.