ifudocs

12 questions to ask a documentation hosting provider

If you plan to provide instructions digitally under Regulation (EU) 2023/1230, put these twelve questions to every provider you look at, us included. Our own answer is under each one, and two of them are not a full yes.

Three questions carry more weight than the rest. They are your own domain (2), the ten years in the contract (6) and the export (11). Together they decide whether you can leave a provider without changing a single label on a machine. Everything else can be fixed later. A printed QR code cannot.

  1. Does every machine get a permanent URL?

    The address on the nameplate has to work for the life of the machine. If the address belongs to a document instead of a machine, it breaks at the first revision.

    With ifudocs every serial number has its own page, and the address never changes.

  2. Can it run on our own domain?

    A code that points to the provider's domain ties every machine you ship to that provider. A code on your domain keeps the decision with you.

    Yes, in every plan. Your subdomain, one DNS record.

  3. Does it generate and manage the QR codes?

    Someone has to make a code for each serial number, sized and with error correction that survive dust and oil, and keep track of which code went on which machine.

    We make the codes and send them as image files ready for the nameplate.

  4. Can the customer download and print?

    Article 10(7) requires it. A viewer that only shows the document in the browser does not meet it.

    Every document is a normal file to download and print.

  5. Does it work offline, during a breakdown?

    The regulation asks that the user can save the instructions on a device. A downloaded file has to open without the platform and without a connection.

    Downloaded files are ordinary files and open anywhere.

  6. Are the ten years in the contract?

    The obligation is yours and runs at least ten years after the machine is placed on the market. A promise on a website is not a contract, and a contract is no use without a way out.

    We plan for ten years after delivery. What goes into the contract is the exit, meaning notice and a final export if the service ever stopped. With the codes on your own domain, the ten years never depend on us alone.

  7. Does the link survive a revision?

    When a manual is revised, the code on machines already in the field cannot change. Decide whether it should open the version delivered with that machine or the current approved one, and check that the platform does both.

    You choose per product. Old versions are archived and never overwritten.

  8. Can a customer confirm it is the right machine?

    The page should show the model and serial number, so the technician knows the document applies before downloading it. There should also be a way in when the label is damaged.

    Each page shows the model, serial number and its documents. A start page where customers look a machine up by model or serial number is set up for each customer.

  9. Can selected documents be protected?

    Service manuals, wiring diagrams or software are often meant for your technicians only, while the operating manual is public.

    Not a full yes. We are building it with our first customers, so tell us which documents need it.

  10. Which file types does it accept?

    Documentation is rarely only PDF. Drawings, spreadsheets, declarations and video often belong with the machine.

    Any file type.

  11. What do we get if we leave?

    Ask what the export contains, in what form and how often. An export you can actually run on another server is worth more than a backup promise.

    A full export after every update with the files, the record, the codes and the finished pages, ready to run on any web server. We also keep our own separate copy.

  12. Is there an API or folder synchronisation?

    If your documentation lives on a PC or NAS, automatic synchronisation saves work. If you have developers, an API lets you build your own workflow.

    Not yet. Updates run as a managed service. You send new or revised files and we publish them, within two working days on Standard and Pro. An upload workflow can be agreed per customer.

Send us your own list

If you are comparing providers, send us your requirements and we reply in writing, point by point. What the regulation itself asks for is in digital instructions under Regulation (EU) 2023/1230, and how ifudocs works is on the main page.

ales@ifudocs.com