Professional-services work can depend on information or specialist input that comes neither from the client nor from the delivery team. A third-party reliance register gives a small firm a focused record of those external inputs and, crucially, the boundaries around how they are being used.
This is not a supplier review process and it is not a general source register. Its purpose is to make dependencies on third-party material visible inside a specific client engagement so the team does not quietly treat an external input as broader, more current or more authoritative than the working basis allows.
Identify third-party inputs that materially affect the work
Record external material or input when it influences an important assumption, analysis step, decision or deliverable. Routine background reading does not necessarily need an entry. The register should concentrate attention on dependencies that another team member would need to understand to follow the work.
Describe the input clearly enough to distinguish it from client-provided information and the firm's own working analysis.
Record the intended use rather than merely naming the source
For each entry, state what the team is using the third-party input for. It may inform a defined calculation, provide specialist context, support a particular workstream or establish an agreed working assumption.
This prevents the existence of a source from being mistaken for unlimited reliance on everything it contains. A narrow purpose should remain narrow in the working record.
Capture ownership of obtaining and checking the input
Make clear who is responsible for obtaining the material, confirming that the expected item has arrived and raising questions where it does not match the engagement's needs. That operational ownership is separate from responsibility for any professional judgement based on the input.
Where the client is coordinating the third party, the register can still identify the firm's internal owner for monitoring the dependency.
Keep limitations beside the reliance entry
If the input is provisional, restricted in scope, based on an earlier position or otherwise qualified, record that limitation with the entry. Do not allow a caveat to become detached from the source as information moves into drafts and working papers.
Where a limitation creates an unresolved issue, link it to the appropriate action, information-gap or escalation record rather than hiding the problem in free-text notes.
Distinguish receipt from acceptance for use
An external document arriving in the project folder does not automatically mean the team has decided it is suitable for the intended purpose. Use separate states where helpful: expected, received, reviewed for intended use, queried or superseded.
This distinction is particularly valuable when revised third-party material arrives after work has already started.
Revisit reliance when the engagement changes
A change in scope, assumptions or deliverable structure may alter the relevance of an external input. Review affected entries when the engagement changes materially rather than assuming the original reliance decision remains appropriate.
If a source is replaced, preserve the relationship between the old and new entries so the team can understand which version informed earlier work.
Close the register against the final work actually delivered
Before engagement close, reconcile material reliance entries with the final deliverables and working records. Confirm that important limitations remain visible and that superseded inputs are not presented as current.
A concise third-party reliance register gives professional-services teams a clearer view of external dependencies without creating a second project-management system. It records what came from outside the client-team relationship, why it mattered, how far it was used and what qualifications travelled with it.