Specify company-profile outputs by use, not by asking only for a “high-quality PDF.” An emailed copy needs readable content, useful links and a size appropriate to its delivery channel. A printed version needs production specifications and separate approval. An editable master needs to open in your team's environment and survive a real amendment. These outputs can share content without sharing every export setting.
Before requesting a quotation, identify readers, devices, future editors and any selected printer. If printing is undecided, separate digital design from production preparation rather than accepting assumptions that may not suit the eventual supplier.
Define an output schedule
| Deliverable | Purpose | Practical acceptance test |
|---|---|---|
| Digital sharing copy | Email, download or direct sharing | Readable text and working links within an agreed size limit |
| Print-production output | Production by a specified printer | Printer requirements, specialist review and proof approval completed |
| Editable source | Future internal updates | Opens in the agreed application and supports a successful edit and export |
| Release record | Identifying approved versions | Connects language, purpose, date and exact file |
Include this schedule in the company profile design brief. “Open files” does not establish the application, fonts, linked images or testing responsibility. A file may open yet be impractical to maintain if every word is a separate object or the entire page is an image.
Test the digital copy in context
Open the output on representative phones and computers, move between pages and test website and email links. Decide whether users need text selection or search. Check the filename, page orientation and any agreed navigation features.
Do not compress photographs until useful project detail disappears merely to achieve an arbitrary small size. Compare alternatives if needed and choose the version that supports the actual sharing task. If a recipient's portal imposes an upload limit, record that specific requirement rather than treating it as a universal rule.
Google can index PDF files. Choose web pages or PDFs according to use and maintenance needs, not an assumption that PDFs cannot appear in search. Indexability does not guarantee inclusion. Google's supported file types.
Treat print preparation separately
Obtain the printer's requirements for final size, binding, margins, colour handling, images and page delivery. Do not select generic settings and expect the printer to resolve the differences later. Adobe documents PDF export controls for printer's marks, bleed and colour output; the production specification determines the appropriate choices. Adobe export guidance.
Before committing to production artwork, confirm an accountable, qualified prepress reviewer and verify representative output accepted by the intended printer. A screen-approved cover does not establish that the complete document is production-ready. Define the required proof, reviewers, release authority and changes that trigger another proof.
Include approved colour references and logo rules from the visual identity. Do not promise identical appearance across every screen and paper. Agree an appropriate reference and assessment method with the production specialist and printer.
Worked hypothetical: email distribution and a short print run
An imaginary supplier needs a twelve-page Arabic–English profile for customer emails and an in-person meeting. The page count illustrates a possible scope, not a recommended standard. The team approves one content reference but commissions two digital sharing files and two language-specific production outputs.
It tests links and table legibility in both digital versions. Print preparation waits for the printer's requirements and then uses a representative sample containing a photograph, information page and table. The team does not automatically send the sharing copy to print simply because it looks attractive on a laptop.
At handover, the internal owner changes a contact detail in the source and exports the file again. This establishes that the intended maintenance task is practical. When an email address changes after approval, the owner updates the source and all four outputs, then withdraws earlier sharing copies. Correcting the digital version alone would leave the next print run outdated.
Prevent handover surprises
Agree fonts, image assets and rights to transfer or reuse them before production. An asset may be licensed for inclusion in a design without being transferable in every form. The rights owner should verify relevant terms, with specialist advice where needed. Do not promise delivery of rights neither party possesses.
Identify the content owner and update route. When services change frequently, content strategy and production can help establish a maintainable text reference rather than a collection of contradictory exports.
Use a practical acceptance session:
- Open the source in the intended environment and check missing assets.
- Change a representative paragraph and contact field.
- Export the appropriate output using the documented settings.
- Compare text, imagery and links with the approved reference.
- Confirm which files are for sharing, editing and production.
- Record the release owner and location of the approved masters.
Common traps include treating a large file as inherently print-ready, assuming a smaller file is unusable for every print process, and confusing approval of wording with approval of production settings. Specify and test the use case instead of relying on the filename.
Frequently asked questions
Can one file serve digital and print uses?
Sometimes, but establish both sets of requirements before deciding. Separate acceptance criteria make it clear whether a single output genuinely meets them.
Does an editable source make every element editable?
Not necessarily. Define the elements your team must change, the application, transferable assets and fonts, then test a representative update.
Who approves printing?
Assign content, brand, technical prepress, proof and final release responsibilities explicitly. Approval of wording should not silently approve every production choice.
What should we send LAB first?
Provide sharing methods, languages, editing needs and printer specifications if available. These establish which work is ready to scope and which production dependencies still require verification.