Components

Date input

Use the date input component to help users enter a memorable date or one they can easily look up.

When was your passport issued?

For example, 12 11 2007
<div id="passport-issued" class="govuk-form-group">
  <fieldset
    aria-describedby="passport-issued-hint"
    class="govuk-fieldset"
  >
    <legend class="govuk-fieldset__legend">
      <h1 class="govuk-heading-l">
        When was your passport issued?
      </h1>
    </legend>
    <span
      id="passport-issued-hint"
      class="govuk-hint"
    >
      For example, 12 11 2007
    </span>
    <div class="govuk-date-input">
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-day"
          class="govuk-label"
        >
          Day
        </label>
        <input
          type="text"
          id="passport-issued-day"
          name="passport-issued[day]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-month"
          class="govuk-label"
        >
          Month
        </label>
        <input
          type="text"
          id="passport-issued-month"
          name="passport-issued[month]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-year"
          class="govuk-label"
        >
          Year
        </label>
        <input
          type="text"
          id="passport-issued-year"
          name="passport-issued[year]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-4 govuk-date-input__input"
        />
      </div>
    </div>
  </fieldset>
</div>
<DateInput
  label={
    <h1 className="govuk-heading-l">
      When was your passport issued?
    </h1>
  }
  name="passport-issued"
  hint="For example, 12 11 2007"
