@@ -224,6 +224,49 @@ ageForm = form(this.ageModel, (schemaPath) => {
 });
 ```
 
+### minDate() and maxDate()
+
+The `minDate()` and `maxDate()` validation rules work with `Date` values, such as a field bound to `<input type="date">`. They also set the `min` and `max` attributes of that input.
+
+```angular-ts
+import {Component, signal} from '@angular/core';
+import {form, FormField, minDate, maxDate} from '@angular/forms/signals';
+
+@Component({
+  selector: 'app-booking-form',
+  imports: [FormField],
+  template: `
+    <form novalidate>
+      <label>
+        Check-in
+        <input type="date" [formField]="bookingForm.checkIn" />
+      </label>
+    </form>
+  `,
+})
+export class BookingFormComponent {
+  bookingModel = signal<{checkIn: Date | null}>({checkIn: null});
+
+  bookingForm = form(this.bookingModel, (schemaPath) => {
+    minDate(schemaPath.checkIn, new Date('2026-06-01'), {message: 'Bookings open on June 1'});
+    maxDate(schemaPath.checkIn, new Date('2026-08-31'), {message: 'Bookings close on August 31'});
+  });
+}
+```
+
+IMPORTANT: An `<input type="date">` reads and writes `Date` values at midnight UTC, whatever the user's time zone, because that is how the browser's `valueAsDate` works. Build the limits the same way, for example with `new Date('2026-06-01')` or `new Date(Date.UTC(2026, 5, 1))`. A `Date` created from local time, such as `new Date(2026, 5, 1)` or `new Date()`, is shifted by the user's UTC offset. Depending on the time zone, the `min` or `max` attribute can then be off by a day, and the limit date itself can be rejected.
+
+To require a date that is not before today, use today's calendar date in the user's time zone, expressed at midnight UTC:
+
+```ts
+const now = new Date();
+const today = new Date(Date.UTC(now.getFullYear(), now.getMonth(), now.getDate()));
+
+minDate(schemaPath.checkIn, today, {message: 'Check-in cannot be in the past'});
+```
+
+Passing `new Date()` directly can reject today's date, because the value picked in the input is midnight UTC, which is earlier than the current time. This happens in UTC and in the time zones behind it.
+
 ### minLength() and maxLength()
 
 The `minLength()` and `maxLength()` validation rules work with strings and arrays:
 
@@ -18,14 +18,19 @@ import {maxDateError} from './validation_errors';
  * This function can only be called on date paths.
  * In addition to binding a validator, this function adds `MAX` property to the field.
  *
+ * When the field is bound to an `<input type="date">`, its value is a `Date` at midnight UTC, so the
+ * maximum should be built the same way, e.g. `new Date('2026-08-31')` or
+ * `new Date(Date.UTC(2026, 7, 31))`. A `Date` created from local time, such as `new Date(2026, 7, 31)`
+ * or `new Date()`, is offset by the user's time zone, which can make the limit date itself invalid.
+ *
  * @param path Path of the field to validate
  * @param maxDate The maximum date, or a LogicFn that returns the maximum date.
  * @param config Optional, allows providing any of the following options:
  *  - `error`: Custom validation error(s) to be used instead of the default `maxDateError()`
  *    or a function that receives the `FieldContext` and returns custom validation error(s).
  * @template TPathKind The kind of path the logic is bound to (a root path, child path, or item of an array)
  *
- * @see [Signal Form Max Validation](guide/forms/signals/validation#min-and-max)
+ * @see [Signal Form Max Validation](guide/forms/signals/validation#mindate-and-maxdate)
  * @category validation
  * @publicApi 22.0
  */
 
@@ -18,14 +18,19 @@ import {minDateError} from './validation_errors';
  * This function can only be called on date paths.
  * In addition to binding a validator, this function adds `MIN` property to the field.
  *
+ * When the field is bound to an `<input type="date">`, its value is a `Date` at midnight UTC, so the
+ * minimum should be built the same way, e.g. `new Date('2026-06-01')` or
+ * `new Date(Date.UTC(2026, 5, 1))`. A `Date` created from local time, such as `new Date(2026, 5, 1)`
+ * or `new Date()`, is offset by the user's time zone, which can make the limit date itself invalid.
+ *
  * @param path Path of the field to validate
  * @param minDate The minimum date, or a LogicFn that returns the minimum date.
  * @param config Optional, allows providing any of the following options:
  *  - `error`: Custom validation error(s) to be used instead of the default `minDateError()`
  *    or a function that receives the `FieldContext` and returns custom validation error(s).
  * @template TPathKind The kind of path the logic is bound to (a root path, child path, or item of an array)
  *
- * @see [Signal Form Min Validation](guide/forms/signals/validation#min-and-max)
+ * @see [Signal Form Min Validation](guide/forms/signals/validation#mindate-and-maxdate)
  * @category validation
  * @publicApi 22.0
  */