In this post I reminded you all that I’m involved with LexCheck, the contract-checking software.
Part of the challenge in developing LexCheck has been determining what we tell the software to do.
For one thing, I’m acutely aware that there’s a difference between your electing to consult A Manual of Style for Contract Drafting and my blog posts and my in effect whispering in your ear as you’re reviewing a draft. In the former circumstance, you’re on my turf; in the latter, I’m on your turf, so LexCheck’s error messages can’t be as categorical as my published guidelines. It’s a matter of tone and emphasis, rather than compromise.
Also, there’s the question of whether LexCheck should flag an issue at all.
That brings us to promptly. Yes, it’s vague, and vagueness can result in dispute. You can end up in a fight over whether you did something promptly enough.
But promptly is an essential contract usage. If the future is sufficiently unclear, it might be that you can’t be precise—that promptly is the most sensible option.
So with LexCheck, we have a choice—have it flag promptly, at the risk of getting a bunch of “false positives,” or don’t flag it.
I’m inclined to flag it, with the error message simply reminding the user that it’s best to precise, if the circumstances allow it. If users find that message more annoying than helpful, they can turn it off for purposes of review of that document.