FREE WORKING TOOL

Contractor document renewal date planner.

Work backwards from a recorded expiry. Find the dates to request a replacement, follow up and leave room for a human review.

01 Enter the expiry on your record02 Set collection and review time03 Save reminders to your calendar
No account, upload or email is needed for this tool.
SITENOD / DATE PLANNERPLAN 01—04

Your renewal timeline.

Work backwards from the recorded expiry. Adjust the time you need to collect and review a replacement.

Illustrative date. Enter the expiry shown on your own document to export a plan.

NEXT MOVE / 01Send the request

Confirm the requirement and ask the contractor for a replacement.

Planning prompts only. Weekend adjustment does not account for public holidays, and the recorded expiry itself is never moved. A date is not independent proof of coverage, validity or approval.

WHY WORK BACKWARDS

Leave room for the decision.

Requesting a file on its expiry date leaves no time to receive it, check that it is the right document, and ask for a correction. The planner separates those actions so the team can see what needs to happen before the recorded date.

Choose a lead time that reflects how long your contractors usually need. The review buffer is time reserved for your team to inspect the replacement. These are planning choices, not a prescribed compliance schedule.

WORKED EXAMPLE

One expiry. Four clear actions.

For a fictional document with a recorded expiry of 24 April 2027, a 60-day request lead time and a 14-day review buffer produce this plan:

  1. 01
    Send the request

    Confirm the requirement and ask the contractor for a replacement.

  2. 02
    Check progress

    Follow up if the replacement has not arrived. Record what was actually sent.

  3. 03
    Finish human review

    Leave time to inspect the file and ask for changes if needed. The target falls on a weekend, so this action moves to the previous Friday.

  4. 04
    Recorded expiry

    Recheck the accepted document and decide the next action before this date.

The follow-up falls midway between the request and review target. Weekend action dates move to the prior weekday by default; public holidays are not considered. Your team still needs to confirm the actual requirement, send any message and record its decision.

PUT THE PLAN TO WORK

Dates are useful when the work has an owner.

Use the free register template to track the contractor, requested document, accepted expiry, review state and responsible owner. Then explore a fictional SiteNod workflow to see how a received file remains separate from an approved one.

Before you rely on a date.

What if the replacement arrives late?

Keep the prior accepted record and the new submission distinct. Record the actual arrival date, then let a person decide whether to approve it or ask for a change.

Does the calendar file send anything?

No. The planner creates a file in your browser containing four generic all-day entries and dates, with no built-in notification alarms. Import it into your calendar and check the imported dates. It does not contact contractors or store your entries.

Does the expiry date prove coverage?

No. It is a date recorded from a document. Your organisation must review the document and apply its own requirements. This tool does not verify coverage, authenticity or legal compliance.

How the planner calculates each date

  1. Request date = recorded expiry minus the request lead time.
  2. Follow-up lead = review buffer + the whole-day floor of half the gap between request lead and review buffer.
  3. Review target = recorded expiry minus the review buffer.
  4. With previous-weekday handling, Saturday actions move back one day and Sunday actions move back two. The recorded expiry never moves.

Lead time must be a whole number from 14 to 180 days. Review buffer must be 1 to 30 days and at least seven days shorter than the lead time. Calculation uses calendar days, not business days, and does not check public holidays. If an action date has passed, act now or revise the plan.

Checked examples: weekends and a leap year

Fictional plans with previous-weekday handlingScroll sideways to see every column. When the table is focused, use the left and right arrow keys.
Recorded expiry / inputsRequestFollow-upReviewExpiry
2026-11-01; lead 30, buffer 72026-10-022026-10-142026-10-232026-11-01
2028-03-01; lead 14, buffer 72028-02-162028-02-182028-02-232028-03-01

In the Sunday 1 November 2026 example, the exact review target is Sunday 25 October. It moves to Friday 23 October; the expiry remains Sunday 1 November. Choosing exact-date handling keeps the review target on 25 October. The March 2028 example crosses 29 February without assuming every year has 365 days.

What your calendar file actually contains

The download contains four all-day calendar entries with generic action labels. It includes no alarm instruction (VALARM), contractor names or document files. Importing it does not send an email or turn on a SiteNod reminder service.

After import, check all four dates and set any notifications in your own calendar. The planner cannot verify your calendar’s import behaviour or notification settings. Keep the schedule with the source record and assign someone to carry out the actions.

Prepare the request once you choose your dates →