Separate Drafting and Review for Payments

Payment reminders combine a repeatable writing task with relationship, dispute and escalation risk. The workflow described here uses separate contexts: a drafting step receives the approved case fields, while a review step receives the proposed text and the communication policy.

The control pattern

The reviewer does not inherit the drafter's hidden reasoning or an instruction to achieve collection. It checks the text for threats, unsupported promises, pressure outside policy and missing context.

Capability creates the strongest boundary

The workflow has no outbound send function. A specialist copies or approves the reviewed text in the authorised communication system. The application can prepare and log; a person controls contact.

This boundary is easy to inspect in code and permissions. It also gives the account owner a place to pause a case for dispute, reconciliation, promise to pay, complaint or another hold state.

The policy and source state come first

Before modelling, define:

• case states that prevent drafting;
• facts the drafter may use;
• approved tone and calls to action by stage;
• prohibited threats and unsupported consequences;
• owner for disputes, payment promises and formal correspondence;
• review result, correction reason and escalation path.

Run deterministic checks for reconciled payment state, dispute, hold and contact history before either model receives the case.

Review the reviewer

Build an evaluation set from the organisation's risk categories, with personal data removed. Include ordinary reminders, partial payments, disputed records, a previous promise and cases that must be held.

Ask finance, account and communications owners to label the expected result. Report harmful text released, safe text held, reviewer reason and specialist edits as separate measures. A high hold rate can reveal missing case context or a policy that needs clarification.

After launch, inspect held cases and recurring edits. Feed policy changes through an owner and version record; let reviewers surface gaps without silently rewriting policy.

The operating measures

Track preparation time, source-state errors, review holds, specialist edits, cases paused before drafting and communication outcomes that the account team can verify. Collection results depend on terms, customer decisions and account context, so use message metrics as process signals.

Release sequence

1. reconcile source data and define hold states;
2. run drafting and review in a no-send environment;
3. compare review decisions with specialist labels;
4. enable the workflow for one approved message category;
5. review edits, holds and incidents with the policy owner.

The pattern applies to any correspondence where wording can affect money, contracts or reputation. Separate preparation, review and sending so each responsibility remains visible.

Review the related receivables workflow or discuss a controlled communication process.