Multi-Document Packaging and Routing Orchestration

GuideUpdated: May 2026

This guide provides technical instructions for consolidating multiple digital assets into a single transactional envelope for sequential or parallel execution within the IUSign Enterprise platform.

This guide provides technical instructions for consolidating multiple digital assets into a single transactional envelope for sequential or parallel execution within the IUSign Enterprise platform.


Prerequisites

  • Administrative or elevated User privileges within a tenant.
  • Active Growth or Enterprise subscription tier.
  • Source documents in supported ISO-standard PDF or Microsoft Office formats.

Strategic Overview

Multi-document packaging allows for the orchestration of complex transactions involving several distinct assets (e.g., a comprehensive mortgage package or a multifaceted executive onboarding set). By grouping these assets into a single "packet," IUSign ensures a cohesive signing experience where recipients are guided through each document in a predefined logical sequence. This eliminates the need for multiple independent transactions and provides a unified audit trail for the entire document set.


Implementation Sequence

1. Initialization of Multi-Asset Envelope

Navigate to the Documents module and select New Envelope. For accounts on eligible tiers, the multi-document ingestion interface will be initialized by default, allowing for the concurrent upload of multiple files.

2. Digital Asset Ingestion and Sequencing

Select the target assets from your local environment or organizational repository. The platform supports:

  • Batch Ingestion: Selection of multiple files via standard OS-level selection (Ctrl/Cmd + Click).
  • Logical Sequencing: Drag and drop assets within the upload queue to define the signing order. The sequence defined here determines the order in which the recipient will encounter the documents during the execution phase.

3. Cross-Document Field Mapping

Utilize the Document Navigation Tabs at the header of the editor to switch between assets. This allows for the precise placement of cryptographic fields (Signatures, Initials, Dates) across the entire packet.

  • Persistent Assignments: A single recipient can have distinct signing requirements on each individual document within the package.
  • Data Inheritance: Specific fields can be configured to "echo" data across documents, reducing the effort for the recipient.

Signer Experience and Progress Tracking

The recipient's interface is optimized for high-density execution:

  • Guided Navigation: Signers are automatically advanced to the next document upon successful completion of the current asset's requirements.
  • Aggregate Telemetry: A real-time indicator shows the overall completion percentage of the entire packet (e.g., "Document 2 of 5 Complete").
  • Unified Execution: Upon final signature, a single Certificate of Completion is generated, cryptographically linking all assets in the packet into a single forensic record.

Technical Specifications

FeatureGrowth TierEnterprise Tier
Max Documents per Packet1050 (Customizable)
Combined File Size Limit50 MB250 MB
Recipient-Specific VisibilityStandardAdvanced (Conditional Access)

Diagnostic and Resolution Protocols

System ExceptionProbable CauseResolution Protocol
Multi-doc unavailableTier constraintVerify your Subscription Tier satisfies Growth+ requirements.
Incomplete signing errorField oversightEnsure all mandatory fields across all documents in the packet have been executed.
Asset indexing failureCorrupted source fileRe-upload the specific corrupted asset and re-sequence the envelope.

Related Documentation