It can suggest. It does not quietly decide.
Bring participant rosters, survey exports and study files together by ID, while every questionable match stays visible for you to review. Processing stays on your Mac.
Five steps, in the same order every time, with the review step in the middle rather than bolted on at the end.
Formatting cleanup and possible near-ID matches stay visible until you approve them. If a cleanup would create a duplicate ID, the app blocks it rather than guessing. Your base table defines who belongs in the final dataset, and IDs found only in source files are reported, not silently added as new participants.
Most of the work in preparing study data is not the merge itself. It is everything that has to be true before the merge is safe.
Files are processed locally. Research data is never uploaded to IMPLEMON or to a third party, and the app works offline.
A participant ID has an extra zero. One export has trailing spaces. Another file contains a duplicate. Two columns share a name but not the same values. A normal merge turns all of that into bad data without saying anything.
Which of these decisions is the software actually entitled to make?
Surface, do not decide. Anything ambiguous becomes a review step rather than a silent fix.
The app is slower to use than one that just merges, and that is the point. A cleanup that would collide with an existing ID is refused outright, because a blocked merge costs an afternoon and a wrong one costs a paper.
How much of the review can be remembered between studies without the memory itself becoming a source of silent decisions.
A merge you cannot explain is not a result.
Cleaner merge. Clearer decisions.