Fixed quote after a free call

Certificate of conformance and quality records, assembled for you

Quality teams spend hours assembling paperwork: certificates of conformance, material certs, inspection reports and first article records for each shipment, plus nonconformance and corrective action records and calibration dates. We build a workflow that gathers the right documents per order from your ERP and file storage, drafts the CoC for the quality manager to sign, keeps NCR and CAPA records together and reminds the team before calibration and maintenance fall due. A typical build costs $1,000 to $2,500 and takes about four to five weeks.

The problem

Why certificate packs hold up shipments

Many customers will not accept a shipment without a complete certificate pack. Finding the right heat-lot cert, the inspection report for this batch and the correct CoC template for this customer, often at the end of the day as the truck waits, is slow and error-prone.

Nonconformances and corrective actions have the same problem: emails, photos and notes spread across inboxes, so the record is rebuilt when an auditor or customer asks. Calibration and preventive maintenance dates live in spreadsheets that only one person checks.

What we build

What our quality document automation includes

Shipment cert packs

CoC, material certs, inspection reports and any customer-specific forms gathered per order and lot into one PDF pack.

Draft CoC

The customer's CoC template filled from order and lot data, left unsigned for the quality manager.

Missing document flags

Orders due to ship without a required cert or report listed for quality the day before.

NCR and CAPA records

Nonconformance reports, photos, emails and actions kept together in one record with owners and due dates.

Calibration and maintenance reminders

Gauges and equipment tracked with due dates and reminders before they lapse.

Audit evidence index

A searchable index of quality records by order, part, lot and date for audits.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Order ready to ship

    The ERP shows an order is ready, which starts the pack.

  2. 02 Automated

    Documents gathered

    Certs and reports are found by part, lot and order and assembled.

  3. 03 Automated

    Gaps flagged

    Missing documents are listed for quality before the ship date.

  4. 04 Office review

    Quality reviews

    The quality team checks the pack and the draft CoC.

  5. 05 Estimator or quality manager decides

    Sign-off

    Signing the CoC, releasing product and closing NCRs is the quality manager's decision.

How it behaves

How certificate packs and records behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • A complete certificate pack with each shipment
  • The right CoC template for their requirements
  • Fewer document queries

What the quality team sees

  • Draft packs and CoCs ready to check
  • A day-before list of missing documents
  • NCR records and calibration reminders in one place

What the automation does

  • Matches documents to orders and lots
  • Drafts certificates without signing them
  • Indexes every record for audits

Edge cases and fallbacks

Material cert missing for a lot
Shipment flagged; nothing is substituted.
Customer changes its CoC template
Old template retired and quality approves the new one.
Lot data inconsistent in the ERP
Flagged for quality to correct before the pack is built.
Storage or n8n outage
Quality builds the pack by hand as before and the run is retried.

Architecture

Certificate packs and quality records at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
ERP Orders, lots Document store Certs, reports n8n workflow Gather, match Cert pack CoC draft, PDFs NCR records Actions, owners Quality manager Signs, closes Audit index By order, lot
  • Input
  • Logic and services
  • Output
  • Data
  • People

How it flows

  1. 1 Orders ready to ship and lot data come from the ERP; certs and reports from your document store.
  2. 2 The workflow gathers documents per order and lot and drafts the CoC.
  3. 3 Missing documents and open NCRs are listed for the quality team.
  4. 4 The quality manager signs and releases, and every record is indexed for audits.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Certificates of conformance & quality records project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Customer cert requirements, where documents live, NCR process and calibration records.

  2. 02

    Design

    2 to 3 days

    Pack rules per customer, CoC templates, NCR record layout and reminders.

  3. 03

    Build

    About 2 weeks

    Document matching, pack assembly, CoC drafts, NCR records and reminders.

  4. 04

    Shadow run

    About 1 week

    Packs built for real shipments while quality builds its own, compared side by side.

  5. 05

    Launch

    1 to 2 days

    Switch on for the customers with the strictest requirements first.

  6. 06

    Support

    Ongoing

    New customer templates and record types.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Your ERP API for orders and lots SharePoint (Microsoft Graph) or Google Drive PDF assembly service Microsoft Teams or Slack for reminders

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Customer requirements, templates and record layout.

    $200 – $450

  • Build

    Matching, pack assembly, CoC drafts, NCR records and reminders.

    $500 – $1,250

  • Integrations

    ERP, document storage and alerts.

    $150 – $400

  • Testing and shadow run

    Packs compared with quality's own.

    $100 – $250

  • Launch and training

    Switch-on and quality team walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. A full QMS replacement is out of scope; we work with the system and storage you have. Storage and n8n are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Document storage: Your Microsoft 365 or Google Workspace plan.
  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

EU: technical documentation and DoC

For CE-marked products the manufacturer keeps technical documentation and the EU declaration of conformity up to date and for at least 10 years after the product is placed on the market.

Source: europa.eu

US: medical device quality systems

21 CFR 820.10 requires device manufacturers to document a quality system meeting ISO 13485; our records support that system and never replace the quality manager's approvals.

Source: www.law.cornell.edu

Signatures stay human

Automation drafts certificates; a named person signs and releases product.

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Certificates of conformance & quality records questions, answered.

It fills the CoC from order and lot data and gathers the supporting certs and reports. Our workflow does that inside your existing systems and leaves the signature to the quality manager.

It works alongside one. If you have a QMS, we connect to it; if your records live in SharePoint or a shared drive, we organise and index them there.

It keeps each NCR's photos, emails, actions and owners in one record with due dates and reminders. Disposition and root cause decisions stay with quality.

An index of records by order, part, lot and date makes evidence quick to find. Meeting the standard is still your quality team's responsibility.

It supports document control and records that those systems rely on. We follow your procedures; certification remains between you and your registrar.

Shipments leaving with a complete pack, packs rebuilt after customer rejection, NCR age and calibration items overdue.

Free 20-minute call

Want this for your manufacturer?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call