Skip to content

Main content

Advisory Source Period Gap Tool

Calculate advisory source period gap from explicit caller-supplied inputs.

Loading tool…

Description

Parse real YYYY-MM-DD dates.

Extension-service time budgets distinguish contact, travel, closed cases, credited pauses and source-validity periods. Allocated person-time differs from elapsed time, while half-open source periods differ from closed deadline checks. A supplied deadline or pause is not automatically an official service requirement.

Parse real YYYY-MM-DD dates.

When to use this tool

Use Advisory Source Period Gap when checking the stated contact/travel, response or source-period convention.

How to use the tool and how it works

  1. Enter adviceDate, sourceStartDate, sourceEndDate, reviewDate. 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 daysFromSourceStart, daysToSourceEnd, ageAtReviewDays, insideSourcePeriod. Inspect insideSourcePeriod before interpreting the associated values.

Parse real YYYY-MM-DD dates. Require source end>=start and review>=advice. Return signed advice-minus-start/source-end-minus-advice day gaps, review age and membership in the half-open source interval [start,end).1

Input fieldMeaning and unitsAccepted input
adviceDateAdvice DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
sourceStartDateSource Start DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
sourceEndDateExcluded end of the source period; advice exactly on this date is outside.Required. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
reviewDateReview DateRequired. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted.
Output fieldInterpretationReturned shape
daysFromSourceStartDays From Source StartRequired. Safe integer.
daysToSourceEndDays To Source EndRequired. Safe integer.
ageAtReviewDaysAge At Review DaysRequired. Safe integer.
insideSourcePeriodInside Source PeriodRequired. Boolean.
json
{
  "input": {
    "adviceDate": "2024-01-05",
    "sourceStartDate": "2024-01-01",
    "sourceEndDate": "2024-01-10",
    "reviewDate": "2024-01-08"
  },
  "output": {
    "daysFromSourceStart": 4,
    "daysToSourceEnd": 5,
    "ageAtReviewDays": 3,
    "insideSourcePeriod": true
  }
}

Limitations and assumptions

  • Dates use UTC day arithmetic without business calendars; no actual publication validity or current agronomic advice is established.
  • 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.

Alternative or Complementary methods

Use verified clock, journey and source records with the governing service and reimbursement policies for actual performance or payment decisions.

References

  1. Calculation and input contract: agricultural-extension/advisory-source-period-gap — tool.io

Similar or alternative tools