/>
Props
Name Type Default Description
id string - 'id' attribute to place on the base HTML element HTML id (If not specified then the name will be used)
classBlock string - Block name override in BEM style classes applied to all elements
classModifiers other - BEM style modifiers to apply to the base HTML element
className string - Extra classes to apply to the base HTML element
accept string -
alt string -
autoComplete string -
autoFocus boolean -
capture other -
checked boolean -
crossOrigin string -
disabled boolean -
form string -
formAction string -
formEncType string -
formMethod string -
formNoValidate boolean -
formTarget string -
height other -
list string -
max other -
maxLength number -
min other -
minLength number -
multiple boolean -
name string -
pattern string -
placeholder string -
readOnly boolean -
required boolean -
size number -
src string -
step other -
type string -
value other - Value for controlled fields
width other -
onChange function -
defaultChecked boolean -
defaultValue other - Initial value of the field
suppressContentEditableWarning boolean -
suppressHydrationWarning boolean -
accessKey string -
contentEditable other -
contextMenu string -
dir string -
draggable other -
hidden boolean -
lang string -
slot string -
spellCheck other -
style other -
tabIndex number -
title string -
translate enum -
radioGroup string -
role string -
about string -
datatype string -
inlist other -
prefix string -
property string -
resource string -
typeof string -
vocab string -
autoCapitalize string -
autoCorrect string -
autoSave string -
color string -
itemProp string -
itemScope boolean -
itemType string -
itemID string -
itemRef string -
results number -
security string -
unselectable enum -
inputMode enum - Hints at the type of data that might be entered by the user while editing the element or its contents
is string - Specify that a standard HTML element should behave like a defined custom built-in element
aria-activedescendant string - Identifies the currently active element when DOM focus is on a composite widget, textbox, group, or application.
aria-atomic other - Indicates whether assistive technologies will present all, or only parts of, the changed region based on the change notifications defined by the aria-relevant attribute.
aria-autocomplete enum - Indicates whether inputting text could trigger display of one or more predictions of the user's intended value for an input and specifies how predictions would be presented if they are made.
aria-busy other - Indicates an element is being modified and that assistive technologies MAY want to wait until the modifications are complete before exposing them to the user.
aria-checked other - Indicates the current "checked" state of checkboxes, radio buttons, and other widgets.
aria-colcount number - Defines the total number of columns in a table, grid, or treegrid.
aria-colindex number - Defines an element's column index or position with respect to the total number of columns within a table, grid, or treegrid.
aria-colspan number - Defines the number of columns spanned by a cell or gridcell within a table, grid, or treegrid.
aria-controls string - Identifies the element (or elements) whose contents or presence are controlled by the current element.
aria-current other - Indicates the element that represents the current item within a container or set of related elements.
aria-describedby string - Identifies the element (or elements) that describes the object.
aria-details string - Identifies the element that provides a detailed, extended description for the object.
aria-disabled other - Indicates that the element is perceivable but disabled, so it is not editable or otherwise operable.
aria-dropeffect enum - Indicates what functions can be performed when a dragged object is released on the drop target.
aria-errormessage string - Identifies the element that provides an error message for the object.
aria-expanded other - Indicates whether the element, or another grouping element it controls, is currently expanded or collapsed.
aria-flowto string - Identifies the next element (or elements) in an alternate reading order of content which, at the user's discretion, allows assistive technology to override the general default of reading in document source order.
aria-grabbed other - Indicates an element's "grabbed" state in a drag-and-drop operation.
aria-haspopup other - Indicates the availability and type of interactive popup element, such as menu or dialog, that can be triggered by an element.
aria-hidden other - Indicates whether the element is exposed to an accessibility API.
aria-invalid other - Indicates the entered value does not conform to the format expected by the application.
aria-keyshortcuts string - Indicates keyboard shortcuts that an author has implemented to activate or give focus to an element.
aria-label string - Defines a string value that labels the current element.
aria-labelledby string - Identifies the element (or elements) that labels the current element.
aria-level number - Defines the hierarchical level of an element within a structure.
aria-live enum - Indicates that an element will be updated, and describes the types of updates the user agents, assistive technologies, and user can expect from the live region.
aria-modal other - Indicates whether an element is modal when displayed.
aria-multiline other - Indicates whether a text box accepts multiple lines of input or only a single line.
aria-multiselectable other - Indicates that the user may select more than one item from the current selectable descendants.
aria-orientation enum - Indicates whether the element's orientation is horizontal, vertical, or unknown/ambiguous.
aria-owns string - Identifies an element (or elements) in order to define a visual, functional, or contextual parent/child relationship between DOM elements where the DOM hierarchy cannot be used to represent the relationship.
aria-placeholder string - Defines a short hint (a word or short phrase) intended to aid the user with data entry when the control has no value. A hint could be a sample value or a brief description of the expected format.
aria-posinset number - Defines an element's number or position in the current set of listitems or treeitems. Not required if all elements in the set are present in the DOM.
aria-pressed other - Indicates the current "pressed" state of toggle buttons.
aria-readonly other - Indicates that the element is not editable, but is otherwise operable.
aria-relevant enum - Indicates what notifications the user agent will trigger when the accessibility tree within a live region is modified.
aria-required other - Indicates that user input is required on the element before a form may be submitted.
aria-roledescription string - Defines a human-readable, author-localized description for the role of an element.
aria-rowcount number - Defines the total number of rows in a table, grid, or treegrid.
aria-rowindex number - Defines an element's row index or position with respect to the total number of rows within a table, grid, or treegrid.
aria-rowspan number - Defines the number of rows spanned by a cell or gridcell within a table, grid, or treegrid.
aria-selected other - Indicates the current "selected" state of various widgets.
aria-setsize number - Defines the number of items in the current set of listitems or treeitems. Not required if all elements in the set are present in the DOM.
aria-sort enum - Indicates if items in a table or grid are sorted in ascending or descending order.
aria-valuemax number - Defines the maximum allowed value for a range widget.
aria-valuemin number - Defines the minimum allowed value for a range widget.
aria-valuenow number - Defines the current value for a range widget.
aria-valuetext string - Defines the human readable text alternative of aria-valuenow for a range widget.
dangerouslySetInnerHTML other -
onCopy function -
onCopyCapture function -
onCut function -
onCutCapture function -
onPaste function -
onPasteCapture function -
onCompositionEnd function -
onCompositionEndCapture function -
onCompositionStart function -
onCompositionStartCapture function -
onCompositionUpdate function -
onCompositionUpdateCapture function -
onFocus function -
onFocusCapture function -
onBlur function -
onBlurCapture function -
onChangeCapture function -
onBeforeInput function -
onBeforeInputCapture function -
onInput function -
onInputCapture function -
onReset function -
onResetCapture function -
onSubmit function -
onSubmitCapture function -
onInvalid function -
onInvalidCapture function -
onLoad function -
onLoadCapture function -
onError function -
onErrorCapture function -
onKeyDown function -
onKeyDownCapture function -
onKeyPress function -
onKeyPressCapture function -
onKeyUp function -
onKeyUpCapture function -
onAbort function -
onAbortCapture function -
onCanPlay function -
onCanPlayCapture function -
onCanPlayThrough function -
onCanPlayThroughCapture function -
onDurationChange function -
onDurationChangeCapture function -
onEmptied function -
onEmptiedCapture function -
onEncrypted function -
onEncryptedCapture function -
onEnded function -
onEndedCapture function -
onLoadedData function -
onLoadedDataCapture function -
onLoadedMetadata function -
onLoadedMetadataCapture function -
onLoadStart function -
onLoadStartCapture function -
onPause function -
onPauseCapture function -
onPlay function -
onPlayCapture function -
onPlaying function -
onPlayingCapture function -
onProgress function -
onProgressCapture function -
onRateChange function -
onRateChangeCapture function -
onSeeked function -
onSeekedCapture function -
onSeeking function -
onSeekingCapture function -
onStalled function -
onStalledCapture function -
onSuspend function -
onSuspendCapture function -
onTimeUpdate function -
onTimeUpdateCapture function -
onVolumeChange function -
onVolumeChangeCapture function -
onWaiting function -
onWaitingCapture function -
onAuxClick function -
onAuxClickCapture function -
onClick function -
onClickCapture function -
onContextMenu function -
onContextMenuCapture function -
onDoubleClick function -
onDoubleClickCapture function -
onDrag function -
onDragCapture function -
onDragEnd function -
onDragEndCapture function -
onDragEnter function -
onDragEnterCapture function -
onDragExit function -
onDragExitCapture function -
onDragLeave function -
onDragLeaveCapture function -
onDragOver function -
onDragOverCapture function -
onDragStart function -
onDragStartCapture function -
onDrop function -
onDropCapture function -
onMouseDown function -
onMouseDownCapture function -
onMouseEnter function -
onMouseLeave function -
onMouseMove function -
onMouseMoveCapture function -
onMouseOut function -
onMouseOutCapture function -
onMouseOver function -
onMouseOverCapture function -
onMouseUp function -
onMouseUpCapture function -
onSelect function -
onSelectCapture function -
onTouchCancel function -
onTouchCancelCapture function -
onTouchEnd function -
onTouchEndCapture function -
onTouchMove function -
onTouchMoveCapture function -
onTouchStart function -
onTouchStartCapture function -
onPointerDown function -
onPointerDownCapture function -
onPointerMove function -
onPointerMoveCapture function -
onPointerUp function -
onPointerUpCapture function -
onPointerCancel function -
onPointerCancelCapture function -
onPointerEnter function -
onPointerEnterCapture function -
onPointerLeave function -
onPointerLeaveCapture function -
onPointerOver function -
onPointerOverCapture function -
onPointerOut function -
onPointerOutCapture function -
onGotPointerCapture function -
onGotPointerCaptureCapture function -
onLostPointerCapture function -
onLostPointerCaptureCapture function -
onScroll function -
onScrollCapture function -
onWheel function -
onWheelCapture function -
onAnimationStart function -
onAnimationStartCapture function -
onAnimationEnd function -
onAnimationEndCapture function -
onAnimationIteration function -
onAnimationIterationCapture function -
onTransitionEnd function -
onTransitionEndCapture function -
error other - Error message
hint other For example, 12 11 2007 Hint
label other - REQUIRED. Label

