Skip to main content

Learning objectives

By the end of this module, learners will be able to:

  • Explain what a document model is.
  • Add fields to a document model.
  • Test and publish a document model for workflow use.

Prerequisites

  • Completion of Module 01.
  • Completion of Module 06 recommended.
  • Admin access.
  • A sample document approved for training.

Concepts

Document model​

A document model defines the fields Smartflow should extract and review for a document type.

Example: A credit agreement model may include borrower name, facility amount, maturity date, margin, and covenant fields.

Field setup​

Each field should have a clear name and expected type.

Example: "Maturity date" should be configured as a date field, not a free-text note.

Model lifecycle​

Models are created as drafts, tested, then published when ready for workflow use.

Example: An admin updates a draft model after testing shows that one field needs clearer review guidance.

Walkthrough

  1. Open the configuration area. Expected outcome: You can see document model configuration options.

  2. Create a model and choose a document type. Expected outcome: A draft model is created.

  3. Add the core fields needed for onboarding. Expected outcome: The model contains fields your team must review.

  4. Set field types and review guidance. Expected outcome: Reviewers know what each field means and how to check it.

  5. Test the model with a sample document. Expected outcome: Extracted fields and source evidence appear for review.

  6. Publish the model after the test result is accepted. Expected outcome: The model can be attached to workflows.

Practice exercise

Scenario: Your team wants to configure a document model for credit agreements.

Task: Create a draft model, add five onboarding fields, test it on one sample document, and identify any field that needs clearer guidance.

Success criteria:

  • Model has a clear name and document type.
  • At least five fields are configured.
  • Each field has an expected type.
  • Test result is reviewed before publication.

Knowledge check questions

  1. What does a document model define?
  2. Why should field names match the operations team's language?
  3. When should a model be published?

Next module

Continue to: Learning Paths