Services / Drafted Revisions

When a rule hits, we draft the change.

For high-impact findings, we generate before/after revisions of the affected policy sections.

Why this matters.

Knowing a rule affects a policy still leaves the rewrite work on someone's desk. A compliance officer who has identified the impact — who knows section 4.3 of the origination policy needs to be updated — still has to open the document, find the language, decide what the new language should say, and write it. That work often gets deferred. The finding sits in a spreadsheet. The policy stays stale.

The gap between "I know this needs to change" and "the policy has been changed" is where compliance risk lives. Drafted revisions close that gap by giving you a concrete starting point: here is the section, here is the proposed language, here is why. You don't have to start from blank.

What this looks like.

reglith.com/impact/r-9c2a

Drafted revision · Fee Disclosure Policy §3.2

Generated 12 minutes ago · Pending your review

Current

Overdraft NSF fees shall not exceed $5.00 per item, in compliance with the safe harbor provisions of 12 CFR 1026.4(b)(11), effective through December 31, 2024.

Proposed

Overdraft NSF fees shall not exceed $5.50 per item, in compliance with the amended safe harbor provisions of 12 CFR 1026.4(b)(11), effective January 1, 2026.

Rationale

Final rule raised the cap from $5.00 to $5.50 effective 2026-01-01.

How we do it.

01

Section-level structured diff

Revisions operate at the section level, not the document level. We identify up to five sections of your policy that are affected by the regulatory change, and for each one we show the current text, the proposed replacement text, and a rationale explaining the connection to the specific rule. You can see exactly what changed and why, without reading the whole document.

02

Review, edit, approve, or reject

The workflow has four actions: approve the draft as-is, edit the proposed text and then approve, reject with a note, or regenerate to get a fresh draft. Approvals and rejections are both recorded — the record of "we saw this and decided not to change it" is as valuable as the record of "we changed it."

03

Non-destructive approval

Approving a revision in Reglith stamps the decision but does not rewrite your policy file. Your source document — whether it lives in SharePoint, Google Drive, or a Word file on a shared drive — stays your source of record. Reglith tracks the decision; you apply the change. This keeps the audit trail clean and avoids a situation where two systems disagree about what your policy says.

What's in the product today.

  • CRITICAL findings get a draft revision generated automatically — no click required

  • MATERIAL and MINOR findings have an on-demand "Generate" button so you control when AI work runs

  • Each revision shows 1–5 affected sections with a before/after view and a rationale per section

  • Edit mode lets you adjust the proposed text before approving — edits are saved separately, original AI draft is preserved

  • Approval stamps the approver, the timestamp, and the approved text as a formal record

  • Rejection is also recorded — useful for cases where the AI suggested a change you consciously chose not to make

  • Approval does not overwrite your source policy document — you still apply the change yourself, which keeps your source of record clean

  • Multiple revisions can exist for one finding over time — re-generate as prompts improve without losing history

Close the gap between finding and fixing.