Inside a Moroccan In-House Legal Team: Workflows, Urgencies and AI

The in-house lawyer is the first line of defense, and often the most under-equipped.

A law firm sells legal work. An in-house legal department absorbs it. Everything the business does that has a legal dimension, every contract signed, every dispute that arises, every regulation that changes, every risk the board worries about, flows toward a team that is almost always smaller than the demand placed on it.

This article maps what an in-house legal team in Morocco actually does, day to day. Not the idealised version from the org chart, but the real version, where a one-line email from the CEO becomes a two-day analysis, and where the legal department is simultaneously a service desk, a risk function, and a strategic advisor.

Understanding this reality is the precondition for understanding where legal AI helps, and, just as importantly, where it should stay out of the way.

The seven flows of in-house legal work

An in-house legal team is not organised around cases the way a litigation firm is. It is organised around flows of work that arrive continuously, from every direction, at every level of urgency. Seven flows recur in almost every department.

1. Contracts. Inbound and outbound. NDAs, supplier agreements, client contracts, distribution agreements, leases, employment contracts, service agreements. This is usually the highest-volume flow, and the one most likely to overwhelm a small team.

2. Internal legal requests. The sales team needs a clause checked by Friday. HR has a termination question. Procurement wants to know if a penalty is enforceable. Marketing wants to run a promotion. These arrive as emails, chat messages, and corridor conversations, and they rarely arrive in a structured form.

3. Compliance and risk. Data protection under the CNDP, anti-money-laundering obligations, sector-specific regulation, internal policies, codes of conduct. This flow is steady, often invisible until something goes wrong, and increasingly demanding.

4. Litigation and external counsel. When disputes arise, in-house counsel rarely litigates directly. Instead, they instruct, brief, supervise, and manage external counsel, while keeping the business informed and the costs controlled.

5. Corporate and governance. Board resolutions, minutes of general meetings, corporate secretarial work, shareholder matters, group structure, statutory filings. This flow is rhythmic, tied to the corporate calendar, and unforgiving about deadlines.

6. Sector-specific regulatory work. Banking, insurance, telecoms, health, energy. Each regulated sector adds a layer of obligations, filings, and supervisory relationships that the legal team has to maintain.

7. Ongoing matters. The disputes, projects, and transactions that span months or years and require continuous attention rather than a single answer.

Seven flows, arriving in parallel, mostly unscheduled. That is the in-house reality.

The pains that come with the flows

Each flow brings its own friction, but a few pains are universal across in-house teams in Morocco.

Volume against headcount. The business grows faster than the legal team. More contracts, more requests, more regulation, same three or four people.

Urgency without context. Requests arrive with a deadline attached and no file behind them. "Can we sign this?" with a PDF and nothing else.

Dispersion. The relevant information is scattered across inboxes, drives, the contract management system that was never fully adopted, and the memory of whoever handled the last similar matter.

Bilingual load. A contract in French, a regulatory notification in Arabic, a board minute in one language referencing a document in the other. The cognitive overhead is constant.

Invisible knowledge. The department's most valuable asset, what it decided last time and why, usually lives in the heads of two or three senior people, not in any system.

The measurement problem. Legal departments are cost centres that are hard to measure. They get attention when something breaks, rarely when something is quietly prevented.

The changing role: from service desk to strategic function

For a long time, the in-house legal department was treated as a service desk. Send a request, receive an answer, move on. That framing is changing, in Morocco as elsewhere.

The reasons are structural. Regulation is increasing. Transactions are more complex. Boards are more aware of legal risk. Data protection has moved from a niche concern to a board-level topic. The cost of getting it wrong, in fines, reputation, and disruption, has risen.

As a result, the best in-house legal teams are moving up the value chain. Less time spent finding documents and producing first drafts. More time spent on risk strategy, on advising the business early rather than cleaning up late, and on the judgment calls that no system can make.

The constraint is time. A legal team buried in document retrieval and first-draft production cannot move up the value chain, because the low-value work consumes the hours that strategy requires. This is precisely the constraint that well-deployed legal AI is positioned to relax.

Where legal AI genuinely helps, and where it should not

Legal AI helps most where the work is high-volume, document-heavy, and judgment-light at the first-draft stage.

