Since the first confirmed COVID-19 death in the UK on March 5th, the Coronavirus has rapidly changed the way people and businesses interact and there is no exception for the legal profession.
On the 19th March, British Judge and President of the Family Division, Sir Andrew MacFarlane suggested a significant change in direction in how the Family Court will function during this time of uncertainty.
As default, Family Court hearings will be undertaken remotely via; email, telephone or video/Skype. Each case will be reviewed to see if physical attendance is required as a necessity, and all remote hearings must ensure that they have the capacity to record hearings.
Case-specific factors will determine whether a remote hearing is feasible. Suitable categories include:
Even in emergency cases, provisions should be made for the trial to be conducted remotely. If a case is genuinely urgent, and it is not possible to conduct a remote hearing, the court will endeavour to conduct the hearing face-to-face. This will be carried out in a way that will limit the chance of infection for all parties involved.
If the case cannot be listed for a remote hearing, and it isn’t an emergency, the case must be adjourned and listed as soon as possible for a directions hearing, which can be completed remotely.
The aim of these directions is to identify the best possible way of conducting the court process, in order to achieve a fair outcome in a timely manner, whilst minimising the chance of infection through personal contact.
The guidance indicates a significant change of direction in the way Family Court proceedings are conducted, that will enable us to continue to operate and meet the needs of those who rely on the Court for protection and justice.
If you have any questions at all on how this may affect you, please do not hesitate to contact firstname.lastname@example.org
|__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.|
|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".|
|__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 track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.|
|ss||session||This cookie is set by the provider Eventbrite. This cookie is used for the functionality of website chat-box function.|
|TawkConnectionTime||session||Tawk.to, a live chat functionality, sets this cookie. For improved service, this cookie helps remember users so that previous chats can be linked together.|
|__hstc||1 year 24 days||This is the main cookie set by Hubspot, for tracking 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).|
|_ga||2 years||The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.|
|_gat_gtag_UA_162540320_1||1 minute||Set by Google to distinguish users.|
|_gcl_au||3 months||Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.|
|_gid||1 day||Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.|
|hubspotutk||1 year 24 days||This cookie is used by HubSpot to keep track of the visitors to the website. This cookie is passed to Hubspot on form submission and used when deduplicating contacts.|
|_fbp||3 months||This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.|
|fr||3 months||Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.|
|test_cookie||15 minutes||The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.|