FAQs

AXLR8 configure Information Request Types for you. We make sure they have the correct “clock” settings, privacy flags and auto-deletion parameters for your Retention Policy. We have templates ready for most jurisdictions.

Here are three examples from our Demo system. Please also see Request Status which works with Request Types to enable events (e.g. “clarification” or “quotation” or “checking proof of ID” or closure) to stop, pause or reset the “clock” as appropriate.

FOI Request Type

The clock is set to ignore bank holidays. Privacy is not flagged (although, see below for “Sensitive FOI”)

Extended FOI

For those FOI requests that require more time – say 40 days, you can create a variant of the FOI Request Type. The only difference is that it has a 40 day “clock”. If you change from and FOI to an FOI – Extended, the deadline will automatically change. Thus, for example, if you realise, on day 9, that an FOI will be much more work, then you have 11 working days to go. If you simply change the Request Type in the drop down box, then you will automatically see the deadline date change to 31 working days hence. The set up ALR8 apply to this is shown below. Some clients have also asked us for other extensions on Request Types.

SAR Request Type

The clock runs including weekends and bank/public holidays. I.e. it works on Calendar days. It is also “Private“.

Sensitive FOI

This is a Request Type for FOIs that include personal, private content. The clock can still run as an FOI but the “Private” flag is set both internally and externally. The “Public” flag is not set. Some organisations ask AXLR8 to set the DPA flag and treat them fully as if they were SARs. They may be Sensitive FOIs for other reasons.

How configuring a Request Type changes IR lifecycle

How else to these parameters change the way the AXLR8 system manages IRs?

