Compliance tasks: who does which conformity document, by when, and what proves it was done

From the list to a reviewed record

1. From the saved list
   Save a sheet and every document the engaged regimes expect (technical file, declaration, risk assessment, test reports, labelling and instructions, traceability, certificates) and every duty that continues after sale (incident reporting, recall readiness, market surveillance cooperation, traceability records, security updates) becomes an item, per product and per market. A product the dictionary cannot place gets one item: classify it by hand. The item set is expanded on the server from the same published dictionary the sheet uses, never typed in.
2. Assign it
   Pick items by product, market, regime or owner and assign them to an owner or editor of your account, with a due date you type, a priority and a note. A viewer sees the board and changes nothing. Solo is one person; Team adds teammates with owner, editor and viewer roles.
3. Track it
   The team board has five columns: open, in progress, awaiting review, done and not applicable. My tasks lists what is yours, due soonest first. Waiting on me to review lists what others submitted. An item past the due date your team set is marked overdue by the time zone of the person looking at it. Mark an item as waiting on a test lab, supplier, retailer or notified body, with the date you asked.
4. Complete it
   An item is completed with evidence by reference (the document name, where it is kept, its version and its date) or marked not applicable with a written reason. No file is uploaded: the evidence stays in your own document system and the board keeps the reference.
5. Review it
   An owner or editor accepts the item or returns it with a reason. On an account with more than one owner or editor, the person who submitted an item cannot accept it. A done item can be reopened with a reason when a certificate expires or the product changes; the earlier evidence stays in the trail.
6. Keep the record
   Every step (added, assigned, due date set, started, waiting, submitted, accepted, returned, reopened, note) is written to an append-only trail with who and when; the database refuses an edit or a deletion. Re-save a changed product list and new products or markets add items, removed ones are archived with their evidence, and a product that comes back is restored. Export the tasks and the trail as CSV, or the whole board as XLSX.

Periods from the text, shown as guidance

Where the text of a mapped regime sets a period on a document or a duty (27 such notes across GPSR, the Machinery Regulation, the Cyber Resilience Act, MDR, IVDR, the CPSC and ISO 13485), the item shows it beside the clause it comes from: for example, technical documentation kept for ten years, or a serious incident reported within set days of awareness. It is guidance. The due date on the item is the one your team types, and an open-ended duty never gets a computed date. Named regimes are described in our own words and set no period here.

What each plan carries

• Free
  The specimen board: the specimen sheet as items, with an invented team, invented states and invented dates. Nothing can be changed.
• Solo
  Compliance tasks on your saved sheet for one person: due dates you set, evidence by reference, not-applicable reasons, the trail, CSV and XLSX export.
• Team
  Everything in Solo for the whole team: assignment to teammates, My tasks, the team board, waiting on me to review, review and return with a reason, no self-acceptance on a team, hand over a person's open items, the trail export for your auditor.

Optional email reminders for items due soon are built and switched off; they are not sent.