The time frame varies from company to company. It is very much dependent upon the current level of adherence to the codes and the quality of the submission pack to the Assessors. The Due Diligence check can take up to 2 weeks, then after engagement with the Assessors, the response rate between the applicant Member and Assessor will dictate the length of the process. From submitting the Due Diligence check information, the application should be completed within one year from the commencement of the Due Diligence check. If the assessment process goes beyond this date, there is a requirement to resubmit the Fit & Proper Persons forms, as these are annual checks performed by FCSA. Evidence collected by the Assessors may have expired, resulting in further work and Assessor costs.
Upon successful competition of the Due Diligence check, an invoice will be raised for the Assessment fee. Once this has been paid, FCSA will engage an Assessor as chosen by us. The Assessor will then get in touch with your chosen point of contact to explain the next steps in the assessment process.
No, use the codes as a framework to ensure compliance when two years are achieved.
To proceed, we require audited accounts, and our code operates on a ‘prove it’ basis. You must have been trading for more than a year to pass the AWR checks. Additionally, we need to review your leaver processes, specifically looking at those who have left over the past two years.
No. To obtain a wide enough range for the assessment, we need 75 samples. These samples must be diverse and capable of providing evidence for all aspects of the code.
To show stability in your supply chain and confirm that you are not a micro umbrella company (MUC), audited accounts are necessary for review by auditors. While not always legally required, the FCSA demands this higher standard. Having audited accounts also demonstrates your commitment to compliance, and financial stability, and addresses any concerns assessors raise. This ensures that all money is accurately accounted for, reflecting your dedication to financial responsibility.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by our website to allow the us to implement or change the website's content in real-time. |
hubspotutk | 5 months 27 days | HubSpot sets this cookie to keep a record of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
JSESSIONID | session | The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application. |
PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
_GRECAPTCHA | 5 months 27 days | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
__hssc | 30 minutes | HubSpot sets this cookie to keep a record of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
__hstc | 5 months 27 days | This is the main cookie set by Hubspot, for recording visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 30 minutes | HubSpot sets this cookie to keep a record of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
Cookie | Duration | Description |
---|---|---|
hubspotutk | 5 months 27 days | HubSpot sets this cookie to keep a record of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjIncludedInPageviewSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit. |
_hjIncludedInSessionSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's daily session limit. |
__hstc | 5 months 27 days | This is the main cookie set by Hubspot, for recording visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
Cookie | Duration | Description |
---|---|---|
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
Cookie | Duration | Description |
---|---|---|
baqend-speedkit-user-id | 5 months 27 days | No description available. |
heyzine_session | 3 months | No description |
_hjSessionUser_2855694 | 1 year | No description |
_hjSession_2855694 | 30 minutes | No description |