Legal Services Offshore blog
Checking executed-contract exhibit packets without deciding incorporation
Reconcile labels, cross-references, signatures, and file identities while counsel determines the legal effect of every exhibit.
Packet completeness and legal incorporation are different questions
An executed agreement can refer to schedules, annexes, statements of work, pricing tables, or disclosure letters that are stored separately. An administrative check can show whether the delivered packet contains files bearing the referenced labels and whether their versions can be traced. It cannot decide that a document forms part of the contract, which version governs, whether a missing exhibit affects enforceability, or what an inconsistency means. Those judgments belong to counsel. The checklist gives counsel a source-linked map of the packet rather than a green completeness label that conceals assumptions.
Preserve the closing source before rearranging files
Start from the approved closing location or transmittal. Record the agreement filename, source path, received time, file size, page count, signature status as displayed, and a hash where the firm's procedure calls for one. Inventory every accompanying file without renaming the originals. NIST describes a hash value as a value used to substantiate integrity or make inclusion and exclusion comparisons; it does not prove that a file is legally operative. Keep the original packet read-only. Any working index or combined PDF should identify its inputs and remain visibly separate from the source delivery.
Build the reference list from the agreement itself
Read the executed agreement only for explicit labels and cross-references authorized by the review protocol. Capture the displayed term, section, page, stated title, date or version, and whether the text says attached, delivered separately, to be agreed, or another formulation. Do not standardize those phrases into a single included status. A reference to Schedule 3 and a file named Schedule 3 are observations; their legal relationship is a lawyer's question. Record nested references too, such as an exhibit that points to a technical appendix, without searching unrelated deal folders unless the owner expands scope.
Compare identities without silently merging them
Create one row for each referenced item and link candidate files beneath it. Compare labels, titles, dates, parties, page headers, version markers, and source locations. Exact filename equality is useful but not decisive, because filenames can be changed in transit. Conversely, similar content does not authorize merging two files. If duplicate-looking documents have different hashes, retain both and identify the observed differences that the approved tool can show. If hashes match, record the match while preserving both source paths. Counsel decides whether either candidate satisfies the agreement reference.
Work the competing Schedule 3 example
Assume the signed agreement refers to Schedule 3, while the closing folder contains Schedule 3 dated March 4 and another dated March 11. The later file arrived with the signature packet, but the earlier one carries initials on each page. The administrator records both candidates, their dates, page counts, hashes, source messages, and visible markings. The checklist stays unresolved. The administrator does not choose the later date, treat initials as assent, or splice pages into a new exhibit. Counsel reviews the negotiation and closing evidence, identifies the authorized version, and records a disposition that links back to both candidates.
Treat signatures and attachments as separate evidence
A signature block, electronic-signature certificate, initials, and an email attachment each show different facts. Capture what is visible and where it came from without declaring a signature valid or attributing an attachment to assent. If an exhibit has its own signature line, record whether it appears populated; do not infer that the main agreement signature covers it. If a certificate lists a document identifier, compare that identifier under the approved procedure. Questions about authority, execution, counterparts, delivery, and effectiveness go to counsel with the exact source reference.
Keep operational identity separate from evidentiary conclusions
A filename, hash, signature image, or transmittal can help distinguish records, but none lets an administrator decide authenticity, admissibility, or what must be treated as an original. Federal Rule of Evidence 1002 is one illustration of why questions about proving document content belong to legal analysis, not packet cleanup. Maintain the contract's own naming and a separate controlled display label if a destination system requires one. Do not rename the source file to make an index look tidy. Filing counsel approves exhibit numbers, redactions, omissions, hyperlinks, and submission format.
Escalate gaps with a narrow evidence question
A useful exception names the agreement reference, candidate files checked, authorized locations searched, and exact uncertainty. Examples include no candidate found, two plausible versions, title mismatch, date mismatch, missing pages, inaccessible file, broken cross-reference, or signature evidence that does not identify the exhibit. Avoid conclusions such as exhibit omitted from contract. Assign the question to the deal lawyer or records owner and preserve the reply as a new event. If counsel supplies a replacement, record its source and hash rather than overwriting the file that exposed the gap.
Test reconstruction, not cosmetic order
Pilot the checklist with a missing schedule, duplicate label, renamed file, nested appendix, different hash, unreadable scan, and exhibit signed separately from the agreement. Ask a second reviewer to reconstruct every row from its cited sources. Measure references captured, candidates linked, unexplained transformations, false merges, missing pages detected, lawyer corrections, and time awaiting dispositions. A beautifully combined PDF can still be wrong; a useful result is one whose provenance and unresolved questions are visible. Increase volume only after reviewers can reproduce the packet map without relying on the preparer's memory.
Close without erasing the decision trail
After counsel identifies the accepted packet, preserve the original inventory, exceptions, dispositions, and final file identities under the firm's records instruction. A compiled convenience copy should list its source components and creation details. Do not delete rejected candidates merely because they are not part of the accepted operational set. LegalServicesOffshore.com can help define a Philippines-based role for closing-packet inventory, cross-reference extraction, controlled comparison, and exception routing. The client and its lawyers retain decisions about incorporation, execution, authority, interpretation, filing, retention, and legal effect.
Plan source-linked contract packet administration with Contract Administration.
Sources
- NIST, Hash / Hash Value glossary
Checked for the limited use of hash values to substantiate digital-evidence integrity or compare known values.
- Legal Information Institute, Federal Rule of Evidence 1002
Checked as a reminder that document-content and original-record questions are legal evidence issues for counsel, not conclusions produced by an administrative checklist.
- State Bar of California, Rules 5.1–5.7: Law Firms and Associations
Checked as an accessible official jurisdictional example for supervision and nonlawyer assistance; the firm must apply each controlling jurisdiction.