The project moves on; access stays behind
Imagine a component manufacturer sharing drawings with an outside partner during sampling. Production begins and the contact changes, but the shared location and access list remain untouched. Former participants see information they no longer need while the successor cannot find the approved version. This is a hypothetical example, not a customer case.
Quotation, sampling, trial production and ongoing production can require different information and participants. Reviewing access only when employees join or leave misses changes within projects. Connect each phase with its work, information owner and necessary participants before choosing settings.
Define the project information boundary
For one active project, locate specifications, drawings, inspection information, confirmations and delivery documents. Distinguish working copies from approved material and identify who can release a new version. Information need not share one system, but a common project identifier should help people connect it.
Similar filenames do not prove identical versions, and creation dates do not establish approval. Record the revision, applicable scope, approver and reason for significant changes. The explanation should be understandable to sales, engineering and quality contacts, not just the file's creator.
Review access at project milestones
At the start, decide who needs to read, change or share information. Revisit that decision at phase changes, handovers and the end of outside involvement. Access should reflect roles rather than be identical for everyone. Temporary exceptions need an owner and a review point.
For group-based access, identify who maintains membership and how changes are communicated. For individual sharing, ensure it can be reviewed too. Someone authorized to decide should approve the scope of sensitive external disclosure; the sender should not have to guess.
Connect revisions to affected work
An update notice should explain the changed material, applicable phase or batch, items needing confirmation and who authorizes continuation. People handling unfinished work need the correct reference; completed work needs an explicit decision about any follow-up.
Preserve the reason for differences and exceptions so a successor can understand them. This need not mean a large form for every edit. Start with changes affecting other departments or external deliveries, agree on a minimal record and check whether it can actually be found.
Closure is more than moving a folder
Confirm the owner of later service questions, necessary retention and external access that can end. Hand over the archive location and retrieval method. A former employee's mailbox should not be the sole historical source, and moving to an archive should not trigger indiscriminate deletion.
Ask someone outside the original discussions to find the approved version, explain the main revision and identify current access. Fill gaps in the authoritative record when this requires the original contact. This tests information handover, not manufacturing quality or regulatory certification.
Run one project through the process
Pilot an information-location list, phase-based access review and change record on a bounded project. Have its owner and IT identify missing context and unnecessary access before expanding. Avoid a company-wide spreadsheet that nobody can maintain.
ACMI can assess related IT governance and digital collaboration needs. Bring one concrete problem involving role changes, external sharing or approval. General IT improvements are not presented here as a replacement for manufacturing systems, engineering document controls or quality processes.
