Explanation of fields

Many of the fields for Strategies are intuitive. Following is a list of fields that either require additional explanation to get the best outcome, or have an impact on dashboards and reports. 

• Commencement date
  • This does not impact reporting or dashboards. 
  • It merely serves as a record when a strategy was, or is expected, to be implemented.
• Next due
  • This is when a strategy will next be executed. For strategies only expected to come into play in future, the 'Next due' and 'Commencement date' will initially be the same. 
  • For strategies that repeat (e.g. annual lump sum super contributions), the 'Next due' date should get pushed forward each time the strategy is done. 
  • The 'Next due' filed, in conjunction with the 'Status' field, determine whether a strategy is overdue, as detailed here. 
• Repetition frequency
  • How often the strategy repeats, including an option for 'Once off'. 
  • Currently this doe not have any implications within the app, and merely serves as an indication of how far to push forward the 'Next due' date following implementation. 
• Expected conclusion
  • When the strategy is expected to be finalised. Using the example of annual superannuation contributions, this may be set to the clients anticipated retirement date. 
  • This field can impact the overdue status of a strategy on dashboards and reports, as noted here. 
• Status
  • A status indicating whether a strategy is something that needs to be considered, is finalised, in progress or no longer applicable. 
  • The status impacts on the overdue status on dashboards and reports as noted here. 
  • For recurring tasks, Beegle recommends setting the status to 'To consider' initially, 'In progress' when implementation commences, then back to 'To consider' once the 'Next due' date is incremented. If the recurring strategy is finalised (e.g. no more annual super contributions following retirement) the status can be set to 'Finalised'.