Predating Document Effective Date

QuinnM

Involved In Discussions
#1
Opinions…

A document has an effective date of 5-Jan-2017.

All approvers signed the document on 20-Feb-2017, after the effective date.

Would this be an issue for the FDA or EU (ISO 13485/MDD)?
 
Elsmar Forum Sponsor

Marc

Fully vaccinated are you?
Leader
#2
What would happen if one or more "approvers" refused to do so for some reason?

In short - A document must be reviewed and approved prior to use.
 

Ronen E

Problem Solver
Moderator
#3
Opinions…

A document has an effective date of 5-Jan-2017.

All approvers signed the document on 20-Feb-2017, after the effective date.

Would this be an issue for the FDA or EU (ISO 13485/MDD)?
Hello QuinnM and welcome to the Cove :bigwave:

A pedantic auditor might make a minor observation off that.
A reasonable auditor will likely treat the date the last approver signed off as the de-facto effective date.
 

v9991

Trusted Information Resource
#4
Opinions…
A document has an effective date of 5-Jan-2017.
All approvers signed the document on 20-Feb-2017, after the effective date.
as principle & practice, "Effective date" is assigned after approval & training. (beyond what Marc has pointed out, training before approving the procedure is not a good practice; especially not recommended (objectionable) for revision/changes to the SOP)


Opinions…
Would this be an issue for the FDA or EU (ISO 13485/MDD)?
Agree with Ronen; this would certainly be an issue (observation) for an auditor; from perspective of document-control & change management.
 

Marc

Fully vaccinated are you?
Leader
#5
I'm a bit prickly about document control. In DoD work, such a document would be close to fraud, will ring all sorts of bells and throw up red flags. A document simply isn't effective until review(s) and approval(s) are complete. After that it may be given an "effective date" and released. HOWEVER, no person(s) can use it until the person(s) has (have) been trained on it.

Were I an ISO 9001 auditor, if there was a "one off", you'd get a "gimme" (no problem - observation probably). But if it was a common practice it would be a major finding in document control, were I the auditor. It simply isn't the way a valid document control system works.
 

Ninja

Looking for Reality
Trusted Information Resource
#6
I'm not in Medical at all, so read this with that knowledge in case it makes a difference.

You do stuff (a process- rev A)
At some point the process must be changed for a valid reason (a process - rev B) {Day 10}
...but you're not sure rev B process works...
So you try it {Day 15}, and test it {Day 25}, and tweak it {Day 50}, and validate it {Day 75} until you have a process that works again.
Now you have to update your document, and do so {Day 85}
...and it gets approved... {Day 100}
...and distributed for use {Day 101}

Which day did you start "using the process" ? Pretty much Day 50
When did you confirm it was the right process to be using? Pretty much Day 75
When did you document it? Pretty much Day 85
When was the doc approved? Day 100
When was the approved document distributed for use? Day 101

Which one is the "effective date"?
If it is de-facto Day 100...what did you do with the stuff made by that exact same process earlier than that?

The document is "effective" when people have the ability to follow the approved document...Day 101.
The use of the process documented started Day 50.
The use of the documented process started on Day 101.

I guess the real question here is whether the documentation follows the process, or vice versa. Chicken and Egg-ish.

If I ran 5 days production as a final validation before locking it down in the approved doc...do I really have to scrap it all, after following the exact same process in all respects, just because the Document de-facto effective date is later?
 

Marc

Fully vaccinated are you?
Leader
#7
I can see this, Ninja, but then you are going to have to put in special controls as you "test and tweak". I know the process you describe is often used. In fact, I put such documents in "Level 5" of a document hierarchy back in the 1990's along with "Temporary Change" documents. Did that in the 1980's in DoD work.

Your description is of a "special circumstance" situation. Whether or not you have to "scrap it all" depends upon the contract language as well as communication/coordination with the customer(s). It is also often referred to as a "running process change". It often involves a contract change, and I have seen customers wanting a lower price since the original contract was for a specific part made by a specific process. This is where "why are you changing the process" can become an issue for discussion with the customer.

Then again, if a company is making drywall screws to sell to hardware stores a process change will likely not be an issue. How big of an issue it is depends upon the actual product. How about titanium joints for humans? How abut heart valves and artificial hearts? What about rubber ducks for children to play with in the bathroom?
 

Ronen E

Problem Solver
Moderator
#8
Were I an ISO 9001 auditor, if there was a "one off", you'd get a "gimme" (no problem - observation probably). But if it was a common practice it would be a major finding in document control, were I the auditor. It simply isn't the way a valid document control system works.
Yes, I agree, I addressed it as a one-off.
 

Ronen E

Problem Solver
Moderator
#9
I'm not in Medical at all, so read this with that knowledge in case it makes a difference.

You do stuff (a process- rev A)
At some point the process must be changed for a valid reason (a process - rev B) {Day 10}
...but you're not sure rev B process works...
So you try it {Day 15}, and test it {Day 25}, and tweak it {Day 50}, and validate it {Day 75} until you have a process that works again.
Now you have to update your document, and do so {Day 85}
...and it gets approved... {Day 100}
...and distributed for use {Day 101}

Which day did you start "using the process" ? Pretty much Day 50
When did you confirm it was the right process to be using? Pretty much Day 75
When did you document it? Pretty much Day 85
When was the doc approved? Day 100
When was the approved document distributed for use? Day 101

Which one is the "effective date"?
If it is de-facto Day 100...what did you do with the stuff made by that exact same process earlier than that?

The document is "effective" when people have the ability to follow the approved document...Day 101.
The use of the process documented started Day 50.
The use of the documented process started on Day 101.