First-pass contract review against the company's own playbook, flagging deviations for a human to assess. Triage of internal requests, turning a vague email into a structured matter with the right documents attached. Search across the department's own history, so the answer to "what did we decide last time" takes seconds instead of relying on memory. First drafts of routine documents, memos, and summaries, always for human review. Timeline and deadline tracking across ongoing matters.

Legal AI should stay out of the way where judgment, strategy, and responsibility live. The decision to sign, to litigate, to settle, to escalate. The client-facing or board-facing final output, which carries the lawyer's name and the lawyer's responsibility. The strategic call that depends on knowing the business, the people, and the politics, none of which a model can fully see.

The principle is consistent with everything in this Academy. The lawyer does not disappear. The lawyer moves higher in the workflow, out of retrieval and first drafts, into judgment and strategy.

In Morocco and francophone practice

The Moroccan in-house context has distinctive features.

Regulated sectors are prominent. Much of Morocco's organised economic activity sits in banking, insurance, telecoms, energy, and increasingly health and technology. In-house teams in these sectors carry heavy regulatory loads and answer to supervisory authorities that expect rigour.

External counsel management is central. Many Moroccan in-house teams are lean and rely heavily on external cabinets for litigation and specialised work. A large part of the in-house role is therefore instructing, supervising, and controlling the cost and quality of external counsel, which is itself a document-heavy, coordination-heavy task.

Bilingual governance. Board minutes, general meeting records, and statutory filings move between French and Arabic. The corporate and governance flow is where bilingual precision matters most, because these are formal, durable, legally significant documents.

Reporting to the top. In Moroccan groups, the legal function increasingly reports close to the top, to the secretary general, the CFO, or directly to the CEO. This raises expectations. The legal team is asked not only to answer questions but to anticipate risk and to communicate it clearly to non-lawyers.

A Legal OS that fits the Moroccan in-house reality is therefore one that structures the seven flows, handles French and Arabic as equals, supports external counsel management, preserves the department's institutional memory, and produces output that a board can read.

Practical example

Consider a single day in the legal department of a mid-sized Moroccan industrial group in Casablanca. The team is three people: a head of legal and two counsel.

By 9 a.m., the head of legal has received a contract from procurement that needs review before a 2 p.m. signing, a question from HR about a contested termination, and a forwarded email from the CEO asking whether the group can exit a distribution agreement. By 10 a.m., a regulatory notification in Arabic has arrived from a supervisory authority with a response deadline. By 11 a.m., external counsel has sent an update on an ongoing litigation that needs to be summarised for the executive committee.

In a fragmented setup, the team spends most of the day in retrieval and triage. Finding the distribution contract and its amendments. Locating the company's position on similar terminations. Reconstructing the litigation file to write the summary. The strategic thinking, what the group should actually do about the distribution agreement, gets squeezed into the last hour, tired and rushed.

In a structured setup with a Legal OS, the contract review starts from the company's own playbook with deviations flagged automatically. The termination question pulls up the three prior similar matters in seconds. The distribution-agreement query opens the matter that already holds the contract, the amendments, and the prior external-counsel memo. The litigation update is summarised from a matter file that is already organised. The retrieval shrinks. The judgment expands.

The team is still three people. The work they spend their hours on is different.

This example is illustrative. Any specific legal output must be reviewed by qualified Moroccan counsel.

What this changes for Burhan

Burhan is designed to fit the in-house reality rather than to fight it.

That means structuring the seven flows into matters and requests rather than leaving them as loose emails. Triaging incoming requests into something workable. Preserving the department's institutional memory so that "what did we decide last time" is a query, not an act of remembering. Supporting the management of external counsel as a first-class workflow. Handling French and Arabic symmetrically. And producing output, with sources and an audit trail, that a general counsel can stand behind in front of a board.

The aim is not to replace the in-house lawyer. The aim is to give a small team the leverage of a larger one, by removing the retrieval and first-draft burden that currently consumes the hours strategy requires.

Key points

• In-house legal work flows through seven recurring channels: contracts, internal requests, compliance, litigation and external counsel, corporate and governance, sector regulation, and ongoing matters.
• The universal pains are volume against headcount, urgency without context, dispersion, bilingual load, and invisible institutional knowledge.
• The in-house role is shifting from service desk to strategic function, and time is the binding constraint.
• Legal AI helps most with high-volume, document-heavy, first-draft work, and should stay out of judgment, strategy, and final responsibility.
• In Morocco, regulated sectors, external counsel management, bilingual governance, and reporting to the top shape what good in-house support looks like.