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. By the time they figured out how to extract the text, the job had gone to a competitor. That isn't a technology failure; it's a format standardization failure, and it happens constantly in small businesses across every industry. The cost is rarely visible on a spreadsheet, but it adds up with frightening speed. A 2023 McKinsey study found that knowledge workers spend roughly 20% of their time just searching for information or recreating documents that already exist in an unusable format. For a five-person team where each person earns £30,000 a year, that is £30,000 in wasted salary — gone, just from format friction. Standardizing on a short, enforced list of document formats fixes this. It stops staff from wasting time troubleshooting files. It prevents data from being lost in translation between programs. And it makes your business look professional to the outside world. This is about choosing the right formats to commit to, which ones to avoid for external communication, and how a tool like CocoConvert can bridge the gap when you inevitably receive a file in a bizarre format.
PDF: The Non-Negotiable Standard for Anything You Send Out
PDF (Portable Document Format) is the only format you should use for documents sent outside your organization. Invoices, proposals, contracts, reports, product sheets—send them all as PDFs. Why? Because a PDF looks identical on every device, every operating system, and every screen size. Your carefully formatted invoice won't arrive with scrambled columns just because the client uses LibreOffice 6.4 on Linux. Anyone who has seen their beautiful design work turn into a digital train wreck on the client's end knows this pain. For legally significant documents, you need to know about PDF/A. This is an ISO-standardized version of PDF (ISO 19005) built specifically for long-term archiving. It embeds all fonts, forbids encryption, and disallows links to external content, ensuring the file can be opened and read correctly decades from now. If you're keeping contracts or tax records for seven-plus years, as UK law requires, PDF/A is the correct choice. Adobe Acrobat Pro can save to PDF/A-1b via File > Save As > PDF/A, and LibreOffice Writer can do the same under File > Export as PDF > PDF/A-1a. Of course, PDFs aren't great for documents that require editing. If you send a proposal as a PDF and the client wants to redline it, you've just created a roadblock. In that specific collaborative phase, a DOCX file is more practical. The rule is simple: draft and collaborate internally with DOCX, but send the final version out as a PDF. CocoConvert handles PDF conversion from all the usual suspects—Word, Excel, PowerPoint, images, and HTML—without needing to install any software. That's a huge benefit for small teams where not everyone can have a pricey Acrobat Pro license.
DOCX for Editable Documents: Compatibility Over Loyalty
Microsoft's DOCX format is the de facto global standard for editable text documents. That isn't an endorsement of Microsoft; it's a practical acknowledgement that a DOCX file will open correctly in Microsoft Word, Google Docs, LibreOffice Writer, Apple Pages, and WPS Office. No other format even comes close to that level of universal support. You have to choose compatibility over brand loyalty. If your team is all-in on Google Workspace, you might be tempted to share native Google Docs (.gdoc) files. Don't. A .gdoc file is just a shortcut pointing to a cloud URL. It contains no actual content and is completely useless to anyone without a Google account and the right permissions. Always download as .docx before sending a file to someone externally. Apple's .pages format is an even bigger liability the moment you interact with the 90% of the business world not using a Mac. While Pages can export to DOCX (File > Export To > Word), the conversion often butchers complex layouts. If you're on a Mac, do yourself and your collaborators a favor: set Word or LibreOffice as your default and create documents in DOCX from the very beginning. For templates like letterheads or proposals, save the master copies as DOTX (Word Template) files. This simple step prevents people from accidentally overwriting the original template and keeps the formatting locked down. Store them in a shared, clearly named folder: `2026_Proposal_Template_v3.dotx` is infinitely better than `final final FINAL proposal.docx`.
Spreadsheets, Presentations, and the Formats You Actually Need
For spreadsheets, XLSX is the undisputed king, just as DOCX is for text. It’s supported by Excel, Google Sheets, LibreOffice Calc, and Numbers, making it the only sensible choice for sharing financial data, project plans, or inventory lists. The only time to use something else is CSV. When you need to export raw data into another system—like an accounting package or a CRM—CSV is perfect because it strips out all formatting, which is exactly what data import tools need. Sending a live Excel file with all its formulas to a client is a disaster waiting to happen. If the recipient clicks the wrong cell, your entire pricing model could break and spit out nonsense. For spreadsheets that are for viewing only, send a PDF. If you need the recipient to fill something out, like a purchase order, use Excel’s built-in data validation and sheet protection tools (under the Review tab) before you send the XLSX file. When it comes to presentations, PPTX is the standard. PowerPoint, Google Slides, Keynote, and LibreOffice Impress all handle PPTX files with reasonable fidelity. Be warned, though: complex animations and custom fonts can get messy when moving between programs. If you're just sending the deck for someone to read, export it to PDF. If you are presenting it yourself, the safest bet is always to bring your own laptop or have a PDF version ready as a bulletproof backup. And one format to banish forever? RTF. It had its moment in the 90s, but DOCX has completely superseded it. If you get RTF files from old systems, use CocoConvert to turn them into modern DOCX files and move on.
Images and Privacy: What Metadata Hides Inside Your Files
When you snap a picture of a document with your phone and email the JPEG, you are sending a lot more than just the image. Image files like JPEG and PNG contain EXIF metadata, a hidden block of data that can include the exact GPS coordinates where the photo was taken, the phone model, the date and time, and even the device's serial number. For most business documents, this is sloppy. For sensitive files, it's a serious privacy breach. A photo of a site plan sent to a contractor could easily contain the precise GPS coordinates of a private property. If that file gets forwarded or leaks, the location data goes with it, creating a genuine liability for your business. The only professional solution is to strip the metadata before sending. On Windows, you can right-click the file, go to Properties > Details > Remove Properties and Personal Information. Macs don't have a simple built-in tool for this, so you either need a third-party app or you can export the image through Preview (File > Export), which removes most of the EXIF data. A much simpler workflow is to convert the image to a PDF using a tool like CocoConvert, which effectively strips the metadata as part of the conversion process. For scanned documents, TIFF is the archival gold standard because it's lossless and supported by document management systems. But TIFF files are huge and terrible for email. The professional workflow is to scan to TIFF for your internal archive, and then export a compressed PDF for sharing. Many office scanners, like a Canon imageRUNNER, can be configured to produce both file types at the same time. If your business handles any personal data under UK GDPR, managing this metadata isn't optional. It's a required part of implementing 'appropriate technical measures' to protect personal data.
Building a Simple Format Policy That Staff Will Actually Follow
A format policy that no one follows is useless. Forget a 20-page binder; for this to work, it needs to be dead simple. A single page, or even a pinned message in your team's Slack channel, is all you need. A good policy just provides clear, default answers for what formats to use for creating, sending, and receiving documents. A workable policy can be this straightforward: Create all text documents in DOCX. Create all spreadsheets in XLSX. Before sending anything to a client or supplier, convert it to PDF unless they absolutely must edit it. For images, use PNG for screenshots and JPEG for photos, and always strip the metadata before sending. Archive critical records like contracts in PDF/A. That's it. The tricky part is handling what you receive. Your clients and suppliers will send you everything: ODT files from LibreOffice, PAGES files from Mac users, WPS files from partners in Asia, and ancient DOC files from companies still running Office 2003. This is where conversion tools prove their worth. CocoConvert handles these odd formats without forcing your staff to install new software or create accounts. Just upload, convert, download. While it's not a substitute for desktop software when you need pixel-perfect control over a complex layout, it's the fastest way to turn an unusable file into a productive one. Take a quick look at this policy once a year. Standards evolve. EPUB is becoming more common for digital manuals, and WebP is changing how marketing teams handle images. A brief annual check-up keeps your policy relevant.
When to Convert and When to Push Back
Not every format problem needs a technical solution. Sometimes, the right move is to politely push back. If a supplier consistently sends you invoices as .pages files, you are signing up for ongoing friction. A single, polite email asking them to send PDFs instead takes thirty seconds and fixes the problem forever. Don't be afraid to train your partners on how to work with you effectively. Of course, there are times when just converting the file is the path of least resistance. A one-off document from a major client, a file from an overseas partner where language barriers make things tricky, or an old file from a system you no longer maintain—in these cases, converting it yourself is simply more practical. For big migration jobs, like moving 200 ODT files from an old server, CocoConvert's batch conversion feature is a lifesaver. Uploading them one by one is a soul-crushing task. Complex documents with intricate tables or macros might not convert perfectly in any automated tool, CocoConvert included. A quick five-minute manual review after conversion is always a smart investment for critical files. Finally, think about what happens to your data during conversion. If you're converting a sensitive document like a client contract or staff record, you must know what the tool's data retention policy is. CocoConvert deletes uploaded files from its servers within an hour. For any business handling sensitive information, that policy is a critical detail to verify for any cloud tool you use. The format is only half the battle; where your data goes is the other half.