1. Length of time to deadline for response progress tracking
2. Appearance or not on the Public Disclosure Log
3. Colours to distinguish them on reports built with AXLR8 Report Builder
4. Privacy settings for users (most of whom will not see “private” flagged request types.
5. Working days (exclude weekends and public holidays set by your organisation in Bank Holiday Admin) or Calendar days.
6. Whether it is in DPA or FOI or EIR reports and screens
7. How retention automation works
8. …………………..and many more.

It is critical to get the Request Types configured correctly. You can see the implications from the list above. We need to consider every dependency.

If you need any changes to your request types, please contact AXLR8 Support. We will be happy to help. You can read the Request Type Admin area but not make any changes yourself. Your AXLR8 Support consultant will ask you for details and configure and test it across business rules with a programmer.

Why must we update Bank Holiday dates? Some information requests have a response deadline in Calendar Days, e.g. SARs. Others like FOI and EIR must be completed in Working days. These “Request Types” are configured in Request Type Admin.

The AXLR8 system must exclude weekends and public holidays for those Request Types. Request Types change from jurisdiction to jurisdiction and in some countries local areas may differ. So, AXLR8 have a simple solution. We provide a Bank Holiday Admin area where you can manage your organisation’s public holiday dates.

Bank Holiday Admin

The Bank Holiday Admin function is to be found in the Super User menu. It is down at the bottom. The reason is that it is not used very often. You can add a few years in ahead if you wish. Don’t forget a diary date to review them.

You can add (or remove) dates for public holidays. This is shown below.

These days are excluded from the day-count up to the response deadline.

Responsibility for updating Bank Holidays

You, the client, are responsible for keeping your Bank Holidays updated. We enter the pubic holidays for a year with you as part of the Super User Systems Admin training. This is done when we first implement your system.

Occasionally, we find a client who has forgotten to update them after that.

We sometimes ask clients if they would like one of our interns to help. It is a good “work experience” job. This might be whilst working on their system on another support job. In that case, we inform the client. Please do not rely upon it. Set a date in your diary. Once a year should do it. There are too many clients and local variations for AXLR8 to manage it centrally.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

AXLR8 configure Information Request Types for you. We make sure they have the correct “clock” settings, privacy flags and auto-deletion parameters for your Retention Policy. We have templates ready for most jurisdictions.

Here are three examples from our Demo system. Please also see Request Status which works with Request Types to enable events (e.g. “clarification” or “quotation” or “checking proof of ID” or closure) to stop, pause or reset the “clock” as appropriate.

FOI Request Type

The clock is set to ignore bank holidays. Privacy is not flagged (although, see below for “Sensitive FOI”)

Extended FOI

For those FOI requests that require more time – say 40 days, you can create a variant of the FOI Request Type. The only difference is that it has a 40 day “clock”. If you change from and FOI to an FOI – Extended, the deadline will automatically change. Thus, for example, if you realise, on day 9, that an FOI will be much more work, then you have 11 working days to go. If you simply change the Request Type in the drop down box, then you will automatically see the deadline date change to 31 working days hence. The set up ALR8 apply to this is shown below. Some clients have also asked us for other extensions on Request Types.

SAR Request Type

The clock runs including weekends and bank/public holidays. I.e. it works on Calendar days. It is also “Private“.

Sensitive FOI

This is a Request Type for FOIs that include personal, private content. The clock can still run as an FOI but the “Private” flag is set both internally and externally. The “Public” flag is not set. Some organisations ask AXLR8 to set the DPA flag and treat them fully as if they were SARs. They may be Sensitive FOIs for other reasons.

How configuring a Request Type changes IR lifecycle

How else to these parameters change the way the AXLR8 system manages IRs?

1. Length of time to deadline for response progress tracking
2. Appearance or not on the Public Disclosure Log
3. Colours to distinguish them on reports built with AXLR8 Report Builder
4. Privacy settings for users (most of whom will not see “private” flagged request types.
5. Working days (exclude weekends and public holidays set by your organisation in Bank Holiday Admin) or Calendar days.
6. Whether it is in DPA or FOI or EIR reports and screens
7. How retention automation works
8. …………………..and many more.

It is critical to get the Request Types configured correctly. You can see the implications from the list above. We need to consider every dependency.

If you need any changes to your request types, please contact AXLR8 Support. We will be happy to help. You can read the Request Type Admin area but not make any changes yourself. Your AXLR8 Support consultant will ask you for details and configure and test it across business rules with a programmer.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

AXLR8 configure Information Request Types for you. We make sure they have the correct “clock” settings, privacy flags and auto-deletion parameters for your Retention Policy. We have templates ready for most jurisdictions.

Here are three examples from our Demo system. Please also see Request Status which works with Request Types to enable events (e.g. “clarification” or “quotation” or “checking proof of ID” or closure) to stop, pause or reset the “clock” as appropriate.

FOI Request Type

The clock is set to ignore bank holidays. Privacy is not flagged (although, see below for “Sensitive FOI”)

Extended FOI

For those FOI requests that require more time – say 40 days, you can create a variant of the FOI Request Type. The only difference is that it has a 40 day “clock”. If you change from and FOI to an FOI – Extended, the deadline will automatically change. Thus, for example, if you realise, on day 9, that an FOI will be much more work, then you have 11 working days to go. If you simply change the Request Type in the drop down box, then you will automatically see the deadline date change to 31 working days hence. The set up ALR8 apply to this is shown below. Some clients have also asked us for other extensions on Request Types.

SAR Request Type

The clock runs including weekends and bank/public holidays. I.e. it works on Calendar days. It is also “Private“.

Sensitive FOI

This is a Request Type for FOIs that include personal, private content. The clock can still run as an FOI but the “Private” flag is set both internally and externally. The “Public” flag is not set. Some organisations ask AXLR8 to set the DPA flag and treat them fully as if they were SARs. They may be Sensitive FOIs for other reasons.

How configuring a Request Type changes IR lifecycle

How else to these parameters change the way the AXLR8 system manages IRs?

1. Length of time to deadline for response progress tracking
2. Appearance or not on the Public Disclosure Log
3. Colours to distinguish them on reports built with AXLR8 Report Builder
4. Privacy settings for users (most of whom will not see “private” flagged request types.
5. Working days (exclude weekends and public holidays set by your organisation in Bank Holiday Admin) or Calendar days.
6. Whether it is in DPA or FOI or EIR reports and screens
7. How retention automation works
8. …………………..and many more.

It is critical to get the Request Types configured correctly. You can see the implications from the list above. We need to consider every dependency.

If you need any changes to your request types, please contact AXLR8 Support. We will be happy to help. You can read the Request Type Admin area but not make any changes yourself. Your AXLR8 Support consultant will ask you for details and configure and test it across business rules with a programmer.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

AXLR8 configure Information Request Types for you. We make sure they have the correct “clock” settings, privacy flags and auto-deletion parameters for your Retention Policy. We have templates ready for most jurisdictions.

Here are three examples from our Demo system. Please also see Request Status which works with Request Types to enable events (e.g. “clarification” or “quotation” or “checking proof of ID” or closure) to stop, pause or reset the “clock” as appropriate.

FOI Request Type

The clock is set to ignore bank holidays. Privacy is not flagged (although, see below for “Sensitive FOI”)

Extended FOI

For those FOI requests that require more time – say 40 days, you can create a variant of the FOI Request Type. The only difference is that it has a 40 day “clock”. If you change from and FOI to an FOI – Extended, the deadline will automatically change. Thus, for example, if you realise, on day 9, that an FOI will be much more work, then you have 11 working days to go. If you simply change the Request Type in the drop down box, then you will automatically see the deadline date change to 31 working days hence. The set up ALR8 apply to this is shown below. Some clients have also asked us for other extensions on Request Types.

SAR Request Type

The clock runs including weekends and bank/public holidays. I.e. it works on Calendar days. It is also “Private“.

Sensitive FOI

This is a Request Type for FOIs that include personal, private content. The clock can still run as an FOI but the “Private” flag is set both internally and externally. The “Public” flag is not set. Some organisations ask AXLR8 to set the DPA flag and treat them fully as if they were SARs. They may be Sensitive FOIs for other reasons.

How configuring a Request Type changes IR lifecycle

How else to these parameters change the way the AXLR8 system manages IRs?

1. Length of time to deadline for response progress tracking
2. Appearance or not on the Public Disclosure Log
3. Colours to distinguish them on reports built with AXLR8 Report Builder
4. Privacy settings for users (most of whom will not see “private” flagged request types.
5. Working days (exclude weekends and public holidays set by your organisation in Bank Holiday Admin) or Calendar days.
6. Whether it is in DPA or FOI or EIR reports and screens
7. How retention automation works
8. …………………..and many more.

It is critical to get the Request Types configured correctly. You can see the implications from the list above. We need to consider every dependency.

If you need any changes to your request types, please contact AXLR8 Support. We will be happy to help. You can read the Request Type Admin area but not make any changes yourself. Your AXLR8 Support consultant will ask you for details and configure and test it across business rules with a programmer.

Why must we update Bank Holiday dates? Some information requests have a response deadline in Calendar Days, e.g. SARs. Others like FOI and EIR must be completed in Working days. These “Request Types” are configured in Request Type Admin.

The AXLR8 system must exclude weekends and public holidays for those Request Types. Request Types change from jurisdiction to jurisdiction and in some countries local areas may differ. So, AXLR8 have a simple solution. We provide a Bank Holiday Admin area where you can manage your organisation’s public holiday dates.

Bank Holiday Admin

The Bank Holiday Admin function is to be found in the Super User menu. It is down at the bottom. The reason is that it is not used very often. You can add a few years in ahead if you wish. Don’t forget a diary date to review them.

You can add (or remove) dates for public holidays. This is shown below.

These days are excluded from the day-count up to the response deadline.

Responsibility for updating Bank Holidays

You, the client, are responsible for keeping your Bank Holidays updated. We enter the pubic holidays for a year with you as part of the Super User Systems Admin training. This is done when we first implement your system.

Occasionally, we find a client who has forgotten to update them after that.

We sometimes ask clients if they would like one of our interns to help. It is a good “work experience” job. This might be whilst working on their system on another support job. In that case, we inform the client. Please do not rely upon it. Set a date in your diary. Once a year should do it. There are too many clients and local variations for AXLR8 to manage it centrally.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

AXLR8 configure Information Request Types for you. We make sure they have the correct “clock” settings, privacy flags and auto-deletion parameters for your Retention Policy. We have templates ready for most jurisdictions.

Here are three examples from our Demo system. Please also see Request Status which works with Request Types to enable events (e.g. “clarification” or “quotation” or “checking proof of ID” or closure) to stop, pause or reset the “clock” as appropriate.

FOI Request Type

The clock is set to ignore bank holidays. Privacy is not flagged (although, see below for “Sensitive FOI”)

Extended FOI

For those FOI requests that require more time – say 40 days, you can create a variant of the FOI Request Type. The only difference is that it has a 40 day “clock”. If you change from and FOI to an FOI – Extended, the deadline will automatically change. Thus, for example, if you realise, on day 9, that an FOI will be much more work, then you have 11 working days to go. If you simply change the Request Type in the drop down box, then you will automatically see the deadline date change to 31 working days hence. The set up ALR8 apply to this is shown below. Some clients have also asked us for other extensions on Request Types.

SAR Request Type

The clock runs including weekends and bank/public holidays. I.e. it works on Calendar days. It is also “Private“.

Sensitive FOI

This is a Request Type for FOIs that include personal, private content. The clock can still run as an FOI but the “Private” flag is set both internally and externally. The “Public” flag is not set. Some organisations ask AXLR8 to set the DPA flag and treat them fully as if they were SARs. They may be Sensitive FOIs for other reasons.

How configuring a Request Type changes IR lifecycle

How else to these parameters change the way the AXLR8 system manages IRs?

1. Length of time to deadline for response progress tracking
2. Appearance or not on the Public Disclosure Log
3. Colours to distinguish them on reports built with AXLR8 Report Builder
4. Privacy settings for users (most of whom will not see “private” flagged request types.
5. Working days (exclude weekends and public holidays set by your organisation in Bank Holiday Admin) or Calendar days.
6. Whether it is in DPA or FOI or EIR reports and screens
7. How retention automation works
8. …………………..and many more.

It is critical to get the Request Types configured correctly. You can see the implications from the list above. We need to consider every dependency.

If you need any changes to your request types, please contact AXLR8 Support. We will be happy to help. You can read the Request Type Admin area but not make any changes yourself. Your AXLR8 Support consultant will ask you for details and configure and test it across business rules with a programmer.

Why must we update Bank Holiday dates? Some information requests have a response deadline in Calendar Days, e.g. SARs. Others like FOI and EIR must be completed in Working days. These “Request Types” are configured in Request Type Admin.

The AXLR8 system must exclude weekends and public holidays for those Request Types. Request Types change from jurisdiction to jurisdiction and in some countries local areas may differ. So, AXLR8 have a simple solution. We provide a Bank Holiday Admin area where you can manage your organisation’s public holiday dates.

Bank Holiday Admin

The Bank Holiday Admin function is to be found in the Super User menu. It is down at the bottom. The reason is that it is not used very often. You can add a few years in ahead if you wish. Don’t forget a diary date to review them.

You can add (or remove) dates for public holidays. This is shown below.

These days are excluded from the day-count up to the response deadline.

Responsibility for updating Bank Holidays

You, the client, are responsible for keeping your Bank Holidays updated. We enter the pubic holidays for a year with you as part of the Super User Systems Admin training. This is done when we first implement your system.

Occasionally, we find a client who has forgotten to update them after that.

We sometimes ask clients if they would like one of our interns to help. It is a good “work experience” job. This might be whilst working on their system on another support job. In that case, we inform the client. Please do not rely upon it. Set a date in your diary. Once a year should do it. There are too many clients and local variations for AXLR8 to manage it centrally.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

AXLR8 configure Information Request Types for you. We make sure they have the correct “clock” settings, privacy flags and auto-deletion parameters for your Retention Policy. We have templates ready for most jurisdictions.

Here are three examples from our Demo system. Please also see Request Status which works with Request Types to enable events (e.g. “clarification” or “quotation” or “checking proof of ID” or closure) to stop, pause or reset the “clock” as appropriate.

FOI Request Type

The clock is set to ignore bank holidays. Privacy is not flagged (although, see below for “Sensitive FOI”)

Extended FOI

For those FOI requests that require more time – say 40 days, you can create a variant of the FOI Request Type. The only difference is that it has a 40 day “clock”. If you change from and FOI to an FOI – Extended, the deadline will automatically change. Thus, for example, if you realise, on day 9, that an FOI will be much more work, then you have 11 working days to go. If you simply change the Request Type in the drop down box, then you will automatically see the deadline date change to 31 working days hence. The set up ALR8 apply to this is shown below. Some clients have also asked us for other extensions on Request Types.

SAR Request Type

The clock runs including weekends and bank/public holidays. I.e. it works on Calendar days. It is also “Private“.

Sensitive FOI

This is a Request Type for FOIs that include personal, private content. The clock can still run as an FOI but the “Private” flag is set both internally and externally. The “Public” flag is not set. Some organisations ask AXLR8 to set the DPA flag and treat them fully as if they were SARs. They may be Sensitive FOIs for other reasons.

How configuring a Request Type changes IR lifecycle

How else to these parameters change the way the AXLR8 system manages IRs?

1. Length of time to deadline for response progress tracking
2. Appearance or not on the Public Disclosure Log
3. Colours to distinguish them on reports built with AXLR8 Report Builder
4. Privacy settings for users (most of whom will not see “private” flagged request types.
5. Working days (exclude weekends and public holidays set by your organisation in Bank Holiday Admin) or Calendar days.
6. Whether it is in DPA or FOI or EIR reports and screens
7. How retention automation works
8. …………………..and many more.

It is critical to get the Request Types configured correctly. You can see the implications from the list above. We need to consider every dependency.

If you need any changes to your request types, please contact AXLR8 Support. We will be happy to help. You can read the Request Type Admin area but not make any changes yourself. Your AXLR8 Support consultant will ask you for details and configure and test it across business rules with a programmer.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

AXLR8 configure Information Request Types for you. We make sure they have the correct “clock” settings, privacy flags and auto-deletion parameters for your Retention Policy. We have templates ready for most jurisdictions.

Here are three examples from our Demo system. Please also see Request Status which works with Request Types to enable events (e.g. “clarification” or “quotation” or “checking proof of ID” or closure) to stop, pause or reset the “clock” as appropriate.

FOI Request Type

The clock is set to ignore bank holidays. Privacy is not flagged (although, see below for “Sensitive FOI”)

Extended FOI

For those FOI requests that require more time – say 40 days, you can create a variant of the FOI Request Type. The only difference is that it has a 40 day “clock”. If you change from and FOI to an FOI – Extended, the deadline will automatically change. Thus, for example, if you realise, on day 9, that an FOI will be much more work, then you have 11 working days to go. If you simply change the Request Type in the drop down box, then you will automatically see the deadline date change to 31 working days hence. The set up ALR8 apply to this is shown below. Some clients have also asked us for other extensions on Request Types.

SAR Request Type

The clock runs including weekends and bank/public holidays. I.e. it works on Calendar days. It is also “Private“.

Sensitive FOI

This is a Request Type for FOIs that include personal, private content. The clock can still run as an FOI but the “Private” flag is set both internally and externally. The “Public” flag is not set. Some organisations ask AXLR8 to set the DPA flag and treat them fully as if they were SARs. They may be Sensitive FOIs for other reasons.

How configuring a Request Type changes IR lifecycle

How else to these parameters change the way the AXLR8 system manages IRs?

1. Length of time to deadline for response progress tracking
2. Appearance or not on the Public Disclosure Log
3. Colours to distinguish them on reports built with AXLR8 Report Builder
4. Privacy settings for users (most of whom will not see “private” flagged request types.
5. Working days (exclude weekends and public holidays set by your organisation in Bank Holiday Admin) or Calendar days.
6. Whether it is in DPA or FOI or EIR reports and screens
7. How retention automation works
8. …………………..and many more.

It is critical to get the Request Types configured correctly. You can see the implications from the list above. We need to consider every dependency.

If you need any changes to your request types, please contact AXLR8 Support. We will be happy to help. You can read the Request Type Admin area but not make any changes yourself. Your AXLR8 Support consultant will ask you for details and configure and test it across business rules with a programmer.

Why must we update Bank Holiday dates? Some information requests have a response deadline in Calendar Days, e.g. SARs. Others like FOI and EIR must be completed in Working days. These “Request Types” are configured in Request Type Admin.

The AXLR8 system must exclude weekends and public holidays for those Request Types. Request Types change from jurisdiction to jurisdiction and in some countries local areas may differ. So, AXLR8 have a simple solution. We provide a Bank Holiday Admin area where you can manage your organisation’s public holiday dates.

Bank Holiday Admin

The Bank Holiday Admin function is to be found in the Super User menu. It is down at the bottom. The reason is that it is not used very often. You can add a few years in ahead if you wish. Don’t forget a diary date to review them.

You can add (or remove) dates for public holidays. This is shown below.

These days are excluded from the day-count up to the response deadline.

Responsibility for updating Bank Holidays

You, the client, are responsible for keeping your Bank Holidays updated. We enter the pubic holidays for a year with you as part of the Super User Systems Admin training. This is done when we first implement your system.

Occasionally, we find a client who has forgotten to update them after that.

We sometimes ask clients if they would like one of our interns to help. It is a good “work experience” job. This might be whilst working on their system on another support job. In that case, we inform the client. Please do not rely upon it. Set a date in your diary. Once a year should do it. There are too many clients and local variations for AXLR8 to manage it centrally.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

AXLR8 configure Information Request Types for you. We make sure they have the correct “clock” settings, privacy flags and auto-deletion parameters for your Retention Policy. We have templates ready for most jurisdictions.

Here are three examples from our Demo system. Please also see Request Status which works with Request Types to enable events (e.g. “clarification” or “quotation” or “checking proof of ID” or closure) to stop, pause or reset the “clock” as appropriate.

FOI Request Type

The clock is set to ignore bank holidays. Privacy is not flagged (although, see below for “Sensitive FOI”)

Extended FOI

For those FOI requests that require more time – say 40 days, you can create a variant of the FOI Request Type. The only difference is that it has a 40 day “clock”. If you change from and FOI to an FOI – Extended, the deadline will automatically change. Thus, for example, if you realise, on day 9, that an FOI will be much more work, then you have 11 working days to go. If you simply change the Request Type in the drop down box, then you will automatically see the deadline date change to 31 working days hence. The set up ALR8 apply to this is shown below. Some clients have also asked us for other extensions on Request Types.

SAR Request Type

The clock runs including weekends and bank/public holidays. I.e. it works on Calendar days. It is also “Private“.

Sensitive FOI

This is a Request Type for FOIs that include personal, private content. The clock can still run as an FOI but the “Private” flag is set both internally and externally. The “Public” flag is not set. Some organisations ask AXLR8 to set the DPA flag and treat them fully as if they were SARs. They may be Sensitive FOIs for other reasons.

How configuring a Request Type changes IR lifecycle

How else to these parameters change the way the AXLR8 system manages IRs?

1. Length of time to deadline for response progress tracking
2. Appearance or not on the Public Disclosure Log
3. Colours to distinguish them on reports built with AXLR8 Report Builder
4. Privacy settings for users (most of whom will not see “private” flagged request types.
5. Working days (exclude weekends and public holidays set by your organisation in Bank Holiday Admin) or Calendar days.
6. Whether it is in DPA or FOI or EIR reports and screens
7. How retention automation works
8. …………………..and many more.

It is critical to get the Request Types configured correctly. You can see the implications from the list above. We need to consider every dependency.

If you need any changes to your request types, please contact AXLR8 Support. We will be happy to help. You can read the Request Type Admin area but not make any changes yourself. Your AXLR8 Support consultant will ask you for details and configure and test it across business rules with a programmer.

Why must we update Bank Holiday dates? Some information requests have a response deadline in Calendar Days, e.g. SARs. Others like FOI and EIR must be completed in Working days. These “Request Types” are configured in Request Type Admin.

The AXLR8 system must exclude weekends and public holidays for those Request Types. Request Types change from jurisdiction to jurisdiction and in some countries local areas may differ. So, AXLR8 have a simple solution. We provide a Bank Holiday Admin area where you can manage your organisation’s public holiday dates.

Bank Holiday Admin

The Bank Holiday Admin function is to be found in the Super User menu. It is down at the bottom. The reason is that it is not used very often. You can add a few years in ahead if you wish. Don’t forget a diary date to review them.

You can add (or remove) dates for public holidays. This is shown below.

These days are excluded from the day-count up to the response deadline.

Responsibility for updating Bank Holidays

You, the client, are responsible for keeping your Bank Holidays updated. We enter the pubic holidays for a year with you as part of the Super User Systems Admin training. This is done when we first implement your system.

Occasionally, we find a client who has forgotten to update them after that.

We sometimes ask clients if they would like one of our interns to help. It is a good “work experience” job. This might be whilst working on their system on another support job. In that case, we inform the client. Please do not rely upon it. Set a date in your diary. Once a year should do it. There are too many clients and local variations for AXLR8 to manage it centrally.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

AXLR8 configure Information Request Types for you. We make sure they have the correct “clock” settings, privacy flags and auto-deletion parameters for your Retention Policy. We have templates ready for most jurisdictions.

Here are three examples from our Demo system. Please also see Request Status which works with Request Types to enable events (e.g. “clarification” or “quotation” or “checking proof of ID” or closure) to stop, pause or reset the “clock” as appropriate.

FOI Request Type

The clock is set to ignore bank holidays. Privacy is not flagged (although, see below for “Sensitive FOI”)

Extended FOI

For those FOI requests that require more time – say 40 days, you can create a variant of the FOI Request Type. The only difference is that it has a 40 day “clock”. If you change from and FOI to an FOI – Extended, the deadline will automatically change. Thus, for example, if you realise, on day 9, that an FOI will be much more work, then you have 11 working days to go. If you simply change the Request Type in the drop down box, then you will automatically see the deadline date change to 31 working days hence. The set up ALR8 apply to this is shown below. Some clients have also asked us for other extensions on Request Types.

SAR Request Type

The clock runs including weekends and bank/public holidays. I.e. it works on Calendar days. It is also “Private“.

Sensitive FOI

This is a Request Type for FOIs that include personal, private content. The clock can still run as an FOI but the “Private” flag is set both internally and externally. The “Public” flag is not set. Some organisations ask AXLR8 to set the DPA flag and treat them fully as if they were SARs. They may be Sensitive FOIs for other reasons.

How configuring a Request Type changes IR lifecycle

How else to these parameters change the way the AXLR8 system manages IRs?

1. Length of time to deadline for response progress tracking
2. Appearance or not on the Public Disclosure Log
3. Colours to distinguish them on reports built with AXLR8 Report Builder
4. Privacy settings for users (most of whom will not see “private” flagged request types.
5. Working days (exclude weekends and public holidays set by your organisation in Bank Holiday Admin) or Calendar days.
6. Whether it is in DPA or FOI or EIR reports and screens
7. How retention automation works
8. …………………..and many more.

It is critical to get the Request Types configured correctly. You can see the implications from the list above. We need to consider every dependency.

If you need any changes to your request types, please contact AXLR8 Support. We will be happy to help. You can read the Request Type Admin area but not make any changes yourself. Your AXLR8 Support consultant will ask you for details and configure and test it across business rules with a programmer.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

AXLR8 configure Information Request Types for you. We make sure they have the correct “clock” settings, privacy flags and auto-deletion parameters for your Retention Policy. We have templates ready for most jurisdictions.

Here are three examples from our Demo system. Please also see Request Status which works with Request Types to enable events (e.g. “clarification” or “quotation” or “checking proof of ID” or closure) to stop, pause or reset the “clock” as appropriate.

FOI Request Type

The clock is set to ignore bank holidays. Privacy is not flagged (although, see below for “Sensitive FOI”)

Extended FOI

For those FOI requests that require more time – say 40 days, you can create a variant of the FOI Request Type. The only difference is that it has a 40 day “clock”. If you change from and FOI to an FOI – Extended, the deadline will automatically change. Thus, for example, if you realise, on day 9, that an FOI will be much more work, then you have 11 working days to go. If you simply change the Request Type in the drop down box, then you will automatically see the deadline date change to 31 working days hence. The set up ALR8 apply to this is shown below. Some clients have also asked us for other extensions on Request Types.

SAR Request Type

The clock runs including weekends and bank/public holidays. I.e. it works on Calendar days. It is also “Private“.

Sensitive FOI

This is a Request Type for FOIs that include personal, private content. The clock can still run as an FOI but the “Private” flag is set both internally and externally. The “Public” flag is not set. Some organisations ask AXLR8 to set the DPA flag and treat them fully as if they were SARs. They may be Sensitive FOIs for other reasons.

How configuring a Request Type changes IR lifecycle

How else to these parameters change the way the AXLR8 system manages IRs?

1. Length of time to deadline for response progress tracking
2. Appearance or not on the Public Disclosure Log
3. Colours to distinguish them on reports built with AXLR8 Report Builder
4. Privacy settings for users (most of whom will not see “private” flagged request types.
5. Working days (exclude weekends and public holidays set by your organisation in Bank Holiday Admin) or Calendar days.
6. Whether it is in DPA or FOI or EIR reports and screens
7. How retention automation works
8. …………………..and many more.

It is critical to get the Request Types configured correctly. You can see the implications from the list above. We need to consider every dependency.

If you need any changes to your request types, please contact AXLR8 Support. We will be happy to help. You can read the Request Type Admin area but not make any changes yourself. Your AXLR8 Support consultant will ask you for details and configure and test it across business rules with a programmer.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Why must we update Bank Holiday dates? Some information requests have a response deadline in Calendar Days, e.g. SARs. Others like FOI and EIR must be completed in Working days. These “Request Types” are configured in Request Type Admin.

The AXLR8 system must exclude weekends and public holidays for those Request Types. Request Types change from jurisdiction to jurisdiction and in some countries local areas may differ. So, AXLR8 have a simple solution. We provide a Bank Holiday Admin area where you can manage your organisation’s public holiday dates.

Bank Holiday Admin

The Bank Holiday Admin function is to be found in the Super User menu. It is down at the bottom. The reason is that it is not used very often. You can add a few years in ahead if you wish. Don’t forget a diary date to review them.

You can add (or remove) dates for public holidays. This is shown below.

These days are excluded from the day-count up to the response deadline.

Responsibility for updating Bank Holidays

You, the client, are responsible for keeping your Bank Holidays updated. We enter the pubic holidays for a year with you as part of the Super User Systems Admin training. This is done when we first implement your system.

Occasionally, we find a client who has forgotten to update them after that.

We sometimes ask clients if they would like one of our interns to help. It is a good “work experience” job. This might be whilst working on their system on another support job. In that case, we inform the client. Please do not rely upon it. Set a date in your diary. Once a year should do it. There are too many clients and local variations for AXLR8 to manage it centrally.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

AXLR8 configure Information Request Types for you. We make sure they have the correct “clock” settings, privacy flags and auto-deletion parameters for your Retention Policy. We have templates ready for most jurisdictions.

Here are three examples from our Demo system. Please also see Request Status which works with Request Types to enable events (e.g. “clarification” or “quotation” or “checking proof of ID” or closure) to stop, pause or reset the “clock” as appropriate.

FOI Request Type

The clock is set to ignore bank holidays. Privacy is not flagged (although, see below for “Sensitive FOI”)

Extended FOI

For those FOI requests that require more time – say 40 days, you can create a variant of the FOI Request Type. The only difference is that it has a 40 day “clock”. If you change from and FOI to an FOI – Extended, the deadline will automatically change. Thus, for example, if you realise, on day 9, that an FOI will be much more work, then you have 11 working days to go. If you simply change the Request Type in the drop down box, then you will automatically see the deadline date change to 31 working days hence. The set up ALR8 apply to this is shown below. Some clients have also asked us for other extensions on Request Types.

SAR Request Type

The clock runs including weekends and bank/public holidays. I.e. it works on Calendar days. It is also “Private“.

Sensitive FOI

This is a Request Type for FOIs that include personal, private content. The clock can still run as an FOI but the “Private” flag is set both internally and externally. The “Public” flag is not set. Some organisations ask AXLR8 to set the DPA flag and treat them fully as if they were SARs. They may be Sensitive FOIs for other reasons.

How configuring a Request Type changes IR lifecycle

How else to these parameters change the way the AXLR8 system manages IRs?

1. Length of time to deadline for response progress tracking
2. Appearance or not on the Public Disclosure Log
3. Colours to distinguish them on reports built with AXLR8 Report Builder
4. Privacy settings for users (most of whom will not see “private” flagged request types.
5. Working days (exclude weekends and public holidays set by your organisation in Bank Holiday Admin) or Calendar days.
6. Whether it is in DPA or FOI or EIR reports and screens
7. How retention automation works
8. …………………..and many more.

It is critical to get the Request Types configured correctly. You can see the implications from the list above. We need to consider every dependency.

If you need any changes to your request types, please contact AXLR8 Support. We will be happy to help. You can read the Request Type Admin area but not make any changes yourself. Your AXLR8 Support consultant will ask you for details and configure and test it across business rules with a programmer.

Why must we update Bank Holiday dates? Some information requests have a response deadline in Calendar Days, e.g. SARs. Others like FOI and EIR must be completed in Working days. These “Request Types” are configured in Request Type Admin.

The AXLR8 system must exclude weekends and public holidays for those Request Types. Request Types change from jurisdiction to jurisdiction and in some countries local areas may differ. So, AXLR8 have a simple solution. We provide a Bank Holiday Admin area where you can manage your organisation’s public holiday dates.

Bank Holiday Admin

The Bank Holiday Admin function is to be found in the Super User menu. It is down at the bottom. The reason is that it is not used very often. You can add a few years in ahead if you wish. Don’t forget a diary date to review them.

You can add (or remove) dates for public holidays. This is shown below.

These days are excluded from the day-count up to the response deadline.

Responsibility for updating Bank Holidays

You, the client, are responsible for keeping your Bank Holidays updated. We enter the pubic holidays for a year with you as part of the Super User Systems Admin training. This is done when we first implement your system.

Occasionally, we find a client who has forgotten to update them after that.

We sometimes ask clients if they would like one of our interns to help. It is a good “work experience” job. This might be whilst working on their system on another support job. In that case, we inform the client. Please do not rely upon it. Set a date in your diary. Once a year should do it. There are too many clients and local variations for AXLR8 to manage it centrally.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.

Short answer, anything you want during any timescale you can afford.

However, this is a standard AXLR8 demo of 48 minutes plus questions.

Items such as migration from legacy systems and security and other areas of compliance required in the public sector will be dealt with in depth if required at a later stage.

Other tools

If of interest, we can always look at other IG tools later Data Breach, DPIA, Information Asset Register, Data Sharing Policy Register, etc.  Also, Complaints Processing and other workflows.