diff --git a/docs/lib/content/commands/npm-ci.md b/docs/lib/content/commands/npm-ci.md
index fb28e34e5f29b..f902e8040243e 100644
--- a/docs/lib/content/commands/npm-ci.md
+++ b/docs/lib/content/commands/npm-ci.md
@@ -21,6 +21,9 @@ The main differences between using `npm install` and `npm ci` are:
 * If a `node_modules` is already present, it will be automatically removed before `npm ci` begins its install.
 * It will never write to `package.json` or `package-lock.json`:
   installs are essentially frozen.
+* `--before` and `--min-release-age` do not affect `npm ci`, which installs
+  the versions recorded in the lockfile without resolving versions or checking
+  release dates.
 
 NOTE: If you create your `package-lock.json` file by running `npm install` with flags that can affect the shape of your dependency tree, such as
 `--legacy-peer-deps` or `--install-links`, you _must_ provide the same flags to `npm ci` or you are likely to encounter errors.
diff --git a/workspaces/config/lib/definitions/definitions.js b/workspaces/config/lib/definitions/definitions.js
index f932d8f48103c..0e47fbb09313a 100644
--- a/workspaces/config/lib/definitions/definitions.js
+++ b/workspaces/config/lib/definitions/definitions.js
@@ -360,6 +360,10 @@ const definitions = {
 
       Packages whose names match \`min-release-age-exclude\` are exempt from
       this filter.
+
+      NOTE: \`npm ci\` does not apply this setting. It installs the versions
+      recorded in the lockfile without resolving versions or checking release
+      dates.
     `,
     flatten,
   }),
@@ -1563,6 +1567,10 @@ const definitions = {
 
        Packages whose names match \`min-release-age-exclude\` are exempt from
        this filter.
+
+       NOTE: \`npm ci\` does not apply this setting. It installs the versions
+       recorded in the lockfile without resolving versions or checking release
+       dates.
     `,
     flatten: (key, obj, flatOptions) => {
       const age = obj['min-release-age']