DMIN in Google Sheets: Find the Shortest Approved Lead Time

A purchasing planner compares quoted lead times in days. Unapproved offers may look fast but should not determine the approved sourcing plan. The criteria cells stay visible beside the report so another person can inspect which records were intended to contribute.

=DMIN(database, field, criteria)

• database: the complete rectangular range, including its field headers.
• field: the header of the column to aggregate, or its one-based position inside that range.
• criteria: a separate range with field headers and one or more rows of tests.

All examples explicitly supply all three arguments. Google’s database specification establishes the header grid: conditions on one row combine with AND; alternative rows combine with OR. Despite the phrase “SQL-like” in some help descriptions, pass a criteria range rather than a SQL statement.

Use a blank sheet. Enter the following original practice data in A1:D7, Copy only the four field columns; the leftmost Row column is a worksheet-row annotation, not data to enter. The numbered row 1 supplies A1:D1. The table heading above it repeats the field names only for readability; do not enter that display heading as an additional row. Enter numbers as numbers, without units appended. Keep the criteria and result outside this database range.

Use F2 for the result. The field argument will be "Days", which selects column D. The equivalent index is 4, measured from A within A1:D7. Criteria may test other columns without changing which field supplies the result.

Clear H1:J4 before each setup so old criteria do not remain. Enter this grid, beginning at H1:

Enter =DMIN(A1:D7,"Days",H1:H2) in F2. Expected result: 3.

Matched worksheet rows: 2, 3, 5. Their selected Days entries are 8, 3, 6. Check the explicit field index by replacing the formula with =DMIN(A1:D7,4,H1:H2); the expected result remains 3.

Clear H1:J4 before each setup so old criteria do not remain. Enter this grid, beginning at H1:

Enter =DMIN(A1:D7,"Days",H1:I2) in F2. Expected result: 6.

Matched worksheet rows: 2, 5. Their selected Days entries are 8, 6. Both tests are on the same criteria row, so a record must pass both. Moving a test to another row would change the selection logic.

Clear H1:J4 before each setup so old criteria do not remain. Enter this grid, beginning at H1:

Enter =DMIN(A1:D7,"Days",H1:I3) in F2. Expected result: 6.

Matched worksheet rows: 2, 4, 5, 7. Their selected Days entries are 8, 12, 6, 9. Each criteria row is a complete alternative. A record qualifies when it passes all tests in either row; it need not pass both alternatives.

Clear H1:J4 before each setup so old criteria do not remain. Enter this grid, beginning at H1:

Enter =DMIN(A1:D7,"Days",H1:J2) in F2. Expected result: 8.

Matched worksheet rows: 2, 4, 7. Their selected Days entries are 8, 12, 9. The warehouse cannot receive before day 7 and needs arrival by day 12. Applying both bounds to approved offers removes the otherwise fastest approved six-day offer. The remaining lead times are 8, 12 and 9 days, so the earliest usable quote is 8 days. The minimum depends on the receiving constraint, not simply supplier speed. Repeating a field header lets its lower and upper bounds apply together on the same row.

Do not encode unknown lead times as numeric zero unless same-day delivery is genuinely intended. A zero is a real numeric candidate in a minimum calculation. Store and resolve missing-data status separately before making a sourcing decision.

If the result is unexpected, first list the records selected by each criteria row. Then check the aggregation separately. This distinguishes an incorrect filter from incorrect arithmetic.

• Keep A1:D7 inclusive of the header. Starting at A2 turns the first record into the apparent labels.
• Copy criteria headers from row 1 rather than inventing display labels. Check that "Days" names the intended result field.
• Enter comparison criteria such as >=7 as cell contents, not as a SQL fragment or an extra formula argument.
• Keep the database range large enough for new records, but do not silently include unrelated totals below the register.
• If a formula fails to parse, check quotation marks, the leading equals sign, and the argument separator expected by your sheet. The examples use English function names and comma-separated arguments.
• If the filter matches no rows, inspect the filter before interpreting any output. This guide does not prescribe an error code or default for empty selections.

This guide targets Google Sheets as described in the saved official documentation reviewed October 19, 2026. The reviewed sources do not provide a first-supported version or a desktop-style release matrix. No mobile, offline, exported Excel, or other spreadsheet-engine behavior was tested. Recheck the worked records after importing or exporting a workbook.

The examples deliberately avoid wildcard rules, date-text parsing, formulas returning empty text, and errors in the selected field. Those edge cases are not established by the sources reviewed here. Do not borrow another product’s behavior for them. For production reports, test the exact data types and selection boundaries used in your own sheet.

• Google Sheets function catalogue: establishes the DMIN signature and aggregate purpose. The individual DMIN detail page was not successfully retrieved; this guide does not claim it was reviewed.
• Google database functions: field selection, criteria headers, AND/OR logic, repeated headers and unrestricted empty criteria cells.

All datasets, record selections and applications above are original instructional examples.