Your forms have a layout unique to your company. Which option fits?
Why C is the answer
A custom Document Intelligence model
Custom models handle layouts that prebuilt models do not cover.
In detail
- A custom model learns your own layout.
- Label a representative set of forms.
Use case
An illustrative scenario, not a real incident.
A logistics firm uses its own delivery form, which no prebuilt model knows. A custom model learns that layout from labeled samples.
See it in different ways
stateDiagram-v2 [*] --> CommonForm CommonForm --> Prebuilt: invoice or similar CommonForm --> Custom: layout unique to you Prebuilt --> Fields Custom --> Fields Fields --> [*]
flowchart LR S0["Collect samples"] --> S1["Label fields"] --> S2["Train custom model"] --> S3["Extract"]
Key point: Unique layouts need a custom model.
Why the other options are wrong
- A. A prebuilt model for a different document type
- A prebuilt model for another document will not fit.
- B. An image generation model
- An image model does not read forms.
- D. A text to speech voice
- A voice has nothing to do with forms.

