> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/jurisphere-guide/handbook/mergers-and-acquisitions/overview.md).

# Overview

M\&A work runs on iteration. Term sheets evolve. Definitive documents go through many turns. Conditions precedent stack up. Jurisphere keeps the moving parts coordinated and citation-grade while the partner's judgement remains on the trade-offs.

## The shape of the work

A typical M\&A mandate moves from term sheet through definitive documents to closing, with regulatory pathways running in parallel. Jurisphere ships an upgraded term-sheet workflow that drafts a strong baseline. For serious deals, [Custom Workflows](https://jurisphere.gitbook.io/jurisphere-guide/creating-custom-workflows) uploaded from your firm's term-sheet template adapt better: they replicate your firm's structure, defined terms, and house style.

* The [Word Add-In](https://jurisphere.gitbook.io/jurisphere-guide/word-add-in/overview-of-the-word-add-in) is where most definitive-document drafting actually happens.
* SPAs, SHAs, and ancillaries live in Word; the Add-In drafts, edits, redlines, and applies [Review Playbooks](https://jurisphere.gitbook.io/jurisphere-guide/word-add-in/review-playbooks) in-place with bubble-comment rationale.
* [Research](https://jurisphere.gitbook.io/jurisphere-guide/research/overview-of-the-research-tool) with full multi-jurisdictional databases drives the regulatory pathway.

Pricing mechanics, indemnity caps, walk-away positions, and the negotiation strategy stay with the deal team.

## How the work moves

A mandate moves through the stages below. The detailed walkthrough — with the tools each stage uses and the call the lawyer still owns — is on the next page.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>M&#x26;A - Pre-Transaction</strong></td><td>Research transaction structure options.</td><td><a href="/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#ma-pre-transaction">/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#ma-pre-transaction</a></td></tr><tr><td><strong>M&#x26;A - Transaction Documents</strong></td><td>Draft Share Purchase Agreement (SPA).</td><td><a href="/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#ma-transaction-documents">/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#ma-transaction-documents</a></td></tr><tr><td><strong>M&#x26;A - Regulatory</strong></td><td>Research regulatory approvals required.</td><td><a href="/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#ma-regulatory">/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#ma-regulatory</a></td></tr><tr><td><strong>M&#x26;A - Closing</strong></td><td>Prepare closing checklist and agenda.</td><td><a href="/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#ma-closing">/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#ma-closing</a></td></tr><tr><td><strong>M&#x26;A - Post-Closing</strong></td><td>Monitor post-closing covenants.</td><td><a href="/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#ma-post-closing">/pages/1e56e8461c5afe38c309eb7e487baf844b634d11#ma-post-closing</a></td></tr></tbody></table>

{% hint style="success" %}
**The shape of the time saved.** Across the deal, the workspace records what each lawyer drafted, when each clause moved, and which regulatory authority was relied on at each point. The structuring calls remain with the partner. The bookkeeping is automatic.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.jurisphere.ai/jurisphere-guide/handbook/mergers-and-acquisitions/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.