Less manual entry
Extract information from files without rebuilding it by hand.
Your structure
Save approved results in the Data Collection that fits your workflow.
Human control
Review, correct, approve, or reject every import draft.
When to choose Doclay
Doclay is a strong fit when your team regularly receives documents that contain useful business data but not in a consistent table. Typical examples include:- onboarding documents and application forms
- contracts, reports, and recurring statements
- property, portfolio, or investment documents
- spreadsheets that need to be standardized
- mixed files that should become one consistent Data Collection
How Doclay works
1
Choose the destination
In Setup, select the Data Collection that should receive approved records. This is the only required decision before Doclay can run.
2
Provide files
Upload files when starting a run or select files that are already stored in Layest. Manual uploads remain available even after you add automation.
3
Let Doclay prepare the data
Doclay reads the source, proposes the structure it found, and extracts the matching records.
4
Review the draft
Check the proposed fields and records. Correct anything that needs attention, re-extract if necessary, or reject the draft without importing it.
5
Approve the result
Approved records are saved to your selected Data Collection. Depending on your review policy, clean imports can also be approved automatically as working drafts.
Your Setup page
Doclay’s Setup page keeps the workflow easy to understand:- Manual uploads are included from the start.
- Data Collection output is required so Doclay knows where approved records belong.
- Email intake can collect attachments through a dedicated inbox.
- Connected folders can start imports when files are added or updated.
- Schedules can run recurring imports from a configured source.
- External destinations can receive approved files or results.
- Ready to run appears as soon as the required destination is in place.
Optional additions never block Doclay. Start manually, prove the workflow with real examples, and add automation only when it saves your team time.
A good first run
Choose two or three representative files: one straightforward example and one that contains the variation your team normally sees. A useful first run helps you confirm:- the right information is being extracted
- field names make sense to your team
- relationships and file links belong in the right place
- reviewers know what they need to check
- the destination Data Collection supports the next step in your process
What happens after approval
Approved records become part of the selected Layest Data Collection. Your team can filter, sort, edit, relate, and use those records in other workflows. The source files and the run history remain available for traceability.Set up your first agent
Follow the short guide from the library to a ready first run.
Understand Data Collections
Learn where Doclay stores approved, structured records.