BDS0.1

Recurrence Configuration

A recurring request with a cadence, reporting membership and target.

Reviewed 2026-10-28Markdown

Configure one accountable membership for the intake. The storage permits multiple links and the digest iterates over them, but Intake Check flags more than one. Active schedules with an Active cadence are candidates for collection. The current digest computes due requests; it does not create Task records. Event Schedule and Scheduler State describe a broader scheduling model and are not consumed by the reviewed digest.

Use and boundaries

Field names below are the current product labels. * and ° are UI markers, not database constraints. A preferred single-record selection is not a global cardinality constraint either. The related guide explains operational rules.

Related guide · All entities

Recurrence Configuration in the current system

Recurrence Configuration in the current system

Fields

Field Storage Source, options or boundary
Name* Text Stored value.
Description* Long text Stored value.
Procedure° Linked records Procedure
Accountable Membership - OLD Text Historical; do not fill.
Reporting Membership Text Text reference; not a linked record.
Target Organization Text Text reference; not a linked record.
Classification Term Text Text reference; not a linked record.
Cadence - OLD Single select Daily, Weekly, Biweekly, Monthly, Quarterly, Annual, On Demand
Event Schedule Long text Stored value.
Estimated Effort Duration Stored value.
Priority Single select Urgent, High, Medium, Low
Target Template° Linked records Metric Target
Version° Text Stored value.
Lifecycle Status* Single select Draft, Proposed, Active, On Hold, Completed, Cancelled, Archived
Scheduler State Long text Stored value.
Tasks Linked records Task
Assignments Linked records Assignment Role
Intakes Linked records Intake
Cadence* Linked records Cadence (mirror)
Cadence (Key) Lookup Cadence* → Key
Observations Linked records Observation
Accountable Membership* Linked records Membership (mirror)
Accountable (Name) Lookup Accountable Membership* → Member
Accountable (Email) Lookup Accountable Membership* → Company Email
Accountable (Membership #) Lookup Accountable Membership* → Membership #
Accountable (Organization) Lookup Accountable Membership* → Business Unit (Legal Name)
Created At Created time Generated by Airtable.
Created By Created by Generated by Airtable.
Target (Value) Lookup Target Template° → Target Value*
Target (Direction) Lookup Target Template° → Metric (Direction)
Target (Unit Text) Lookup Target Template° → Metric (Unit Text)
Target (Metric) Lookup Target Template° → Metric*
Accountable Display Name Lookup Accountable Membership* → Member Display Name
Cadence (Lifecycle Status) Lookup Cadence* → Lifecycle Status
Intake Check Formula Computed; see formulas below.
Intake Step Formula Computed; see formulas below.
Tags Linked records op:tags · optional labels from the Core Tags catalog; classification only.

Current formulas

Internal references are rendered as readable field names. These expressions describe current configuration, including its limitations.

Intake Check

IF(COUNTA({Accountable Membership*})!=1,"⚠ Choose one accountable membership. ","") & IF(COUNTA({Cadence*})!=1,"⚠ Choose one cadence. ","") & IF({Cadence (Key)}=BLANK(),"⚠ Cadence has no key. ","") & IF({Cadence (Lifecycle Status)}&""!="Active","⚠ Cadence is not Active. ","") & IF(COUNTA({Target Template°})>1,"⚠ Choose at most one target. ","") & IF(AND({Target Template°},OR({Target (Metric)}=BLANK(),{Target (Unit Text)}=BLANK(),{Target (Direction)}=BLANK())),"⚠ Complete the linked target metric. ","")

Intake Step

IF(OR({Lifecycle Status*}="Draft",{Lifecycle Status*}=BLANK()),IF(OR({Name*}=BLANK(),{Description*}=BLANK()),"Schedule - 1",IF({Accountable Membership*}=BLANK(),"Schedule - 2",IF({Cadence*}=BLANK(),"Schedule - 3","Schedule - 4"))),"")

Example and maintenance

Illustrative example: “Daily service report” requests one membership to report against Target v1 on an Active daily cadence.

The 193 current records were migrated on 2026-10-21 from the legacy Operations base: all Active, Version 1, starting 2026-10-21. Identical old rows were merged, so one record can list several accountable memberships even though Intake Check expects one. Event Schedule keeps the old day as text, for example “Monday to Saturday”; the digest does not read it. See Architecture.

Use the existing fictitious records to inspect relationships in the guide. Before changing fields, check lookups, formulas, intakes and workflow contracts. This page documents structure; a field does not prove that an integration populates it.