> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myfundingmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Practice with sample files

> Create six synthetic files in a selected Location and practice the normal funding workflow.

Agency admins can open **Admin → Locations → Actions (three dots) → Sample files** for a Location. The menu also retains the links to Location details and the CRM.

Before adding files, verify that the Location’s CRM workflows exclude Contacts tagged **fm-sample-file**. The app blocks its own real credit pulls, messages, lender submissions, and charges for sample files. It cannot suppress workflows configured in the CRM. Sample Contacts have no phone number, use a reserved test email domain, and are created with Do Not Disturb enabled.

## The six files

| File | Starting point |
| - | - |
| Avery Morgan | New Applicant, ready for review |
| Jordan Ellis | New Applicant with a thinner credit profile |
| Casey Bennett | Applicant with an agreement sent |
| Taylor Reed | Client ready to submit for processing |
| Riley Parker | Client with card processing completed and results published |
| Quinn Hayes | Parked Applicant with a callback disposition |

Names begin with **\[Sample]**. Their reports use sanitized golden credit fixtures, synthetic identities, and dates shifted together to preserve credit history. Reports and agreements have downloadable sample PDFs. A completed Client demonstrates processing completion; no real funding or payment has occurred.

Open a sample Applicant or Client to view its stored credit report. Sample report IDs are supported directly; viewing a sample does not require a fresh credit pull.

## Practice the workflow

Use the normal file controls to review credit, re-run underwriting, approve an Applicant, edit a funding plan, and submit a Client to processing. The sample banner lets you simulate a signed agreement and a completed Processing Application. Sending an agreement produces a sample document; no signature request is delivered.

The files are created through the same underwriting, document, approval, agreement-conversion, and processing functions as normal files. Sample funding and report rows are excluded from dashboard financial totals and underwriting outcome calibration.

CRM credit-score, underwriting-decision, and report-ID fields are optional. Sample files keep their complete credit reports and workflow records in Funding Machine even when those CRM fields are absent. Available mapped fields are synchronized and checked; the Location still needs its Applicants and Clients pipelines and required stages.

## Retry or remove

The dialog shows each file’s progress and any failed step. **Retry unfinished step** resumes that file. Adding the pack again returns the existing run, so repeated clicks do not create another six Contacts.

Creation waits briefly for CRM searches to reflect new records and stage changes. The sample worker controls stage changes during setup; normal workflow automation resumes once the file is complete. If CRM synchronization still fails, the file remains unfinished and the dialog shows the error for retry.

If an earlier attempt stopped with a credit-field mapping error, use **Retry unfinished step** after the fix is available. Missing optional CRM credit fields no longer prevent creation.

To reset the Location, select **Remove this run’s six sample Contacts and their related files**, then confirm removal. This also removes changes made while practicing on those files. Other Contacts are preserved. If the sample ownership tags or email were changed, removal stops for review instead of deleting an uncertain Contact. After removal finishes, you can add a fresh pack.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.