I guess the real question here is whether the documentation follows the process, or vice versa. Chicken and Egg-ish.

If I ran 5 days production as a final validation before locking it down in the approved doc...do I really have to scrap it all, after following the exact same process in all respects, just because the Document de-facto effective date is later?
I do come from the medical field, so what I write applies mostly (if not only) to it.

I actually don't like the concept of a formal "effective date" (ie something printed on the document itself) at all. I'm fine with a declared effective date in change control documentation though. In my opinion and experience an effective date is more of a result than an origin, though it's useful to document a target effective date for purposes of orderly management. What I do find important is a documented understanding of when a document becomes effective, and in my opinion using the last approval signature's date for that purpose is simple, practical and typically regulatory-compliant. I can't remember a regulatory requirement that dictates imprinting a formal effective date. All quality systems I have been involved with (there were one or two :)) implemented that approach.

Coming back to Ninja's questions, in the medical industry products made for final validation are typically usable / sellable provided that the (documented) settings used in their making are within the eventually approved ones. Such products are usually quarantined until final approval and then released for use / sale. Products made prior to the final validation (usually smaller quantities) are typically scrapped / recycled / archived (depending on the particulars).

Cheers,
Ronen.
 
Last edited:

Jen Kirley

Quality and Auditing Expert
Leader
Admin
#10
Good responses so far. :agree1:

I cannot understand why have both an "effective date" and an approved date. A document becomes effective at the time it is released, that is after all approvals are completed; as has been pointed out, one of the approvers may have asked for a change.

If you must have an effective date, it should be the date the revised document was released to users. So says the ex-Document Control Queen... (did it for almost four years)
:2cents:
 
Thread starter Similar threads Forum Replies Date
T Document Review Process Map AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 4
A Introducing a document control system benefits Document Control Systems, Procedures, Forms and Templates 5
J ISO 9001:2015 Document Revison History ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 8
G Record test data into Word document Document Control Systems, Procedures, Forms and Templates 3
A Digital Document Control - Revision ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 13
T Ensuring Document Review AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 3
T TipQA Document Management AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 1
A Document control system for QMS in Google Drive? Document Control Systems, Procedures, Forms and Templates 6
M On-demand EU MDR Compliance toolkit with online training courses, templates & document management system Training - Internal, External, Online and Distance Learning 0
C Document Record/Template Minimum Requirements ISO 13485:2016 - Medical Device Quality Management Systems 3
E Do anyone have document of automotive production risk and control of risk? Lean in Manufacturing and Service Industries 1
Q Document representation ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 7
J Document Control of Online Management Software ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 10
W Document control Document Control Systems, Procedures, Forms and Templates 10
D Increasing efficiency - Capt. Proj. Document Review Matrix Document Control Systems, Procedures, Forms and Templates 4
A ISO 9001:2015 8.5.6 and 7.5.3 Document Control Questions ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 5
qualprod Sheets into a spreadsheet document control ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 4
J Document Changes that don't have to be approved Document Control Systems, Procedures, Forms and Templates 11
D Electronic Document Management System ISO 13485:2016 - Medical Device Quality Management Systems 16
M Document Control - Applying Suitable Identification to Obsolete Documents ISO 13485:2016 - Medical Device Quality Management Systems 7
D Document Control Question involving DocuSign US Food and Drug Administration (FDA) 6
M Document Control ISO and FDA ISO 13485:2016 - Medical Device Quality Management Systems 7
D Document Change Approval ISO 13485:2016 - Medical Device Quality Management Systems 6
R Does anyone use iQMS for their ISO based document control? Manufacturing and Related Processes 5
C Document Identification Question ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 8
B Document retention Policy for Japan's PMDA Japan Medical Device Regulations 1
B Document Retention Policy for NMPA China Medical Device Regulations 1
B Document Retention period for MHRA submission UK Medical Device Regulations 0
A If document coding is change will there be a revision Document Control Systems, Procedures, Forms and Templates 1
S Document numbering question? ISO 13485:2016 - Medical Device Quality Management Systems 7
R Quality policy review document IATF 16949 - Automotive Quality Systems Standard 3
dpenbert AS9100 7.5.3 - Manual Document Control AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 6
S Software design document NMPA guidance and consultant China Medical Device Regulations 4
qualprod Is it worth to document all the processes? ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 7
S Help in document control procedure Document Control Systems, Procedures, Forms and Templates 14
P Which MDCG Document should I use for PMS Plan and PSUR? EU Medical Device Regulations 2
N API Q1, Management of Change & Document Change Request Oil and Gas Industry Standards and Regulations 4
J Project management Document. IATF 16949 - Automotive Quality Systems Standard 4
S Master Document Register Document Control Systems, Procedures, Forms and Templates 3
M Preparing a document for Raw Material of Medical Device EU Medical Device Regulations 1
R Regulations on Controlled Document Size (Paper Size) Document Control Systems, Procedures, Forms and Templates 4
M Document Architecture ISO 13485:2016 - Medical Device Quality Management Systems 8
cgaro62 Using internal audits as part of document reviews Document Control Systems, Procedures, Forms and Templates 21
J Training on the importance of Document Control Document Control Systems, Procedures, Forms and Templates 3
Ed Panek External Standards List - Should this document include previously revised standards? ISO 13485:2016 - Medical Device Quality Management Systems 4
H Document retention period Canada Medical Device Regulations 2
S Document Notes ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 1
M ISO 13485 and document control for programs ISO 13485:2016 - Medical Device Quality Management Systems 6
Ed Panek MR Mandate Document EU Medical Device Regulations 1
C Document Index Document Control Systems, Procedures, Forms and Templates 5

Similar threads

Top Bottom