Charcoal runs your loan procedures as approved playbooks inside the LOS, the verification portals, AUS, and the loan file. It does the rules-based work and stops when an underwriter needs to decide.
Above: one prior-to-close employment condition, worked to the procedure. The verification comes back under a different employer name, so the run stops, routes the call to the underwriter, and clears the condition with the evidence filed.
The run above is one playbook. Most of the work between intake and investor delivery takes one of a few shapes. A playbook fits any of them.
Anything between the borrower package and underwriting: classifying and indexing documents, keying the 1003, chasing what is missing. Shown: a package indexed into the Encompass eFolder, with the one document that never arrived requested.
Anything worked from a checklist against the closed file: your QC plan, investor pre-purchase reviews, HMDA scrubs. Shown: a Closing Disclosure re-verified against the QC checklist, with one exception routed.
Anything you wait on after closing and chase per document: recorded deeds and assignments, final title policies, investor delivery. Shown: a county recorder checked until the deed records, then filed and delivered.
Charcoal reads the documents, works the portals, and updates the systems of record your team already uses.
If your team can sign in to it,
Charcoal can work in
it.
You bring the procedure your team already follows: a condition matrix, a QC checklist, a written walkthrough. Charcoal turns it into a playbook, and your team reviews and approves that playbook before anything runs.
No. Charcoal is not a system of record and there is nothing to migrate. Your LOS stays your LOS, your documents keep filing where they file, and your vendors stay your vendors. Charcoal signs in to those systems the way your team does and works inside them.
Days, not quarters. A first playbook is typically in production within 24 to 48 hours of the procedure being handed over. There is no integration to build and no data to move, so the work is writing the procedure down and approving it.
No. Playbooks gather documents, work portals, and file evidence. Any step that needs judgment routes to the person you name, and the run waits for their decision before it continues.
The run stops at that step and routes the call to the person you name, with both sides shown: the paystub against the verification, the note against the lock, the 1003 against the credit report. Their decision is recorded with the rest of the run before it continues.
Playbooks work the same screens your team does. Encompass, MeridianLink, Byte, or a proprietary system: if your team signs in to it in a browser, a playbook can work in it, alongside DU and LPA, The Work Number, FHA Connection, MERS, and the documents in the loan file.
Every run keeps a step-by-step record: what was checked, what was found, and who signed off. The evidence files with the loan, so audit and investor questions get answered from the record, not from memory.
It doesn’t decision loans, and it doesn’t improvise. If a run hits something the approved playbook doesn’t cover, it stops and hands the file to a person.
Independently audited controls.
Controls for regulated data.
Covered deployments with access and audit controls.
Bring the condition matrix or the QC checklist your team works from today. We’ll show you the same procedure running as a playbook in your systems, evidence and all.
Encompass 
MeridianLink 
The Work Number 
Desktop Underwriter 
Loan Product Advisor 
FHA Connection 
MERS 
DocMagic 
Optimal Blue 
CoreLogic