Document Formats Every Small Business Should Standardise On
Why Format Chaos Costs Real Money
A plumbing company in Bristol recently spent three hours trying to open a quote sent as a .pages file on a Windows machine. The client called twice asking for a response. By the time someone figured out how to extract the text, the job had gone to a competitor. That is not a technology failure — it is a format standardisation failure, and it happens dozens of times a day in small businesses across every industry. The cost is rarely visible on a spreadsheet, but it accumulates fast. McKinsey research from 2023 estimated that knowledge workers spend roughly 20% of their time searching for information or recreating documents that already exist in an incompatible format. For a five-person team where each person earns £30,000 a year, that is £30,000 annually in wasted labour — just from format friction. Standardising on a short list of document formats does three things simultaneously: it reduces the time staff spend converting or troubleshooting files, it lowers the risk of data being lost in translation between formats, and it makes your business look more professional to clients and suppliers. This article covers the specific formats worth committing to, the ones worth avoiding for external documents, and where a conversion tool like CocoConvert fits into the workflow when legacy files inevitably arrive.
PDF: The Non-Negotiable Standard for Anything You Send Out
PDF (Portable Document Format) should be the only format you use for documents sent to people outside your organisation — invoices, proposals, contracts, reports, product sheets. The reason is simple: a PDF renders identically on every device, every operating system, and every screen size, assuming the recipient has any modern PDF reader, which essentially everyone does. Your carefully formatted invoice will not arrive with scrambled columns because the client is running LibreOffice 6.4 on Linux. For legally significant documents, PDF/A is worth knowing about. PDF/A is an ISO-standardised subset of PDF (ISO 19005) designed for long-term archiving. It embeds all fonts, prohibits encryption, and disallows external content references. If you are keeping contracts, tax records, or compliance documents for seven or more years — which UK law requires for most business records — PDF/A is the right choice. Adobe Acrobat Pro can export to PDF/A-1b via File > Save As > PDF/A. LibreOffice Writer can do the same under File > Export as PDF > PDF/A-1a. One honest caveat: PDFs are not ideal for documents that need frequent editing. If you send a proposal as a PDF and the client wants to redline it, you have created friction. In that specific case, a DOCX file is more practical. The rule of thumb is: DOCX for internal drafting and collaborative editing, PDF for anything that leaves the building in a final state. CocoConvert handles PDF conversion from most common formats — Word, Excel, PowerPoint, images, and HTML — without requiring software installation. That matters for small teams where not everyone has Acrobat Pro licences.
DOCX for Editable Documents: Compatibility Over Loyalty
Microsoft's DOCX format, standardised as ECMA-376 and ISO/IEC 29500, is the de facto global standard for editable text documents. That is not an endorsement of Microsoft as a company — it is a practical acknowledgement that DOCX files open correctly in Microsoft Word, Google Docs, LibreOffice Writer, Apple Pages, and WPS Office. No other editable format comes close to that level of cross-platform support. If your team works entirely within Google Workspace, you might be tempted to use Google Docs' native format (.gdoc files). Resist that temptation for anything shared externally. A .gdoc file is essentially a shortcut to a cloud URL — it contains almost no actual content and is useless to anyone without a Google account and access to your Drive. Always export or download as .docx before sending. Similarly, Apple's .pages format is a liability the moment you work with anyone outside the Apple ecosystem. Pages can export to DOCX under File > Export To > Word, but the conversion is imperfect for complex layouts. If you are on a Mac, set Word or LibreOffice as your default word processor and author in DOCX from the start. For templates — letterheads, proposal frameworks, meeting agendas — save master copies as DOTX (Word Template) files. This prevents staff from accidentally overwriting the template and keeps formatting locked. Store them in a shared folder with clear naming conventions: 2026_Proposal_Template_v3.dotx, not 'final final FINAL proposal.docx'.
Spreadsheets, Presentations, and the Formats You Actually Need
XLSX is to spreadsheets what DOCX is to text documents: the universal standard. It is supported by Excel, Google Sheets, LibreOffice Calc, and Numbers. For anything involving financial data, project tracking, or inventory management that you share externally, XLSX is the right choice. CSV is appropriate when you are exporting data to another system — an accounting package, a CRM, an e-commerce platform — because it strips all formatting and leaves only raw data, which is exactly what import tools expect. A common mistake is sending a live Excel file with formulas to a client or supplier. If the recipient edits a cell, the formulas break, and suddenly your carefully constructed pricing model produces nonsense. For spreadsheets sent externally that are not meant to be edited, export to PDF. For spreadsheets that need to be filled in by the recipient — a purchase order form, for example — consider using Excel's built-in data validation and sheet protection (Review > Protect Sheet) before sending as XLSX. For presentations, PPTX is the standard equivalent. PowerPoint, Google Slides, Keynote, and LibreOffice Impress all read PPTX files with reasonable fidelity, though complex animations and custom fonts sometimes degrade. If you are sending a presentation for someone to view rather than edit, export it as PDF. If you are presenting it yourself and cannot guarantee the venue's software, bring your own laptop or export to PDF as a backup. One format to avoid entirely for business documents: RTF. It was useful in the 1990s for cross-platform compatibility, but DOCX now does everything RTF does, better and more reliably. If you receive RTF files from older systems, CocoConvert can convert them to DOCX in seconds.
Images and Privacy: What Metadata Hides Inside Your Files
This section sits in the privacy category for a reason. When you photograph a document with your phone and send it as a JPEG, you are almost certainly sending more than the document. JPEG and PNG files contain EXIF metadata — embedded data that can include GPS coordinates, the device model, the date and time the photo was taken, and sometimes the device's serial number. For most business documents this is merely untidy. For sensitive documents — anything involving client addresses, financial details, or site surveys — it is a genuine privacy risk. A JPEG of a surveyor's site plan sent to a contractor might contain the precise GPS coordinates of the property. If that file is forwarded or leaked, the metadata travels with it. The solution is to strip metadata before sending. On Windows, right-click the file, go to Properties > Details > Remove Properties and Personal Information. On Mac, there is no built-in metadata stripper for photos; you need a third-party tool or you can export the image through Preview (File > Export) which drops most EXIF data. Converting the image to PDF using CocoConvert also strips most EXIF metadata in the process, which is a practical side benefit of converting phone photos to PDF before sending. For scanned documents, TIFF is the archival standard — it is lossless and widely supported by document management systems. However, TIFF files are large and impractical for email. The standard workflow is to scan to TIFF for archiving and export a compressed PDF for distribution. Most office scanners support this natively; on a Canon imageRUNNER, for example, you can set the scan destination to produce both simultaneously. If your business handles any personal data under UK GDPR, metadata management is not optional — it falls under the requirement to implement 'appropriate technical measures' to protect personal data.
Building a Simple Format Policy That Staff Will Actually Follow
A format policy does not need to be a 20-page document. In practice, a single A4 sheet pinned to a shared drive — or a pinned message in your team's Slack channel — is enough. The policy should answer three questions: what format do we use to create documents, what format do we use to send documents, and what do we do when we receive something in the wrong format? A workable one-page policy for a small business might look like this. Create all text documents in DOCX. Create all spreadsheets in XLSX. Before sending any document externally, convert it to PDF unless the recipient specifically needs to edit it. For images attached to business documents, use PNG for screenshots and diagrams, JPEG for photographs, and always strip metadata before sending. Archive contracts and compliance documents in PDF/A. The 'what do we receive' question is where conversion tools earn their place. Clients and suppliers will send you ODT files from LibreOffice, PAGES files from Mac users, WPS files from users in China and Southeast Asia, and ancient DOC files from businesses still running Office 2003. CocoConvert handles most of these conversions without requiring staff to install software or create accounts — upload, convert, download. It is honest to say that CocoConvert is not a replacement for full desktop software when you need precise formatting control on a complex document, but for the routine task of turning an awkward format into something usable, it removes friction. Review the policy once a year. Format standards do shift — EPUB is becoming more relevant as businesses create digital guides and manuals, and WebP is replacing JPEG for web-facing images in ways that affect marketing teams. A brief annual check keeps the policy from becoming outdated.
When to Convert and When to Push Back
Not every format problem requires conversion. Sometimes the right answer is to ask the sender to resend in a standard format, particularly if you will be receiving many files from that source over time. A supplier who consistently sends invoices as .pages files is creating ongoing friction; one polite email asking them to switch to PDF takes thirty seconds and solves the problem permanently. That said, there are situations where conversion is the faster path. A one-off document from a long-standing client, a file from an overseas partner where language barriers make format discussions awkward, or an archived file from a system you no longer use — these are all cases where converting the file yourself is more practical than negotiating a format change. CocoConvert's batch conversion feature is worth knowing about for the archiving scenario. If you are migrating from an old system and have 200 ODT files that need to become DOCX or PDF, uploading them one at a time is not viable. Batch conversion handles this in a single operation. It is worth noting that very complex documents — those with intricate tables, embedded macros, or non-standard fonts — may not convert perfectly in any automated tool, CocoConvert included. For those files, a manual review after conversion is always worth the five minutes it takes. Finally, consider what happens to files after conversion. If you are converting a document that contains personal data — a client contract, a staff record, an NDA — make sure the conversion tool you use does not retain copies of uploaded files. CocoConvert deletes uploaded files from its servers within one hour of conversion. For businesses handling sensitive data, that retention policy matters and is worth checking for any tool you use regularly. The format of a document is only part of the picture; where it lives during processing is the other part.