Due dates that calculate themselves from your data
Anchor a step's deadline to a date your team actually collects in the run — a go-live, a renewal, a ship date. Set it once as “2 business days before” and every run works out the real date on its own, no manual math and nothing to keep re-typing.
Start a free trial — no credit card required.
Stop guessing deadlines run by run
Every event has a different date, so a fixed deadline is wrong the moment the run starts. Relative due dates read the date your team enters and work out each step's deadline for that run — consistently, every time.
- Someone edits each step's date on every run
- A slipped go-live leaves stale deadlines behind
- Reminders fire off the wrong day
- Set the rule once on the workflow
- Each run calculates its own real dates
- Reminders land relative to the true deadline
Three steps to self-calculating deadlines
Collect a date in a step
Add a Date data-collection field to a step — the go-live, the renewal, the appointment. Your team fills it in as the run progresses.
Anchor a step's due date to it
On another step, set a relative due date: an amount of time, before or after, measured from the collected date. That rule lives on the workflow template.
Every run does the math
Once the date is entered, Manifestly calculates the real deadline for that run — and recalculates if the date is later corrected.
The date flows straight into the deadline
Inside a run, one step captures the date. As soon as that step is completed with a value, the deadline on the step you configured is worked out for you — and written to the run so it drives everything downstream.
- Calculates once the source date is entered and its step is complete.
- Correct the date later and the due date recalculates to match.
- Step reminders can key off the calculated due date, so nudges land on time too.
Anchor a deadline to whatever matters
A relative due date is an amount of time measured from a starting point. Choose the starting point that fits the work — a collected date is one of four.
From a collected date
Measured from a date field your team fills in during the run.
From the run start
Measured from the moment the run begins.
From the previous step
Measured from when the prior step is completed.
From the run due date
Measured backward from the run's own deadline.
Before or after, in the units you count in
Say how much time and which direction. A positive offset falls after the anchor date; a negative one falls before it. Measure in minutes, hours, or days — and for days, choose whether you're counting calendar days or business days.
- Before for lead-time deadlines — “prep is due 2 days before go-live.”
- After for follow-ups — “send the recap 1 day after the meeting.”
- The rule reads in plain language on the step, so anyone editing the workflow understands it.
Count the days that actually count
When you measure in days, business-day counting skips weekends and the holidays on the workflow's business calendar — so “2 days before go-live” never lands your team on a Saturday. A landing rule can nudge a result onto the next business day when a calculation falls on a day off.
- Choose calendar days or business days per step.
- Business days honor the workflow's working days and holiday calendar.
- A landing rule keeps deadlines off weekends and holidays.
Automatic, but never rigid
The calculation handles the common case, and a person stays in control of the exception. Override a single run's due date by hand and Manifestly respects it — it won't quietly recalculate over your change, and the run's activity records both what it would have set and that a person overrode it.
- Manually set a due date on any run when a one-off calls for it.
- A manual override isn't overwritten by later recalculation.
- Due-date changes are logged to the run's activity for a clean audit trail.
Where a collected date drives the deadline
Launches & go-lives
Capture the target go-live date up front.
The final review is due 2 business days before — and shifts automatically if the date moves.
Renewals & compliance
Record the renewal or expiry date on the run.
Paperwork is due 5 days before the deadline, every contract, without a spreadsheet of dates.
Events & appointments
Collect the event or appointment date.
Prep tasks are due before it and follow-ups after it — all anchored to the one date entered.
Relative due dates, answered
Other Features
Workflow Customization
Shape exactly how each workflow behaves — logic, data, timing, and documentation.
Assign and Automate
Get the right work to the right people, on schedule — automatically.
Track Progress and Reporting
See what's done, what's late, and what's coming — across every run.
Govern, secure & prove it
SSO, granular permissions, and a complete audit trail — the controls enterprise teams need to run their work and prove how it was done.
Communicate
Keep the conversation — and a permanent record of who did what, and when — in one place.
Trusted by organizations big and small for their recurring workflows
Set Step Due Dates from a Collected Date
With Manifestly, your team will Never Miss a Thing.