ITP Submission Readiness: Review the Client Form, Close Gaps and Send a Clear Package

Confirm the required submission route before formatting

Find the contract clause, quality plan, client instruction or document-control procedure that states which ITP form, supporting records, reviewer, revision convention, transmittal route and review period apply. Confirm whether the customer requires its own form and whether linked inspection records, procedures, certificates or a register must accompany it.

Preserve mandatory headings, document-control fields, revision history, approval blocks and point legends. If the package needs continuation sheets or cross-references, identify them clearly and confirm that the process permits them. Do not assume a public template or generic form satisfies a project submission requirement.

Make contractor review a traceability check

Before issue, check that the package scope and boundaries are explicit; the sequence reflects the defined work; each retained row points to a current approved source and usable locator; and the method, criterion, frequency, role, control point and record are supported by project documents. Split combined rows when their sources, triggers, lots or responsible authorities differ.

Check that the stated client form and revision match the required one, titles and identifiers agree across attachments, and the ITP links to the records that will capture actual observations. Verify that proposed internal checks are not presented as contractual Hold or Witness Points. List omissions and conflicts in a query log instead of quietly filling them with typical values.

Prepare a submission cover and attachment register

A short cover/transmittal helps the reviewer locate and decide the submission. Identify the contract/package, work area, submitting organisation, ITP title and document number, revision/date, included files and revisions, purpose/status (for example, initial review or revision), requested response route/date when the contract specifies one, and any open queries affecting the package.

Use a compact attachment register with filename/document number, title, revision/date, status and relation to the ITP. Identify superseded copies where the project process requires it. Never label a draft ‘approved’ or imply a reviewer’s silence grants release unless the contract expressly defines that result.

Turn missing or conflicting inputs into actionable queries

For each gap, name the precise missing or conflicting requirement, affected ITP row and location, documents searched with revisions/locators, the decision needed, the project role or channel that can resolve it, date raised and current status. Keep supported rows moving while isolating only the affected decision; the client’s procedure determines whether submission can proceed with open queries.

Examples include a drawing/detail revision mismatch, an unstated acceptance value or sampling basis, a missing approved mix reference, unclear lot limits, contradictory notice instructions, or an unassigned release role. Ask the project authority to identify or confirm the governing requirement. Do not choose the strictest, newest or most convenient value without an authorised basis.

Keep authorship, review and approval roles separate

The contractor prepares and internally checks a submission against the available contract information. The client, superintendent, designer or other named reviewer acts only within the authority assigned by the contract. A completeness check is not technical approval, and an approval stamp does not necessarily release a separate construction Hold Point.

When comments arrive, retain the response trail, classify each comment, revise controlled content, update affected attachments and query statuses, and transmit a new revision through the prescribed system. Record unresolved or rejected comments and the authorised decision; do not silently delete them from the next issue.

Scope a drafting request with clear inputs and boundaries

A project-specific drafting package can be scoped around one defined trade/work package and the available source set: customer form and instructions, scope/contract documents, current drawings and specifications, relevant approved submittals, required linked records, and known review route. The output can be a mapped draft, source references and a query log for unresolved inputs.

The stated package is USD 99 with a 24-hour turnaround after complete required inputs are received. That clock covers preparation of the defined draft package; it does not promise client review, technical approval, engineering certification or resolution of missing project decisions. If inputs are incomplete, identify the missing items and clarify when the preparation window can start. ITP drafting is available for all construction trades, including customer-defined work types. Choose the named trade or Other and define one work package with its controlled source documents. Drafting supplies the plan and blank records; it does not perform design, construction, testing or certification.

Practical FAQ

**Can the client’s form be used even if it is awkward?** If the contract or client instruction mandates it, preserve its required fields and structure. Flag a field that cannot be completed from supplied sources; ask through the designated route rather than omitting or guessing it.

**Can an ITP be submitted with open queries?** The contract and document-control process decide. If submission is permitted, identify each open item, affected row/work and requested decision so the reviewer can see the boundary. Never conceal a technical gap in a generic note.

**Does the USD 99 / 24-hour package include approval?** No. It is a drafting turnaround measured from receipt of complete required inputs. Client review, technical decisions, engineering sign-off and formal release are controlled by the project’s assigned parties and process.

**What if my work type is not listed?** Select Other and name the actual discipline, work area and package boundary. Supply the governing drawings, specification, procedures and required form; missing requirements are raised as queries rather than replaced with generic values.

Fictional example: prepare a contractor review package

Fictional scenario only. The contractor, package identifiers and query IDs are illustrative; no live submission or approval is represented.

1. Confirm the fictional client requires its controlled ITP form, one linked field record and submission through its document system; record form revision and route in the cover sheet.
2. Map each in-scope row to the supplied approved source and locator, and check the contractor’s attachments and revision identifiers.
3. Log a conflict between two supplied detail revisions as Q-04 with affected row/location, both references and a specific request for the authorised current detail; leave the dependent criterion pending.
4. Prepare a transmittal listing the draft ITP revision, attachment register, purpose, status and Q-04 open item; submit only through the project’s stated route.
5. On receipt of an authorised response, update the controlled draft and query log, then issue the revised package and response cross-reference for the next review cycle.