Receive
Files arrive through borrower upload, analyst upload, bulk upload, or project email without leaving the project record.
§ Platform - CORE Workflow
CORE Workflow manages the borrower file.
CORE Workflow coordinates pipeline, borrower portal, collection templates, project email, uploaded files, staged workflows, forms, data room, internal review, and file routing around one project record.
Required docs, inbox files, forms, and workflows move together.
A project can carry multiple program-scoped workflows - acquisition, B&I, bridge, C-PACE, servicing, diligence - while files are classified, attached to requirements, routed to the right entity, and preserved in one activity history.
Required docs, staged workflows, and inbound file routing§ Workflow Layer
From inbound file to controlled requirement.
Classify
CORE identifies document type, entity, fiscal year, downstream usage, and processing status before the analyst has to hunt.
Match
Unattached inbox files can be matched to the right requirement, linked to a suggested collection item, or used to add a new requirement to the workflow.
Run parallel workflows
One project can carry multiple program-scoped collection paths, each with its own stages, entity assignments, and status view.
Review
Analysts keep notes, markups, context, status decisions, and follow-up tasks attached to the same collection record.
Preserve
Attachments, status changes, stage releases, and analyst actions become part of the project history.
§ Fit
What makes it more than a CRM
CORE Workflow is the landing product for teams replacing pipeline, portal, collection, and file-management sprawl.
01
Pipeline, companies, contacts, custom stages, and borrower-file activity
02
Project inbox for files sent by email, portal, or internal upload
03
Entity-scoped required documents, forms, tasks, and review states
04
Many program-scoped workflows under a single project record
05
AI-assisted file classification and requirement matching
06
Staged workflow release so borrowers only see what is ready
07
Document notes, markups, analyst context, and attachment history
§ Path
How collected files become underwriting evidence
Build the workflow
Configure the Loan Program, Base Package, optional Add-on Packages, stages, entity assignments, visibility, and review paths before release.
Collect the files
Borrowers and analysts upload through the portal, project inbox, or internal upload while every file stays inside the borrower record.
Understand and route
Once approved for processing, CORE identifies document type and entity, extracts facts, and routes the file to the right collection item, workflow stage, and downstream use.
Create reusable evidence
CORE preserves the source file and, where useful, creates linked evidence artifacts from it: file summaries, structured key facts, and metadata.
Underwrite from evidence
Those evidence artifacts feed spreading, policy and risk analysis, and credit memo generation while every claim stays traceable to the uploaded source.
§ Next Step
Replace the package chase with a controlled file.
CORE should make the borrower file feel organized, routed, and defensible before the AI ever drafts a sentence.