Hold points and witness points: coordinating project responsibilities
Admin · 22 October 2026
Illustrative image. Photo by alan boyce on Unsplash. Unsplash License.
A point identified in a quality plan has practical value only when the team understands the event, notification and authority attached to it. Terms such as hold point and witness point may be used in project documents, but their actual meaning needs to be established from the applicable requirements and agreement. Assuming a universal interpretation can leave one party expecting attendance while another believes work may continue.
For package managers, the task is to translate the agreed position into a dependable sequence. The responsible technical and commercial teams establish the requirement and its effect. Delivery planning then coordinates readiness, notice, access and the evidence needed for the next step. A label in a spreadsheet should not be left to carry all that meaning by itself.
Confirm the project definitions
Locate the requirements that establish the point and clarify how the relevant terms are used. Identify what must happen, who participates and what consequence applies if the event is not completed. Obtain appropriate advice where wording is unclear. Do not rely on a team’s habit from another contract as evidence of the current arrangement.
Record the agreed interpretation in the relevant controlled plan, with references to its source. The site team needs a usable explanation without casually rewriting the contractual or technical requirement. If clarification changes the basis, route it through the project’s proper process. The objective is a coherent position across documents, not another informal rule.
Identify the actual work stage
Describe the condition at which the event occurs and the work to which it relates. A broad stage name may be insufficient where several areas progress independently. Use identifiers appropriate to the package so participants understand which location, component or system is ready for review. The responsible technical team should establish the required detail.
Connect the event to the sequence before and after it. Ask what preparation is needed and what activity depends on the outcome. This makes the consequence visible in planning and helps package leads provide realistic notice. A point scheduled only in a quality register can be missed if the delivery programme does not show its dependency.
Allocate notification responsibility
Name the person who initiates the notification and identify the required recipients and channel under the actual arrangement. The person performing the work may know readiness first, while another person administers the formal notice. Clarify that handover so neither assumes the other has completed it. Record the information the notice must contain.
Use the applicable notice requirements and allow for them in planning. Do not invent a standard period across every package. If the work sequence changes, review the notification effect before treating the new date as confirmed. The relevant attendees need an accurate account of readiness and any revised commitment.
Check readiness before inviting attendance
Confirm the prerequisites established by the responsible team, including the relevant information and evidence. A planned date is not proof that the work has reached the required condition. An incomplete event can consume specialist time and delay the next activity. Use a proportionate readiness check to identify gaps before the formal attendance.
A hypothetical package books a review before closure of an area, but supporting records remain incomplete and the work stage is ambiguous. The issue is not solved by having every party attend. The coordinator needs to identify what is missing, obtain the appropriate decision and update the sequence using a credible account of readiness.
Make authority explicit
Identify who can confirm the relevant outcome or release under the applicable arrangements. Attendance, observation and authorisation are different actions. A person present may have a limited review role rather than authority to accept the whole package. The record should describe what they actually reviewed and the status that follows.
Where an expected participant is unavailable, obtain the appropriate direction through the established process. The site should not infer permission from silence or assume another attendee can substitute without authority. Preserve the request and decision so the next team understands the basis on which the activity proceeded or remained constrained.
Record outcomes precisely
Use the project’s agreed record to identify the work, participants, evidence and conclusion. Distinguish an event completed from actions still outstanding. A signed attendance sheet may prove attendance but not the technical outcome or permission for the next stage. Keep the meaning of each acknowledgement clear.
If the event identifies a problem, route it through the relevant quality and technical process. The point record should link to that action without improvising a corrective solution. The responsible competent people determine the response and required evidence. Planning needs the resulting status and dependencies, with uncertainty preserved where assessment continues.
Connect release to the next team
Communicate the authorised outcome through the channel used by the people controlling subsequent work. A release stored only in one person’s inbox may not reach the package waiting to proceed. Confirm the current status and any conditions that apply. The receiving supervisor should not have to reconstruct the decision from meeting recollections.
The APM configuration management overview provides context for traceable current information. Applied here, the practical need is to connect the outcome to the correct work and document versions. A clear reference helps prevent a record for one area being mistaken for another.
Manage changes and repeated activities
Review the point when design, method or package scope changes. The original arrangement may need further assessment under the applicable process. Do not assume a previous release applies automatically to revised work. The responsible team should determine what remains valid and what evidence is needed now.
For repetitive work, establish the appropriate scope and sampling arrangements with competent specialists and the relevant requirements. A completed first event should not be treated as universal acceptance unless the actual plan establishes that basis. Keep the coverage explicit so every participant understands what the record does and does not represent.
Preserve the status during team changes
Include open points and consequential releases in the handover to incoming supervisors or package leads. They need the current work identity, outcome and remaining conditions, not merely a copy of the original plan. Check that they can retrieve the referenced evidence and understand the decision route. This prevents a personnel change creating an assumption that every earlier point is closed, or causing a completed review to be repeated unnecessarily because its authorised record cannot be found.
For packages progressing in several areas, use identifiers that distinguish each event and its coverage. A release for one room, floor or batch should not appear as a package-wide completion. Ask the receiving supervisor to check the scope against the work now planned and refer any mismatch to the responsible coordinator before relying on the record.
Review coordination failures constructively
When an event is missed or delayed, investigate the specific cause. It may involve unrealistic notice, unclear readiness or an unavailable decision owner. Repeating a reminder to follow the plan may not address the underlying condition. Assign a practical improvement and check its effect on subsequent events.
Keep commercial questions within the appropriate review route. The operational chronology supplies facts, but it should not make unsupported conclusions about liability or entitlement. A factual record of notice, attendance and readiness helps the responsible advisers assess the position under the actual agreement.
Well-coordinated hold and witness arrangements connect defined requirements to real work stages, clear authority and usable evidence. They give the delivery team a dependable account of when the next activity can proceed under the project process. The result is fewer decisions based on assumptions about a label and a clearer trail from readiness through review to the authorised outcome.
Test the process during mobilisation with one representative event. Confirm the notification route, relevant information and communication of the result before several packages rely on the same workflow.
