How Q&A works in Jurimesh

For one question during due diligence, you needed multiple tools:

• A data room to find the document and the source clause.

• An Excel tracker to log the question.

• An email to send it to the other side.

• Or even a sticky note ;)

Then you waited, copied the answer back into Excel and probably lost the thread.

Jurimesh Q&A changes that. Every question, from detection to resolution, stays inside the platform. Linked to the source clause, tracked in real time, and visible to your team.

Here's how it works.

The scenario: an unlawful dismissal buried in the data room

You're reviewing the data room for the acquisition of TechVista, a mid-sized Belgian tech company. Hundreds of documents. Contracts, board minutes, financial statements, HR files.

One of them is an internal email from the HR department to the legal team, subject line: "RE: Q4 workforce planning, updated headcount overview." It reads like a routine update. Headcount numbers, open positions, payroll indexation, fleet policy changes. The kind of email you scan and move past.

But buried in the fifth paragraph, between a grievance about workload and a note about board planning, sits a single passage: "Following her dismissal, Ms. Van Houten's counsel alleges the termination constituted unlawful dismissal. No prior formal warning was issued."

That's a risk. Hidden in an email that has nothing to do with litigation. You need to know the current status of this claim before you can close the employment section of your report.

Here's what happens next.

Step 1: Jurimesh flags the risk

You upload the email to Jurimesh, or sync it from the data room. Jurimesh runs its analysis and flags the unlawful dismissal claim as a risk under the employment section.

The source clause is highlighted directly in the document. No need to copy-paste a reference or describe the issue in a separate tracker. The risk is linked to the exact paragraph, section 3.2.1, where the allegation appears.

You now have a risk on your list. But you don't yet have enough information to assess it.

Step 2: Send the risk to Q&A

You click "Send to Q&A." and draft the: "What is the status of the ex-employee's unlawful dismissal claim?"

Now the question is ready. But it's not sent yet, it goes into a batch first.

Step 3: Send the batch of questions out

You probably collected several questions over the course of your review, some about missing documents, some about unclear clauses. You group them into a batch. In this case, the batch is called "Seller", because these questions are all directed at the seller's counsel.

You could just as easily create a separate batch for a tax advisor or a financial expert. The grouping is yours to decide.

When you're ready, you send the batch. It gets locked. The counterparty, in this example, Mark Jacub, receives an invite to log into Jurimesh and respond. Every question in the batch gets a status: pending.

Your internal comments and priority levels stay invisible. The other side only sees the questions and the source document.

Step 4: The counterparty answers – inside Jurimesh

The counsel of the seller, Mark, logs into Jurimesh and sees the open batch. He navigates to the question about the Van Houten dismissal claim and replies directly: "Resolved through mutual settlement. All claims fully released."

He attaches the supporting document,"Settlement Agreement Josephine.pdf", right there in the platform.

On your side, the response appears immediately. You can view the answer, open the attached settlement agreement, and see the original source clause, all without leaving Jurimesh.

Step 5: Resolve and report

You review Mark's answer and the settlement agreement. The claim is resolved. All claims fully released. You now have what you need.

You mark the question as solved. From here, you decide the next step: archive it or add the finding to your due diligence report. The settlement agreement enters the data room. The issue closes. Your progress bar updates.

One continuous thread, from a flagged clause in an HR email to a resolved question with supporting evidence, fully traceable.

Conclusion

The old workflow for this single question looked like this: find the email in the data room, copy the relevant clause into a Word file, log the question in Excel, email it to the counterparty, wait for a reply, download the attachment, go back to your review tool to verify the clause, update the Excel tracker, close the loop.

That's nine steps across four tools. For one question.

In Jurimesh Q&A, it's five steps in one place. Every question traces back to its source clause. Internal and external communication are clearly separated. The counterparty answers where the question lives. And when it's resolved, the answer can flow directly into your report.

Ready when you are.