Building a legal or compliance taskforce: roles, ramp-up and governance

Short answer: Staff a compliance taskforce in three steps: appoint the team lead first, then quality control, then the reviewers, and ramp up in waves rather than at full strength on day one. Before the ramp-up, put written review instructions, system access and reporting to in-house compliance or legal in place. One example from practice: a KYC taskforce of 8 FTE under staff leasing completed a remediation project at a financial institution in Switzerland in 10 months.

This guide is for heads of compliance, MLROs, general counsel and project owners in Switzerland and Germany who need a team at short notice for a remediation, a review or a regulatory project. It covers roles, ramp-up, onboarding, governance and wind-down of a legal or compliance taskforce.

When do you need a taskforce rather than individual professionals?

A taskforce makes sense when a clearly defined task with high volume and a fixed deadline needs more capacity than the line organisation can provide alongside day-to-day work. Typical triggers are:

• KYC and AML remediation: updating client files, closing gaps, working through transaction monitoring alerts.
• Audit findings: measures from an internal or external audit must be implemented and evidenced on time.
• Contract and document reviews: such as regulatory repapering, change-of-control reviews or due diligence.
• Internal investigations: reviewing large document sets after a whistleblowing report.
• Regulatory implementation projects: new rules such as DORA, NIS2, the EU AI Act or AML/KYC requirements call for inventories, gap analyses and updated documents.

For a single gap, such as a vacancy, one professional is usually enough. A taskforce needs roles, a shared review standard and governance. To size a contract backlog first, see clearing a contract review backlog.

Role model: who does what in the taskforce?

A taskforce works with four roles: team lead, quality control, reviewers and an in-house project owner. Interim professionals can take on the first three; the in-house project owner always stays within the company.

Ratio of reviewers to quality control

There is no fixed ratio; it depends on the error rate, risk and regulatory expectations. A staged approach works well: in the first weeks, quality control re-checks a high share of cases, later only a risk-based sample. Assumption for illustration: in a team of six reviewers, one person can cover quality control after the start-up phase if the rework rate stays low. Test this against your own error rate.

Ramping up in waves rather than at full strength on day one

Ramping up in waves reduces rework, because the review instructions are tested with a small group first. A proven sequence:

1. Wave 0, preparation: the team lead and quality control start first, work test cases and refine the review instructions.
2. Wave 1, pilot: two or three reviewers work live cases. Quality control re-checks a high share.
3. Wave 2, expansion: once the review instructions are signed off, more reviewers join and are trained together.
4. Wave 3, full capacity: the team works at full strength; the quality control sample is reduced on a risk basis.
5. Wind-down: as the remaining volume falls, the team is reduced step by step.

At Alpinum Solutions, selected profiles are usually available within 48 hours; the start date is agreed between the company and Alpinum. The actual start mostly depends on contracts, security screening and system access, so plan these steps in parallel with selection.

Onboarding in blocks: access, training, review instructions

Onboarding in blocks means that everyone in a wave starts on the same day with the same documents and the same training. This saves in-house time and ensures a consistent review standard. Use this checklist to prepare:

• Access: user accounts, roles and permissions for core systems, document storage and case management, requested before day one wherever possible.
• Confidentiality: non-disclosure undertakings, rules on devices, downloads and place of work.
• Co-determination (Germany): where there is a works council, it must be involved under section 99 BetrVG before leased professionals start, and the client must show it the provider's licence declaration (section 14(3) AÜG). Plan this step for every wave.
• Training: project objective, regulatory background, internal policies, system use, examples of good and deficient cases.
• Review instructions: review steps, output template, definition of "done", reasons for escalation.
• Contacts: who answers subject-matter questions, system questions and questions about individual clients or contracts?
• First week: short daily stand-up, high re-check rate, collected questions feed into the review instructions.

Governance: reporting, escalation and decisions that stay in-house

The taskforce is governed through weekly reporting and a clear escalation rule; decisions with regulatory or legal consequences stay within the company. Under staff leasing, the company generally holds the right to give professional instructions and the professionals are integrated into its organisation. Under freelancing, professionals deliver independently within the agreed mandate.

What lean weekly reporting covers

