Source files are released once project deliverables have received formal sign-off and the final invoice balance has been settled in full. Delivery is coordinated by Operations & Client Services, providing direct access to raw design files or code repositories prepared by the Creative or Technology departments.
Prerequisites for source file release
Before any working files or production code leave the studio, two operational conditions must be met:
1. Final sign-off: You must review the final deliverables and submit formal approval via the project portal or Ask Xylo chat. 2. Balance settlement: Any outstanding project fees or milestone payments must clear. Deposits are non-refundable once your production slot is held. Before work begins, sums not yet earned are refunded pro rata; after work begins, completed work and booked time are charged. Defects are fixed free of charge within the acceptance window. The full terms are on the Refund Policy page of the main site.
Once both requirements are confirmed by Operations & Client Services, the production team begins compiling the master project archive. If your project commenced under an ambassador referral discount (typically 10-30% confirmed on your initial quote), this reduction has already been calculated against your total balance; file packaging follows the exact same delivery standard.
What gets delivered by department
Deliverables are curated and packaged according to specific departmental standards, ensuring your internal team or subsequent suppliers can pick up the work cleanly:
Creative department For branding, graphic design, digital interfaces, and motion engagements, the Creative department exports all native working files alongside final production assets:
- Vector assets: Native Illustrator (.ai), SVG, and vector PDF files, cleanly organised with outlined and non-outlined typography variants.
- Interface designs: Transfer of ownership for Figma project files or master component libraries, complete with responsive layouts, design tokens, and style guides.
- Motion and media: Layered After Effects project files, Premiere timelines, raw footage sequences, audio stems, and associated project cache folders.
- Typography and asset licences: Working files reference licensed typefaces and third-party stock assets. The studio provides a font register containing names, version requirements, and foundry vendor links. Due to intellectual property laws, the studio cannot transfer proprietary desktop font licences directly; your organisation must hold independent licences for commercial typefaces.
Technology department For web development, software engineering, and infrastructure projects, the Technology department packages complete, production-grade repositories:
- Codebases: Transfer of repository ownership or full Git commit history pushed to your organisation's GitHub, GitLab, or Bitbucket organisation account.
- Configuration and environment files: An example environment file (`.env.example`) specifying required keys, schemas, and third-party service hooks. Live production API keys and private secrets are excluded for security.
- Documentation: A comprehensive `README.md` detailing local environment setup, build pipelines, package management commands, and deployment runbooks.
- Database schemas: Raw migration scripts, baseline schema definitions, and seed fixtures.
Delivery sequence and timings
File preparation and distribution follow a four-step sequence during our standard working hours (Monday to Thursday, 09:00 to 17:00 GMT):
1. Compilation: Operations & Client Services notifies the production team once payment is marked complete. Asset packaging takes between 24 and 48 hours depending on archive size. 2. Handover dispatch: Digital archives are issued via encrypted, time-limited transfer links. Code repositories are transferred directly by inviting your designated technical administrators. 3. Inspection window: You are granted a 14-day verification window to download the files, clone the repositories, inspect asset structures, and verify that local build scripts execute cleanly. 4. Archive closure: Once your confirmation is received—or the 14-day window elapses—the project staging environment is decommissioned and the master files are transferred to cold offline backup.
Client responsibilities and access windows
To ensure a seamless transfer without repeated exports, your organisation must provide:
- The name and direct corporate email address of the designated technical or creative asset custodian.
- Verified repository usernames or organisation team handles prior to repository transfer.
- Adequate local or cloud infrastructure to store the final deliverables. Layered multimedia, video, and 3D archives routinely exceed 20 GB.
Download links expire 7 days after issue. You must pull all files locally within this timeframe to avoid transfer resets.
Edge cases and delivery issues
If a download link expires before your team captures the files, or if an archive encounters a checksum mismatch during decompression, raise a request immediately via Ask Xylo chat on this portal. Operations & Client Services will review the project log and generate a fresh transfer link.
Our team operates Monday to Thursday, 09:00 to 17:00 GMT, with a first reply target of 24 hours. In the rare event that an imported design symbol, linked texture, or code submodule is missing from the compiled package, the original project lead from Creative or Technology will inspect the master working files and issue an incremental patch.
Handover checklist
- Confirm project completion and provide sign-off via Ask Xylo chat.
- Settle any outstanding invoices with accounts.
- Supply verified repository handles or custodian contact details.
- Download all master archives to permanent internal storage within 7 days of link issue.
- Unpack and test repository build commands or design assets locally.
- Confirm successful handover receipt within the 14-day verification window.