Each party instructs their collaboratively trained lawyers individually
You and your lawyer will discuss what you both need in order to prepare for the first joint “four way meeting”.
Depending on the issues and the information gathered at the initial meeting and lawyer/lawyer discussion.
There should be some discussion between lawyers as to whether other professionals are required to assist. These can include an IFA or Tax or Pension expert, or a child therapist or family consultant if at this point this is considered. The two lawyers together with the other professionals form your collaborative team. The team will communicate with one another to plan how their services will be best utilised.
The two lawyers will have initial discussions with each other either over the phone or face to face in order to plan for the meetings.
At the first four way meeting.
The lawyers will make sure you both understand that you are making a “binding” commitment to work out an agreement without going to court and that by entering into this process it prevents either lawyer from representing either party in court process.
Essentially if the process breaks down, both parties will have to instruct new lawyers.
Both you and your former partner will sign a “Participation Agreement” and often both parties will be asked to provide “anchor statements” which is the parties promise on how they will conduct themselves in the meetings and how they would like the outcome to be reached.
Discussion will then move to the topics and issues that need to be decided and from that an agenda for the next meeting will be agreed. Usually this will be the end of the initial meeting. Often only a few topic areas will be on the agenda in any one meeting and meetings will not go on beyond 2 hours generally as it can be tiring emotionally for both parties.
Subsequent meetings take place.
An agreement is reached on those issues and recorded in minutes which are typed up and distributed to all parties and the team within 48 hours of the meeting. Any corrections are made and the minutes finalised with agreements recorded clearly.
During meetings, lawyers can often give legal advice in front of everyone or explain how the law works, or case law decisions which can help break any impasse. If both lawyers broadly agree with the other’s synopsis it can aid resolution and bring agreement quickly.
These meetings will continue until all matters are resolved.
The final meeting.
In this meeting documents detailing the agreements reached will be signed and the lawyers will guide both parties through anything else that needs to be done in order to promote smooth implementation. A timetable of implementation is often drafted as a guide for the parties and the lawyers will explain how to put the arrangements into a legally binding agreement.
If you would like to know more about this process or feel this could be something you and your partner would benefit from, please contact Matt Clemence at [email protected] or telephone Ipswich 01473 213311 or Colchester 01206 584584, where Matt will be happy to speak with you.
Subscribe Now for Newsletter and Updates
|_zcsr_tmp||Zoho - This cookie is necessary for the login function on the website.|
|bcookie||2 years||This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page.|
|collect_chat_launcher_load||1 month||This cookie is set by the provider Collect.chat. This cookie is used for enabling the chat function on the website.|
|collect_chat_page_load||1 month||This cookie is set by the provider Collect.chat. This cookie is used for optimizing the chat-box functionality by recognising the user.|
|kerseys-_zldp||1 year||This cookie identifies the unique visitors for the website, www.kerseys.co.uk for Zoho Live Chat functionality.|
|kerseys-_zldt||1 day||This cookie identifies unique visits for a visitor in the website, www.kerseys.co.uk for Zoho Live Chat functionality.|
|lang||This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website.|
|lidc||1 day||This cookie is set by LinkedIn and used for routing.|
|ypsession||1 day||For Yumpu PDF viewer.|
|yumpu_slc||7 days||PDF viewer|
|_ga||2 years||This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.|
|_gat_UA-46814924-1||1 minute||This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.|
|_gid||1 day||This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.|
|_hjAbsoluteSessionInProgress||30 minutes||This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.|
|_hjFirstSeen||30 minutes||This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.|
|_hjIncludedInPageviewSample||30 minutes||This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.|
|_hjTLDTest||session||When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.|
|vuid||2 years||This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website.|
|_fbp||3 months||This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.|
|AVPUID||1 year||imagazine.advertserve.com Used to identify the visitor across visits and devices. This allows the website to present the visitor with relevant advertisement - The service is provided by third party advertisement hubs, which facilitate real-time bidding for advertisers.|
|b3e783bb62||This cookie is set by the provider Zoho. This cookie is used for collecting information on user interaction with the web-campaign content. This cookie helps the website owners to promote products and events on the CRM-campaign-platform.|
|bscookie||2 years||This cookie is a browser ID cookie set by Linked share Buttons and ad tags.|
|fr||3 months||The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin.|
|MUID||1 year 24 days||Used by Microsoft as a unique identifier. The cookie is set by embedded Microsoft scripts. The purpose of this cookie is to synchronize the ID across many different Microsoft domains to enable user tracking.|
|NID||6 months||This cookie is used to a profile based on user's interest and display personalized ads to the users.|
|test_cookie||15 minutes||This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.|
|UserMatchHistory||1 month||Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences.|
|_hjid||1 year||This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.|
|AnalyticsSyncHistory||1 month||No description|
|cookielawinfo-checkbox-functional||1 year||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-others||1 year||No description|
|S||1 hour||No description|