When to use this component

Use the date input component when you’re asking users for a date they’ll already know, or can look up without using a calendar.

When not to use this component

Do not use the date input component if users are unlikely to know the exact date of the event you’re asking about.

Read more about how to ask users for dates.

How it works

The date input component consists of 3 fields to let users enter a day, month and year.

The 3 date fields are grouped together in a <fieldset> with a <legend> that describes them, as shown in the examples on this page. This is usually a question, like ‘What is your date of birth?’.

If you’re asking one question per page, you can set the contents of the <legend> as the page heading. This is good practice as it means that users of screen readers will only hear the contents once.

Read more about why and how to set legends as headings.

When was your passport issued?

For example, 12 11 2007
<div id="passport-issued" class="govuk-form-group">
  <fieldset
    aria-describedby="passport-issued-hint"
    class="govuk-fieldset"
  >
    <legend class="govuk-fieldset__legend">
      <h1 class="govuk-heading-l">
        When was your passport issued?
      </h1>
    </legend>
    <span
      id="passport-issued-hint"
      class="govuk-hint"
    >
      For example, 12 11 2007
    </span>
    <div class="govuk-date-input">
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-day"
          class="govuk-label"
        >
          Day
        </label>
        <input
          type="text"
          id="passport-issued-day"
          name="passport-issued[day]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-month"
          class="govuk-label"
        >
          Month
        </label>
        <input
          type="text"
          id="passport-issued-month"
          name="passport-issued[month]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-year"
          class="govuk-label"
        >
          Year
        </label>
        <input
          type="text"
          id="passport-issued-year"
          name="passport-issued[year]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-4 govuk-date-input__input"
        />
      </div>
    </div>
  </fieldset>
</div>
<DateInput
  label={
    <h1 className="govuk-heading-l">
      When was your passport issued?
    </h1>
  }
  name="passport-issued"
  hint="For example, 12 11 2007"
/>

Never automatically tab users between the fields of the date input because this can be confusing and may clash with normal keyboard controls.

If you’re asking more than one question on the page

