Date dependencies in Airtable

NOTE

Date dependencies differ from the Gantt view date dependency behavior because date dependencies use the data layer for all view types and interfaces.

Date dependencies is a project management feature that natively allows automatically cascading updates between date fields in dependent records.

These updates work by allowing the base creators to designate specific fields for a table(s), such as start date, end date, duration, and predecessor fields. Once those fields are designated, Airtable automatically updates any/all dependent record(s).

The following date dependency behavior is supported within Airtable records:

• Automatically recalculate start dates, end dates, and modified field durations.

NOTE

• Date dependencies' rules are similar to the calendar app date time ranges limitations:

  • Updating the start date moves the end date forward or backward while the duration is unchanged.  

  • Updating the end date will update the duration accordingly. 

  • Updating the duration will update the end date accordingly. 

NOTE

If "Omit weekends and holidays" is enabled, this recalculation behavior takes those days into account.

The following date dependency behaviors are supported across Airtable records:

• Finish-to-start (FS) dependencies.

• Shifting record dates when they otherwise violate a dependency relationship — also known as “ consume buffer” in Asana or “ flexible buffer” in Monday.com.

  • Tasks are shifted when their dates begin to overlap. The distance between tasks possibly still decreases.

NOTE

If "Omit weekends and holidays" is enabled, this recalculation behavior takes those days into account.

To use date dependencies, your table will need the following field types:

Records can contain invalid date dependency values, preventing them from recalculating correctly when dependent values change.

Date dependencies errors:

• Missing required values

• End date is before start date

• Inconsistent duration period

• Finish-to-start (FS) dependency violations

• Looping dependencies

NOTE

When errors are present, they are displayed as a floating bar in the bottom left corner of the view displaying rows, including date dependency data.

Clicking the floating bar opens a modal that directs you to fix the errors manually or allows Airtable to address them automatically. Airtable attempts to fix all errors described above, except for looping dependencies. — which needs to be resolved by the user.

1. Visit your Airtable homepage.

2. Create or open your preferred base.

3. Click the + icon next to “Add or import.”

4. Click Create blank table, then Save.

5. Click the ⌄ icon next to your table’s name and select Configure date dependencies.

7. Click the ⌄ icon under the “Predecessor field” section and select your preferred field (optional).

8. Click the ⌄ icon under the “Start date field” section and select your preferred field.

9. Click the ⌄ icon under the “End date field” section and select your preferred field.

10. Click the ⌄ icon under the “Duration date field” section and select your preferred field.

11. Click Save.

Date dependencies work alongside record templates. Instead of hardcoding specific dates or defining them relative to a date on the parent record, child record dates can be defined relative to their dependencies.

When date dependencies are enabled for a table, the configuration UI appears slightly different and only allows start dates and duration values to be defined because the end date value is calculated from the other 2 field values.

Only the duration value can be defined if a record has a dependency because its start date is determined from the dependencies.

Once the record template use is initiated, all child records are assigned dependency-aware dates defined relative to each other.

No. Date dependencies currently only support consume buffer behavior, meaning tasks only shift when their dates overlap. The distance between tasks may still decrease.

Tasks ending on a specific date occupy the entire day. Below is an example of how Airtable's timeline view handles similar issues. In our example, "Record 1" ends on 1/31, and "Record 2" starts on 1/31.

We do not support “End dates” ending at the start of a day.