[{"data":1,"prerenderedAt":278},["ShallowReactive",2],{"\u002Fupdates\u002F2026-09-18-calculate-next-dates-from-each-records-cadence":3,"surround":273},{"id":4,"title":5,"body":6,"date":250,"description":251,"extension":252,"head":253,"meta":254,"navigation":260,"path":261,"schemaOrg":253,"screenshot":262,"screenshotMargin":263,"seo":264,"sitemap":265,"stem":266,"tags":267,"__hash__":272},"updates\u002Fupdates\u002F2026-09-18-calculate-next-dates-from-each-records-cadence.md","Calculate next dates from each record's cadence",{"type":7,"value":8,"toc":241},"minimark",[9,18,23,59,78,82,107,111,189,193,213,217,232],[10,11,12,13,17],"p",{},"Many processes already store how often work repeats, such as a monthly review or a yearly inspection, but until now ",[14,15,16],"strong",{},"Cadence"," field type was not available for date calculations. Teams copied the same information, or worked the next date out by hand, and the dates drifted when a record's cadence changed.",[19,20,22],"h2",{"id":21},"whats-new","What's new:",[10,24,25,26,29,30,32,33,36,37,40,41,40,44,40,47,50,51,54,55,58],{},"A date ",[14,27,28],{},"Formula"," can now offset by a ",[14,31,16],{}," field as well as a ",[14,34,35],{},"Duration",", so the next date follows the interval already stored on each record. ",[14,38,39],{},"Weekly",", ",[14,42,43],{},"Monthly",[14,45,46],{},"Quarterly",[14,48,49],{},"Half-yearly"," and ",[14,52,53],{},"Yearly"," each move the starting date by that amount, forward or back, while ",[14,56,57],{},"One-off"," and blank cadences leave the date empty.",[10,60,61,62,65,66,69,70,73,74,77],{},"The same ",[14,63,64],{},"Offset Field"," list is used by ",[14,67,68],{},"Computed (Date)"," fields and by a scheduled automation's ",[14,71,72],{},"Due Date",". A ",[14,75,76],{},"Lookup"," field that copies a cadence from a linked record appears there too.",[19,79,81],{"id":80},"why-it-matters","Why it matters:",[83,84,85,92,98],"ul",{},[86,87,88,91],"li",{},[14,89,90],{},"Keep one interval"," by driving the next date from the cadence already on the record, rather than maintaining a second duration for the same repeat.",[86,93,94,97],{},[14,95,96],{},"Trust short months"," as 31 January plus one month becomes the last day of February, and 29 February plus one year becomes 28 February in a non-leap year.",[86,99,100,103,104,106],{},[14,101,102],{},"Leave one-off work empty"," because a ",[14,105,57],{}," cadence does not invent a follow-up date.",[19,108,110],{"id":109},"how-it-works","How it works:",[112,113,114,129,135,148,170,184],"ol",{},[86,115,116,117,120,121,124,125,128],{},"Open the collection, click the options menu (⋯), and select ",[14,118,119],{},"Configure",", then under ",[14,122,123],{},"Setup"," click ",[14,126,127],{},"Fields",".",[86,130,131,132,134],{},"Add a ",[14,133,16],{}," field if needed, plus a date field for the starting point, such as last review.",[86,136,137,138,141,142,145,146,128],{},"Click ",[14,139,140],{},"Add field",", name the next date, and set ",[14,143,144],{},"Type"," to ",[14,147,68],{},[86,149,150,151,153,154,157,158,145,161,164,165,167,168,128],{},"Under ",[14,152,28],{},", select the starting date, click ",[14,155,156],{},"Add Offset",", set ",[14,159,160],{},"Offset Type",[14,162,163],{},"Field Value",", and select the ",[14,166,16],{}," field under ",[14,169,64],{},[86,171,172,173,145,176,179,180,183],{},"Set ",[14,174,175],{},"Direction",[14,177,178],{},"Add"," to move the date forward, or ",[14,181,182],{},"Subtract"," to move it back.",[86,185,137,186,188],{},[14,187,178],{},", then set a record's cadence and check the computed date.",[19,190,192],{"id":191},"when-to-use-it","When to use it:",[83,194,195,201,207],{},[86,196,197,200],{},[14,198,199],{},"Facilities teams"," can keep each asset's next service date in step with its own interval, whether that is monthly for lifts or yearly for fire doors.",[86,202,203,206],{},[14,204,205],{},"Accountancy practices"," can work out a client's next filing review from the cadence already on their record, instead of maintaining a separate duration field alongside it.",[86,208,209,212],{},[14,210,211],{},"Membership organisations"," can schedule renewal reminders from each member's billing cadence, while one-off supporters are left without a follow-up date.",[19,214,216],{"id":215},"get-started","Get started",[10,218,219,220,222,223,225,226,228,229,231],{},"Open a collection you can configure, add or reuse a ",[14,221,16],{}," field, then create a ",[14,224,68],{}," field with ",[14,227,64],{}," set to the ",[14,230,16],{}," field.",[10,233,234,235,240],{},"If you have questions or feedback, we would love to hear from you. Email ",[236,237,239],"a",{"href":238},"mailto:support@kinabase.com","support@kinabase.com"," — we're listening.",{"title":242,"searchDepth":243,"depth":243,"links":244},"",2,[245,246,247,248,249],{"id":21,"depth":243,"text":22},{"id":80,"depth":243,"text":81},{"id":109,"depth":243,"text":110},{"id":191,"depth":243,"text":192},{"id":215,"depth":243,"text":216},"2026-09-18","Use a Cadence field to move a date forward or back for each record. Weekly, monthly, quarterly, half-yearly, and yearly intervals keep a dependable next date, and one-off records stay without a follow-up date.","md",null,{"readingTime":255},{"text":256,"minutes":257,"time":258,"words":259},"3 min read",2.045,122700,409,true,"\u002Fupdates\u002F2026-09-18-calculate-next-dates-from-each-records-cadence","\u002Fupdates\u002F2026\u002F2026-09-18-calculate-next-dates-from-each-records-cadence.png",false,{"title":5,"description":251},{"loc":261},"updates\u002F2026-09-18-calculate-next-dates-from-each-records-cadence",[268,269,270,271],"Collection","Field","Computed Field","Automation","EJXZEoP4lDt6es7i0hVdVnssq0c1zedR8sqXjxxhL9Y",[274,253],{"title":275,"path":276,"stem":277,"children":-1},"Require a type before a record can be saved","\u002Fupdates\u002F2026-09-14-require-a-type-before-a-record-can-be-saved","updates\u002F2026-09-14-require-a-type-before-a-record-can-be-saved",1789744619183]