Skip to content

Main content

Unit Key Handover Possession Date Tag

Preserve explicit key-handover and possession date wording without deciding legal possession.

Loading tool…

Description

Preserve explicit key-handover and possession date wording.

Property bookkeeping distinguishes scheduled and collected rent, concessions, assigned common area, fee bases and calendar boundaries. A decimal index change differs from a percentage-number input, and a rent-free period needs explicit start/end conventions. Supplied scenarios do not establish market value, lawful charges, possession or enforceable lease terms.

Preserve explicit key-handover and possession date wording.

When to use this tool

Use Unit Key Handover Possession Date Tag when you already have unitId, keyHandoverDateText, possessionDateText and need to preserve explicit key-handover and possession date wording.

How to use the tool and how it works

  1. Enter unitId, keyHandoverDateText, possessionDateText. 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 token. Use the output convention below.

Enter unitId, keyHandoverDateText, possessionDateText using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1

Input fieldMeaning and unitsAccepted input
unitIdUnit IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
keyHandoverDateTextKey Handover Date TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
possessionDateTextPossession Date TextRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
tokenTokenRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "unitId": "U17",
    "keyHandoverDateText": "2026-10-28",
    "possessionDateText": "2026-11-01"
  },
  "output": {
    "token": "[\"U17\",\"2026-10-28\",\"2026-11-01\"]"
  }
}

Limitations and assumptions

  • The result records supplied values without deciding legal possession. Sources and asserted relationships are not independently authenticated.
  • 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

Review the lease, transaction records and stated area-measurement method for actual charges and allocations. Use a complete cash-flow or closing statement when assessing net proceeds; supplied credits, caps and fee terms are scenario components.

References

  1. Calculation and input contract: real-estate/unit-key-handover-possession-date-tag — tool.io

Similar or alternative tools