Proving which control plan revision was active on a given date

Ask most shops for their control plan and you get an answer in seconds. The current revision is on the wall or a click away in the system. The question that actually stops people cold comes later, usually from a thorough auditor working a complaint. Which control plan revision was active on a specific date months ago, the day the parts in question were actually made? That is a different question, and the current plan does not answer it.

Why the current control plan is not enough

A control plan does not sit still. Over the life of a part you add a characteristic after a customer return, tighten a tolerance, swap an inspection method for a better gauge. Every one of those changes lands as a new released control plan revision. If the only thing anyone can see is the latest revision, there is no honest way to prove which one was in force on the day the work ran. Worse, holding today's plan up against parts made under an earlier revision reads worse than saying nothing, because the inspection on record no longer matches the plan on record, and now it looks like the shop was checking the wrong things. What the auditor is really testing is narrow and fair. Was the right revision active on a date, released by the right authority, at the moment the work was done.

How the history answers the question

The whole thing gets easy the moment two facts are true at once. First, each control plan revision is released as a dated event, so its effective date is a matter of record rather than folklore. Second, every capture record carries the exact revision it was taken against, so a characteristic result is never floating loose from the plan that governed it. Read those two together and the date question resolves itself. You find the revision in force on the day from the release events and their effective ranges, then you pull the capture records stamped with that same revision. No reconstruction, no arguing from the current plan backward. The revision history and the capture records point at each other, and the date sits in the middle where the auditor put it.

Where this lives day to day

VoraControl holds control plans as released revisions. Each revision has its release event and the characteristics it requires, and inspection capture is tied to the specific revision it was taken against, so the link between plan and result is made at the moment of work rather than pieced together afterward. When an auditor asks which revision was active on a date, VoraAudit scopes the read to that period through the Audit Reporter and shows the revision, its release record, and the capture results from that time to review on screen or print. Every line traces back to the release event or the capture result it came from.

The date question only ambushes a shop that treats its control plan as a single living document. Treat each revision as a dated, released fact and tie the inspection work to it as it happens, and the answer is already sitting there when someone asks for it. You did the work once, correctly. Proving which revision governed it is just reading back what you already recorded.