Customer onboarding templates: relative dates vs fixed dates

The single biggest workflow upgrade in customer ops is moving onboarding templates from fixed dates to relative dates. It's also one of the most under-adopted patterns.

What "relative dates" means

• Fixed-date template: "Send welcome forms on March 5. Run kickoff on March 8. Go-live on March 19."
• Relative-date template: "Send welcome forms on Day 1. Run kickoff on Day 4. Go-live on Day 14."

When you clone the relative-date template to a new customer with a start date of June 12, it auto-schedules: welcome forms June 12, kickoff June 15, go-live June 26.

Why it matters

Onboarding-driven teams clone templates 20–100 times per year. With fixed dates, every clone is followed by 30 minutes of date adjustment. With relative dates, the clone is done in one click.

For a team running 50 onboardings/year:

• Fixed dates: 50 × 30 min = 25 hours/year of pure date-adjustment work
• Relative dates: 0 hours

Plus the elimination of "I forgot to update the date on this task" errors that propagate across the onboarding plan.

Why teams use fixed dates anyway

1. Their tool doesn't support relative dates. Monday, ClickUp, Asana all require workarounds (formulas, automations) to do relative scheduling at the template level.
2. They didn't realize the pattern existed. "We've always done it this way."
3. One-off customizations creep in. Each new customer gets a different start date, so the template gets rebuilt every time.

The mental model that works

Think of the customer's start date as T+0. Every other task is T+1, T+3, T+7, T+14. The template stores offsets, not absolute dates. The customer record stores T+0.

This is how project management tools have done it for 30 years. Customer onboarding just hasn't caught up.

What "Day 0" actually means

Pick one anchor and be consistent:

• Contract signature (most common; clean date)
• Kickoff call (good if kickoff often slips and you want milestones to shift with it)
• First-login (good for product-led teams; bad for high-touch enterprise)

Don't switch anchors mid-template — pick one and stick with it.

How BlueHill handles this

Relative-date templates are first-class objects in BlueHill. Build the template once with relative offsets. Clone to a new customer. Every task auto-schedules.

If a milestone slips, downstream tasks shift automatically (Day 14 stays Day 14 relative to Day 0; Day 14 doesn't shift forward if Day 7 slipped to Day 9, but the dependency chain is visible).

Related reading

• Onboard SaaS customers in 14 days
• Customer kickoff playbook
• Onboarding glossary