Skip to Content
Colabmo
  • Services
  • Learning
  • Experts
    Diggy Breiling, Colabmo quality systems and regulatory compliance expert

    Diggy Breiling

    Quality, Compliance, ERP/PLM
    Susan Haynes, Colabmo electrical engineering and embedded systems expert

    Susan Haynes, MS

    Electrical, Firmware, Medical Devices 
    Keri Austin, Colabmo ecommerce and digital marketing expert

    Keri Austin

    Ecommerce, Marketing Automation
    Colabmo component engineering and supply chain expert

    Adam Doolittle, BS

    Component Engineering, Supply Chain 
    Andrei Aleinikov, PhD, Colabmo creativity and innovation expert

    Andrei Aleinikov, PhD

    Creativity, Innovation, Learning 
    Angela Clarke, RN, Colabmo workplace health and first aid expert

    Angela Clarke, RN

    Workplace Health, First Aid, Training

    You could be here.

    Seeking Subject Matter Experts.

    Meet Our Experts

    Explore the full directory and find expertise relevant to your project.

    View All Experts
  • About
  • 0
  • Sign in
Colabmo
  • 0
    • Services
    • Learning
    • Experts
    • About
  • +1 (941) 416-1578
  • Sign in
  1. Courses
  2. Good Documentation Practices for Manufacturers and Distributors
  3. 02 · Make entries, signatures and corrections honestly
Nav
Home └Good Documentation Practices for Manufacturers and Distributors └02 · Make entries, signatures and corrections honestly

Good Documentation Practices for Manufacturers and Distributors

0 %

Completed

Course content
  • Uncategorized
    • 01 · Start with records people can trust
    • 02 · Make entries, signatures and corrections honestly 10 xp
      • Quiz
    • 03 · Use the right document for the job
    • 04 · Keep receiving and distribution records connected 10 xp
      • Quiz
    • 05 · Complete travelers and inspection records
    • 06 · Store, retrieve and retain usable evidence 10 xp
      • Quiz
    • 07 · Use electronic systems and AI responsibly 10 xp
      • Quiz
    • 08 · Workshop: review a shipment record package
    • 09 · Final knowledge check 10 xp

02 · Make entries, signatures and corrections honestly

10 XP
Prev Next
Fullscreen Share

Your outcome: Correct an error without hiding the original, and distinguish an event date from a later entry or approval date.

Make the record understandable

Use the approved form or system. Identify the job or item, relevant units and the person performing the work. Record the observation when the work occurs. Do not sign a step in advance, fill gaps with guesses, or copy a previous result because today's value is missing.

Follow the organization's unambiguous date convention. For example, 2026-10-05 and 05-Oct-2026 are readable ways to show 5 October; neither is a universal course requirement. Include the required time and time zone when sequence or elapsed time matters.

Correct the entry, preserve its history

For a paper record, follow the approved correction method. A common method is one line through the incorrect entry so it remains readable, the correct entry, the correcting person's identity and actual correction date, with a reason when required or needed to understand the change. Do not obscure the original with erasure, correction fluid or a replacement page presented as the original.

For an electronic record, use the approved correction or amendment function. Retain the original value and the context of the change as required by the system and procedure. Do not edit an exported PDF to conceal an error in the source system.

Late entries and missing evidence

If an observation was not recorded at the time, report the gap. Where the procedure allows a late entry, identify it as late, record the actual entry date, distinguish any supported event date, state the source and reason, and obtain the required review. If the result cannot be established, record that uncertainty and let the authorized owner decide the disposition.

Sign only within your authority. Distinguish performed, checked and approved. Use your own account; another person's login or pasted signature does not demonstrate their review. A specimen-signature register is one possible organizational control, not a requirement created by this course.

Worked example

A count sheet says 120 units, but the preserved count evidence supports 102. The receiver makes an authorized correction showing both values, identifies who changed it and when, and explains the transposition. If product was already issued using 120, the stock and downstream impact also need review.

Practice: Write a fictional late-entry note that states what is known, what evidence supports it, and what remains unknown.

Practice check: Complete the two questions attached to this lesson, then review the answer explanations before continuing.

  • ​ About
  • Comments (0)
Correct an error without hiding the original, and distinguish an event date from a later entry or approval date.
Rating
0 0

There are no comments for now.

Join this Course
to be the first to leave a comment.

1. The receiving record says 120 pieces. You recount and establish that 102 were received. What should happen?
Replace the record with a clean copy showing 102, without preserving the original. Correct the record through the approved process, preserve the original entry and assess affected stock records. Leave 120 because the original entry is already signed.
2. Yesterday’s inspection was performed, but you did not record the result. Today you cannot establish the measured value. What is the sound response?
Enter a typical value and use yesterday’s date. Ask AI to estimate the value from nearby inspections. Report the gap and follow the approved late-entry or investigation process without inventing a result.
Prev Next

Subscribe to the Colabmo newsletter

Practical insights on quality systems, operations, ERP workflows and technical projects, plus guides and learning updates.

Thanks for subscribing!

Subscribe

By subscribing, you agree to receive the Colabmo newsletter. You can unsubscribe at any time. See our Privacy Policy.

Useful Links

  • Home
  • Privacy Policy
  • Contact us

About us

Practical expertise for quality systems, operations, ERP workflows and technical projects. Review. Implement. Verify. Improve. We help plan the work, check results and equip your team to sustain progress.

Colabmo also operates FPD.DEV — display, embedded systems & Edge AI engineering.

Cookie Policy

Copyright © 2026 Colabmo.
Powered by Colabmo

We use cookies to provide you a better user experience on this website. Cookie Policy

Only essentials I agree