Skip to content

Main content

Business Day Target Calendar Offset

Apply an already resolved calendar-day offset for a business-day target without calculating working days or holiday calendars.

Loading tool…

Description

Shift a reference date by supplied calendar days.

Project records separate planned effort, recorded time, forecast assumptions, resource buffers and role authority. A probability-weighted impact is one scenario term, and a calendar-day shift is not a business-calendar calculation. Local progress and workload shares need consistent scope and periods before broader interpretation.

Shift a reference date by supplied calendar days.

When to use this tool

Use Business Day Target Calendar Offset when you already have referenceDate, suppliedCalendarOffsetDays and need to shift a reference date by supplied calendar days.

How to use the tool and how it works

  1. Enter referenceDate, suppliedCalendarOffsetDays. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read targetDate. Use the output convention below.

Require real UTC referenceDate and signed safe whole offset; add it in UTC and require output year 0000..9999.1

Input fieldMeaning and unitsAccepted input
referenceDateReference DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
suppliedCalendarOffsetDaysSigned calendar-day offset. Weekends and holidays are included despite the business-day title.Required. Safe integer.
Output fieldInterpretationReturned shape
targetDateTarget DateRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "referenceDate": "2026-10-28",
    "suppliedCalendarOffsetDays": 4
  },
  "output": {
    "targetDate": "2026-11-01"
  }
}

Limitations and assumptions

  • Despite the title, this performs calendar-day arithmetic only; no weekends, holidays, business-day rules or lawful deadline are selected.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Reconcile the complete plan, resource calendar, costs and action history for an operational question. Use the actual business calendar or delegated-role documentation when required, rather than treating one supplied offset or Boolean as that full workflow.

References

  1. Calculation and input contract: management/business-day-target-calendar-offset — tool.io

Similar or alternative tools