When a professional-services engagement closes, the client may receive several final documents, supporting files and reference materials. The operational problem is not necessarily how to hand over the relationship; it is how to make the final output set intelligible after the project team has moved on. A deliverables index gives that output set a simple structure.
The index is not another copy of the deliverables and it is not a narrative handover note. It is a controlled map of what was issued: the final item, its status or version, where it belongs, any supporting material needed to interpret it and, where useful, who owns the next administrative step.
Define what qualifies for the final output set
Start by deciding which items belong in the index. Include final client-facing deliverables and supporting material that the client reasonably needs to use or interpret them. Exclude routine working drafts, superseded review copies and internal files that were never intended to form part of the final output.
This boundary matters because an index becomes less useful if it reproduces the entire project folder. Its job is to identify the authoritative output set, not to catalogue every artefact created during delivery.
Give each deliverable a stable, recognisable identity
Use the title or identifier that appears on the final item itself wherever possible. If internal shorthand was used during the engagement, translate it into wording the client will recognise rather than carrying unexplained team labels into the final index.
Where several related items have similar names, add enough description to distinguish them. The client should not need to open three files to discover which one is the final schedule, supporting note or decision document.
Record version and final-status information explicitly
The index should make clear which version is authoritative. Record the final version or issue date according to the firm's established document-control approach, and distinguish a final deliverable from material supplied only for reference.
If an item replaces an earlier version already received by the client, note that relationship where confusion is plausible. The aim is to prevent an older review copy from continuing to circulate simply because somebody saved it locally.
Map supporting files to the deliverable they explain
Supporting schedules, appendices, data extracts or reference notes can lose meaning when they are listed as unrelated files. Connect each supporting item to the deliverable it belongs with and briefly state its purpose when the relationship is not obvious from the filename.
This turns the index into a navigation layer. A future reader can begin with the main deliverable and immediately see which additional materials are relevant rather than searching through a folder without context.
Separate file location from ownership
Where the engagement uses an agreed repository or client workspace, record where the final item is held. Separately, identify any ongoing ownership that matters after close, such as responsibility for maintaining a client-controlled working file or completing a final administrative action.
Do not imply continuing professional responsibility merely because a person's name appears in the index. Location, administrative ownership and substantive responsibility are different concepts and should be recorded separately when necessary.
Reconcile the index against what was actually issued
Before closing the record, compare the index with the files and communications through which final outputs were supplied. Check that every listed item exists, that final-status information matches the issued copy and that obvious superseded drafts have not been included accidentally.
This is a reconciliation exercise rather than a fresh content review. The question is whether the index accurately describes the final output set the client received.
Keep the index as the durable map of the engagement outputs
Store the completed index with the engagement close records in a location the firm can retrieve later. If a final administrative correction changes a file name or location, update the index in a controlled way rather than allowing it to become detached from the output set.
A concise deliverables index gives both firm and client a clearer route back into completed work. Months later, the useful question is often not what happened during the engagement, but which final item should be opened and what supporting material belongs with it. The index should answer that quickly.