A hold-point register should make it possible to find the notification, the inspection or review record and the authorised release for the correct activity. It should not suggest that a coordinator has released work simply because a scheduled date has passed. The governing inspection plan, specification and contract define the actual process and authority.

Use the approved reference

Begin with the activity identifier and wording supplied by the approved project documents. Record the relevant inspection or test plan revision, work area, lot or asset and the party designated to receive notification. Ask the package lead to confirm notice periods and release responsibilities rather than copying them from another project.

Keep an explicit link to the controlling requirement. If the project changes an inspection plan or work sequence, record which issue applies to the affected work and obtain direction from the authorised person where it is unclear.

Track separate events

Useful register fields include planned activity date, notice reference and sent date, recipient, acknowledgement, inspection reference, release decision, release issuer, release date and source file. Include conditions or restrictions exactly as recorded by the authorised party, with a link to the original communication.

Do not collapse notified, attended and released into a single checkbox. Each describes a different event. A witness record, inspection attendance sheet or an email acknowledging a notice may not be the release evidence required by the project. Ask the authorised reviewer to confirm how those records should be classified.

Hypothetical example

A contractor sends a notice for a foundation inspection and later receives an acknowledgement. The register marks notice sent and acknowledgement received, while release remains awaiting evidence. When the nominated authority supplies the release record, the coordinator links it to the same activity and records any conditions. The earlier acknowledgement is retained as part of the trail.

Reconcile before final handover

Compare the applicable activity list with the register and investigate missing links. Check that repeated activities are distinguishable by location or lot, and that releases are not accidentally assigned to the next activity in sequence. Keep open queries visible in the gap list.

A documentation coordinator can maintain the index and retrieve the correspondence. The coordinator must not authorise work to proceed, invent a release or interpret an ambiguous condition as permission. Only the party appointed by the project's process can make that decision. The register should preserve and communicate that authority, not replace it.