If you’re asking more than one question on the page, do not set the contents of the <label> as the page heading. Read more about asking multiple questions on question pages.

When was your passport issued?For example, 12 11 2007
<div id="passport-issued" class="govuk-form-group">
  <fieldset
    aria-describedby="passport-issued-hint"
    class="govuk-fieldset"
  >
    <legend class="govuk-fieldset__legend">
      When was your passport issued?
    </legend>
    <span
      id="passport-issued-hint"
      class="govuk-hint"
    >
      For example, 12 11 2007
    </span>
    <div class="govuk-date-input">
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-day"
          class="govuk-label"
        >
          Day
        </label>
        <input
          type="text"
          id="passport-issued-day"
          name="passport-issued[day]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-month"
          class="govuk-label"
        >
          Month
        </label>
        <input
          type="text"
          id="passport-issued-month"
          name="passport-issued[month]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-year"
          class="govuk-label"
        >
          Year
        </label>
        <input
          type="text"
          id="passport-issued-year"
          name="passport-issued[year]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-4 govuk-date-input__input"
        />
      </div>
    </div>
  </fieldset>
</div>
<DateInput
  label="When was your passport issued?"
  name="passport-issued"
  hint="For example, 12 11 2007"
/>

Use the autocomplete attribute for a date of birth

Use the autocomplete attribute on the date input component when you’re asking for a date of birth. This lets browsers autofill the information on a user’s behalf if they’ve entered it previously.

To do this, set the autocomplete prop to bday. See how to do this in the code snippet in the following example.

What is your date of birth?

For example, 31 3 1980
<div id="dob" class="govuk-form-group">
  <fieldset
    aria-describedby="dob-hint"
    class="govuk-fieldset"
  >
    <legend class="govuk-fieldset__legend">
      <h1 class="govuk-heading-l">
        What is your date of birth?
      </h1>
    </legend>
    <span id="dob-hint" class="govuk-hint">
      For example, 31 3 1980
    </span>
    <div class="govuk-date-input">
      <div class="govuk-date-input__item">
        <label for="dob-day" class="govuk-label">
          Day
        </label>
        <input
          type="text"
          id="dob-day"
          name="dob[day]"
          pattern="[0-9]*"
          inputmode="numeric"
          autocomplete="bday-day"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label for="dob-month" class="govuk-label">
          Month
        </label>
        <input
          type="text"
          id="dob-month"
          name="dob[month]"
          pattern="[0-9]*"
          inputmode="numeric"
          autocomplete="bday-month"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label for="dob-year" class="govuk-label">
          Year
        </label>
        <input
          type="text"
          id="dob-year"
          name="dob[year]"
          pattern="[0-9]*"
          inputmode="numeric"
          autocomplete="bday-year"
          class="govuk-input govuk-input--width-4 govuk-date-input__input"
        />
      </div>
    </div>
  </fieldset>
</div>
<DateInput
  label={
    <h1 className="govuk-heading-l">
      What is your date of birth?
    </h1>
  }
  name="dob"
  hint="For example, 31 3 1980"
  autoComplete="bday"
/>

If you are working in production you’ll need to do this to meet WCAG 2.1 Level AA.

You will not normally need to use the autoComplete attribute in prototypes, as users will not generally be using their own devices.

Error messages

Error messages should be styled like this:

When was your passport issued?

For example, 12 11 2007Error: The date your passport was issued must be in the past
<div
  id="passport-issued"
  class="govuk-form-group govuk-form-group--error"
>
  <fieldset
    aria-describedby="passport-issued-hint"
    class="govuk-fieldset"
  >
    <legend class="govuk-fieldset__legend">
      <h1 class="govuk-heading-l">
        When was your passport issued?
      </h1>
    </legend>
    <span
      id="passport-issued-hint"
      class="govuk-hint"
    >
      For example, 12 11 2007
    </span>
    <span
      id="passport-issued-error"
      class="govuk-error-message"
    >
      <span class="govuk-visually-hidden">
        Error:
      </span>
      The date your passport was issued must be in the
      past
    </span>
    <div class="govuk-date-input">
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-day"
          class="govuk-label"
        >
          Day
        </label>
        <input
          type="text"
          id="passport-issued-day"
          name="passport-issued[day]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-month"
          class="govuk-label"
        >
          Month
        </label>
        <input
          type="text"
          id="passport-issued-month"
          name="passport-issued[month]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-year"
          class="govuk-label"
        >
          Year
        </label>
        <input
          type="text"
          id="passport-issued-year"
          name="passport-issued[year]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-4 govuk-date-input__input"
        />
      </div>
    </div>
  </fieldset>
