Enriched Fields
Enriched fields let Optible automatically derive new values from applicant answers, uploaded documents, and external data sources. They are how Optible fills the gaps between what applicants submit and the specific numbers and labels your scoring criteria need.
Why enriched fields exist
Applicants rarely give you the exact value you need to score against. Some common examples:
Total budget — The applicant entered 15 expense line items. Your grant needs one total. An enriched field adds them up.
Project category — The applicant described their project in a paragraph. Your grant needs it classified as Education, Health, Environment, Arts, or Community. An enriched field picks one.
Verified utility spend — The applicant uploaded their latest energy bill. Your grant needs the total amount billed. An enriched field pulls the figure directly off the bill.
What an enriched field draws from
When you configure an enriched field, you choose what it has access to:
Full application — Draws from every answer the applicant gave, plus any enriched fields that have already run. Works well for classification or summarisation.
Selective — You pick specific questions and uploaded documents to draw from. This is how an enriched field pulls values out of a document — for example, reading the total from an uploaded invoice.
Enriched only — Draws solely from the output of earlier enriched fields. Use this when combining already-derived values, such as producing a risk tier from a credit score and a cashflow rating.
How enriched fields pull data from documents
When Optible reads an uploaded document during validation, it extracts and saves specific values — amounts, dates, names, and so on. An enriched field in Selective mode can be pointed at one of those documents to use those extracted values.
For example: an applicant uploads an energy bill. Document validation extracts the total amount billed ($1,245.80). An enriched field called Verified energy spend is configured to pull that figure. The result — $1,245.80 — is saved as a new field on the application, visible to reviewers and available for scoring.
Order matters
Enriched fields run one at a time, in the order you set. Each field's output becomes part of the application, which means later enriched fields can draw on it.
For example, a grant might run three enriched fields in this order:
Annual revenue — pulled from an uploaded financial statement
Annual expenses — pulled from the same statement
Cashflow rating — draws from the two values above and returns Strong, Adequate, or Weak
If the order were reversed, the third field would have nothing to draw from. Order is the grant admin's responsibility.
What an enriched field produces
A single value — a number, a label, a sentence. Once saved, it sits alongside the applicant's own answers in the reviewer interface. If a value is incorrect, the reviewer can correct it the same way they would any other field.
Does an enriched field need to be linked to a scoring criterion?
No. There are three common patterns:
Linked to a criterion — The criterion's question references the enriched field. For example, "Is the total project budget above $50,000?" where the total budget is an enriched field.
Shown to the reviewer only — The field saves the reviewer time (e.g. extracted invoice total) but is not part of the scoring rubric.
Used by other enriched fields only — An intermediate value that exists solely to feed into a later enrichment.
Where enriched fields fit in the assessment
Enriched fields are the middle stage of Optible's assessment pipeline:
Document validation — Reads uploaded files and extracts values
Enriched fields — Combines extracted values and applicant answers into new derived fields
Criteria scoring — Reads everything above and assigns scores
Document validation must complete before enriched fields run. Enriched fields must complete before criteria scoring begins.