A subcontract can spread document requirements across schedules, specifications, drawings and client procedures. Copying only the obvious handover schedule may leave important submissions outside the working register. A disciplined extraction exercise makes the sources and responsibilities visible, while leaving interpretation with the authorised contract and technical owners.

Create a source inventory

List the contract documents provided for the task, including revision or date and their relationship to the package. Ask the contract owner to confirm the current set. Keep variations and written instructions in the inventory so later changes can be traced back to their source rather than added as unexplained spreadsheet rows.

The coordinator should not decide the order of precedence between conflicting documents. Record the conflict, identify the affected deliverable and ask the responsible person for direction. Retain the instruction with the resulting register entry.

Extract one deliverable per line

Useful fields include requirement reference, quoted or clearly identified requirement, practical deliverable name, package, intended recipient, required format, lead time, due milestone, information owner and reviewer. Distinguish a document to be produced from a record to be collected from another party.

A long clause may contain several actions. Split these into linked register lines where that improves ownership and follow-up. Conversely, avoid counting the same requirement several times just because it appears in more than one source. Use cross-references and let the contract owner confirm whether entries are duplicates or separate obligations.

Hypothetical example

A specification calls for an equipment schedule, while the handover instructions require asset data in the client's spreadsheet format. The coordinator links the two source references and asks whether one controlled deliverable can satisfy both needs. The confirmed answer is recorded, including who will prepare the file and who checks the technical data.

Maintain the register after award

Review the extraction with the package lead before using it to chase submissions. Add new rows only with a source and a reason. Keep a change log when dates, formats or responsibilities are revised, particularly where supplier lead times or review cycles are affected.

This process produces a document plan, not legal advice about what the subcontract requires. It does not determine whether an obligation can be waived, whether a claim is valid or who bears a disputed cost. Escalate those questions to the contract administrator and qualified advisers. The register's value is that a reviewer can see where each requested file came from and what decision remains outstanding.