Answer Hub · Audit & compliance

Why do email-based draw workflows create audit issues?

Reviewed by
Reviewed by RAZE
Last reviewed

Short answer

Email moves files but keeps no single record of a draw. Reports and photos scatter across inboxes, versions multiply, forwarded photos can lose their metadata and their link to budget lines, and approvals sit in reply threads. When an auditor or examiner asks who approved which draw, when and on what evidence, someone has to piece the answer back together.

Where the gaps come from.

Email is a reasonable way to send a file. The trouble starts when the inbox becomes the place the draw file lives.

  • Scattered attachments. The request, the report, the photos and the approval arrive in separate messages, often in different inboxes, and the file holds only what someone remembered to save.
  • No single status history. A message shows when it was sent, not where the draw stood. Nothing records in one place when the inspection was ordered, submitted, approved or sent back, or by whom.
  • Version confusion. A corrected report sent as a new attachment sits beside the original, and a reviewer later has to work out which one supported the funding.
  • Photos cut loose. Photos that are downloaded, resized or pasted into a document can lose the date, time and location data they carried. A batch of photos in one message also carries no link to the budget line each one supports.
  • Approvals in threads. An approval written as a reply is hard to tie to a specific report version and draw amount.
  • Retention. Records kept in individual mailboxes follow mailbox settings rather than the lender's retention schedule, and they can leave with the employee. How long to keep draw records is a question for lender policy and counsel.

None of this means a lender's reviews were wrong. It means the evidence that they were right is harder to produce.

Why it matters for lenders.

FDIC rules require the real estate lending policies of FDIC-supervised banks to include documentation, approval and reporting requirements (12 CFR § 365.2). The FDIC's construction and land development procedures ask whether management reviews written inspection reports before funds are released, and the OCC's Comptroller's Handbook lists dual approval of loan disbursements and independent review of the records among effective controls. Showing those steps from an inbox takes reconstruction, one draw at a time. See what makes an inspection record audit-ready and how examiners review construction loan monitoring.

How RAZE handles it.

RAZE keeps the inspection side of each draw in one place. Lenders order in the Ordering Engine, and inspectors capture and submit the report from the field in the RAZE Mobile App. Photos carry GPS coordinates and date and time stamps and link to the draw sheet line items they support, two of the links a chain of evidence depends on. The status history records each change from Inspection Ordered to Lender Approved or Lender Rejected, with who made it and, on a rejection, the reviewer's reason. RAZE integrates with existing construction loan administration workflows; the funding decision stays with the lender.

Sources

Primary sources only. Where a figure appears on this page, it comes from one of these.

  1. 1.Construction and Land Development Lending (Core Analysis Procedures, 10/25)FDIC · fdic.gov
  2. 2.12 CFR § 365.2, Real estate lending standardsElectronic Code of Federal Regulations · ecfr.gov
  3. 3.Commercial Real Estate Lending (Comptroller's Handbook)OCC · occ.gov

See the workflow behind the answer.

RAZE standardizes how draw inspections are ordered, dispatched, captured and delivered, inside the loan administration workflow a lender already runs.

Request a Demo