Keep the SBA Rule, Your Procedure, and the Evidence Aligned
Controlled context
- SBA requirements
- Lender policies and procedures
- Loan and servicing evidence
- Version and effective-date context
Executable checks

Inspect the basis
- Cited finding
- Computed verdict
- Review required
The Rule, the Procedure, and the File Have to Hold Together
SBA lending programs add program-specific requirements to the lender’s own credit, closing, servicing, and documentation practices. Those requirements and procedures can change over time, while later review may ask what applied and whether the file supports the action.
- SBA requirements come from SOPs, procedural notices, forms, and program guidance that can change over time.
- Lender policies, procedures, checklists, and training have to reflect the requirements that apply to the work being performed.
- Origination, closing, and servicing actions depend on documentation that may need to explain the decision later.
- Later lender review or guaranty-purchase preparation can require reconstructing what applied and what evidence supported the action.
Governing SBA context
- Applicable SBA SOPs
- Program notices and forms
- Version and effective-date context
Lender controls
- Credit policy
- Closing and servicing procedures
- Checklists and approvals
Evidence record
- Credit analysis
- Loan-action documentation
- Supporting file evidence
The answer depends on the connection between the requirement, the lender process, and the evidence for that action.
What SBA Lending Teams Can Do With Hextropian
Keep Procedures Aligned
Compare controlled SBA lending procedures against the applicable requirements. See which requirements are supported, where support is missing, and what still needs review, with the source evidence and date context attached.
Ask What Applied at the Time
Ask which requirement, version, or procedure applied to an earlier origination or servicing action. Hextropian answers from cited controlled sources and preserves effective-date and what-was-known-when context.
Reconstruct the Record for Review
Assemble exportable, independently verifiable evidence packages from the agreed source set, controlled procedures, and selected records to support internal review, SBA review, or guaranty-purchase preparation. Preserve source provenance, version and effective-date context, and an inspectable derivation. Where evidence or formal support is insufficient, return a review state that identifies what is missing.
See What the Procedure Supports, and What Still Needs Review
Substantive results carry the governing source, evidence, and reasoning needed to inspect the basis. If support is incomplete, the platform returns a review state that identifies what is missing.
What the evidence shows
- What was checked
- Does the servicing procedure require the business reason and supporting documents to be retained for the action?
- Result
- Review required
- Governing requirement
- The loan file must retain the justification and supporting documents for the servicing action.
- Evidence reviewed
- The procedure requires manager approval but does not state which justification or supporting documents must be retained.
- Why review is needed
- The required file documentation is not demonstrated in the procedure.
- Next step
- Provide the servicing checklist or update the controlled procedure to specify the required evidence.
From SBA Requirements to Evidence-Backed Results
Define the SBA Source Set and Question
Agree the applicable SBA sources, lender procedures, selected records, date context, and compliance questions to be evaluated.
Turn Approved Requirements Into Executable Checks
Regulatory text is structured as requirements, and approved requirements are compiled into versioned, executable checks.
Review the Result and Evidence
Evaluate the controlled procedure and supporting record. Review the cited finding, computed verdict, or review state with the evidence and derivation attached.
Computed Results, Not Plausible Answers
SBA lending questions can be revisited after the original decision, sometimes under a different version of the rules. General-purpose AI can help read and draft. Hextropian anchors substantive outputs to cited source evidence and deterministic validation. HexReason computes formal results from structured facts using deterministic AI.
The same facts, evaluated deterministically, produce the same verdict and derivation. When the evidence or formal support is not there, Hextropian returns a review state instead of filling in the gaps.
Controlled sources + executable checks + procedures and records move through HexReason and produce Cited finding, computed verdict, or review state. Two identical runs are shown producing the same result.
Run 01
Controlled sources + executable checks + procedures and records
Run 02
Controlled sources + executable checks + procedures and records
HexReason
Deterministic validation

Result 01
Cited finding, computed verdict, or review state
Result 02
Cited finding, computed verdict, or review state