</div>
<DateInput
  label={
    <h1 className="govuk-heading-l">
      When was your passport issued?
    </h1>
  }
  name="passport-issued"
  hint="For example, 12 11 2007"
  error="The date your passport was issued must be in the past"
/>

If you’re highlighting just one field - either the day, month or year - only style the field that has an error. The error message must say which field has an error, like this:

When was your passport issued?

For example, 12 11 2007Error: The date your passport was issued must include a year
<div
  id="passport-issued"
  class="govuk-form-group govuk-form-group--error"
>
  <fieldset
    aria-describedby="passport-issued-hint"
    class="govuk-fieldset"
  >
    <legend class="govuk-fieldset__legend">
      <h1 class="govuk-heading-l">
        When was your passport issued?
      </h1>
    </legend>
    <span
      id="passport-issued-hint"
      class="govuk-hint"
    >
      For example, 12 11 2007
    </span>
    <span
      id="passport-issued-error"
      class="govuk-error-message"
    >
      <span class="govuk-visually-hidden">
        Error:
      </span>
      The date your passport was issued must include a
      year
    </span>
    <div class="govuk-date-input">
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-day"
          class="govuk-label"
        >
          Day
        </label>
        <input
          type="text"
          id="passport-issued-day"
          name="passport-issued[day]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-month"
          class="govuk-label"
        >
          Month
        </label>
        <input
          type="text"
          id="passport-issued-month"
          name="passport-issued[month]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-2 govuk-date-input__input"
        />
      </div>
      <div class="govuk-date-input__item">
        <label
          for="passport-issued-year"
          class="govuk-label"
        >
          Year
        </label>
        <input
          type="text"
          id="passport-issued-year"
          name="passport-issued[year]"
          pattern="[0-9]*"
          inputmode="numeric"
          class="govuk-input govuk-input--width-4 govuk-input--error govuk-date-input__input"
        />
      </div>
    </div>
  </fieldset>
</div>
<DateInput
  label={
    <h1 className="govuk-heading-l">
      When was your passport issued?
    </h1>
  }
  name="passport-issued"
  hint="For example, 12 11 2007"
  error={{
    year:
      "The date your passport was issued must include a year",
  }}
/>

Make sure errors follow the guidance in error message and have specific error messages for specific error states.

If there’s more than one error, show the highest priority error message. In order of priority, show error messages about:

  • missing or incomplete information
  • information that cannot be correct (for example, the number ‘13’ in the month field)
  • information that fails validation for another reason

If nothing is entered

Say ‘Enter [whatever it is] ’.

For example, ‘Enter your date of birth’.

If an incomplete date is entered and you know what is missing

Say ‘ [whatever it is] must include a [whatever is missing] ’.

For example, ‘Date of birth must include a month’ or ‘Date of birth must include a day and month’.

If an incomplete date is entered and you do not know what is missing

Say ‘Enter [whatever it is] and include a day, month and year’.

For example, ‘Enter your date of birth and include a day, month and year’.

If the date entered is not a real one

Say ‘Enter a real [whatever it is] ’.

For example, ‘Enter a real date of birth’.

If the date is in the future when it needs to be in the past

Say ‘ [whatever it is] must be in the past’.

For example, ‘Date of birth must be in the past’.

If the date is in the future when it needs to be today or in the past

Say ‘ [whatever it is] must be today or in the past’.

For example, ‘Date of birth must be today or in the past’.

If the date is in the past when it needs to be in the future

Say ‘ [whatever it is] must be in the future’.

For example, ‘The date your course ends must be in the future’.

If the date is in the past when it needs to be today or in the future

Say ‘ [whatever it is] must be today or in the future’.

For example, ‘The date your course ends must be today or in the future’.

If the date must be the same as or after another date

Say ‘ [whatever it is] must be the same as or after [date and optional description] ’.

For example, ‘The date your course ends must be the same as or after 1 September 2017 when you started the course’.

If the date must be after another date

Say ‘ [whatever it is] must be after [date and optional description] ’.

For example, ‘The day your course ends must be after 1 September 2017’.

If the date must be the same as or before another date

Say ‘ [whatever it is] must be the same as or before [date and optional description] ’.

For example, ‘The date of Gordon’s last exam must be the same as or before 31 August 2017 when they left school’.

If the date must be before another date

Say ‘ [whatever it is] must be before [date and optional description] ’.

For example, ‘The date of Gordon’s last exam must be the same as or before 31 August 2017’.

If the date must be between two dates

Say ‘ [whatever it is] must be between [date] and [date and optional description] ’.

For example, ‘The date your contract started must be between 1 September 2017 and 30 September 2017 when you were self-employed’.