• cases closed per week and remaining volume, by case type or risk class
• forecast to project end based on current throughput
• rework rate from quality control and the most common error types
• open escalations with their age and owner
• risks to the deadline, such as missing access or pending decisions

Decisions that stay in-house

• risk rating of clients or contracts where it deviates from the review instructions
• exiting client relationships, reports to authorities and communication with the supervisor
• changes to the review instructions and sign-off of the project result

Interim professionals can take on formal functions such as MLRO or compliance officer with regulatory responsibility, depending on the company's requirements and the rules in Switzerland or Germany. For the MLRO role, regulatory restrictions may rule out an external mandate or require staff leasing (Personalverleih, the Swiss term). In Switzerland, a financial intermediary may appoint external persons as its anti-money laundering unit only if an internal unit is not possible or disproportionate because of its size or organisation (Article 25(4) AMLO-FINMA). In Germany, the appointment of the money laundering reporting officer must be notified to the supervisor in advance (section 7(4) GwG). Clarify this before the start.

Wind-down and handover

A taskforce ends in an orderly way when the remaining volume, open escalations and documentation are handed over to the line before the last working day. Start planning the wind-down as soon as the remaining volume falls below the capacity of the coming weeks.

1. Release reviewers step by step, starting with those who joined last.
2. Keep quality control and the team lead until the end.
3. Document remaining cases, open questions and special cases in a handover list.
4. File the review instructions, lessons learned and metrics as a closing report.
5. Revoke access and collect devices and documents.

If an ongoing task follows, such as periodic client reviews, part of the team can stay on as continuing support. Discuss this option early so that knowledge is not lost.

Example: KYC taskforce of 8 FTE over 10 months

In 2025, a financial institution in Switzerland needed capacity for KYC remediation at short notice. Alpinum provided a taskforce of 8 FTE: compliance officers including a team lead, all working 100 %, under staff leasing. The team handled KYC remediation, KYC file reviews, transaction monitoring, alert handling and documentation. The team lead reported to in-house compliance. Profiles were available within 48 hours; the team started around two weeks after the engagement. The project was completed within 10 months. The full KYC taskforce case study describes the starting point and approach. For detailed planning, see planning KYC remediation with interim specialists.

Limits and risks

• Accountability stays in-house: the taskforce works and documents cases; sign-off, risk decisions and communication with the supervisor remain with the company.
• No legal advice: Alpinum provides professionals and is not a law firm. High-impact interpretation questions may need outside counsel.
• Ramping up too fast: starting at full strength on day one often creates rework. The pilot saves that time.
• Access as a bottleneck: missing accounts delay the start more than selection does. Request them early.

FAQ: compliance taskforce staffing

How large should a taskforce be?

Size follows from volume, time per case and the deadline. Measure the time per case in a pilot, multiply it by the total volume and divide by the available weeks and the productive hours per person. Add the team lead and quality control. Start smaller and expand after the pilot, once the review instructions are stable and the rework rate is known.

Who leads the taskforce?

Day to day, a team lead with experience in the subject plans the work, allocates cases and reports. Responsibility for objectives, scope and decisions of principle stays with an in-house owner, usually the head of compliance, MLRO or head of legal. This split creates clear escalation paths and a clean sign-off at the end.

How quickly can a team start?

At Alpinum, selected profiles are usually available within 48 hours. The start date is agreed between the company and Alpinum and depends on availability, contracts, security screening and system access. In the KYC taskforce example, the team started around two weeks after the engagement, with the team then working at 100 %.

Staff leasing or freelancing for a taskforce?

Both models work. Staff leasing fits when the professionals should be integrated into your organisation and receive your professional instructions, for example when they work in your core systems. Freelancing fits clearly defined work packages delivered independently under a mandate. Mixed teams are possible where the tasks allow it.

How do I prevent knowledge loss after the project?

Make documentation part of the brief from the start: maintained review instructions, a decision log, a handover list and a closing report with metrics. Keep the team lead and quality control on the project until the end. If a follow-on task exists, part of the team can stay as ongoing support.

Next step

Describe the task, volume, deadline and the roles you need. Alpinum Solutions provides legal and compliance professionals through staff leasing and freelancing, from a single person to a project team with a team lead.

• Backlog, review and investigation
• AML and KYC remediation
• Planning KYC remediation
• Discuss your needs

Last updated: 30 October 2026.