Nothing Written Down Before the Next Customer Review

What the owner is deciding this week

The owner is not choosing a new supplier this week and is not rewriting a technology plan. The owner is choosing whether purchasing and engineering may keep using unapproved AI tools. Those tools include personal AI accounts that already sit on company laptops. The work at stake is specifications, quote language, and vendor pricing. The clock is the next customer review, which already has a date. Silence is already a choice, and the visitor will treat that silence as a fact.

Purchasing needs speed when a ship window moves or a line waits on a part. Engineering needs speed when a drawing change arrives late in the week. Personal AI accounts feel fast because no request has to wait in a queue. Unapproved AI tools sit beside the same files the quality system claims to control. The customer will not grade that convenience. The customer will ask where the record lives and who could see it.

The decision has three honest answers and no fourth. Staff may continue under a written rule that names what may leave a laptop. Staff may stop until that rule exists and until finished work sits in a controlled folder. Staff may use nothing that names a customer, a part, a process, or a price. Each answer can be signed this week. Delay is still an answer, and it will look like permission when the review begins.

This call belongs to the owner because purchasing cannot bind the plant and engineering cannot bind the plant. A supervisor can tell a person to stop typing. Only the owner can say what the company will defend in the conference room. Further reading for plants in this harbor market sits on the North Charleston service area page. Use that page as context, not as a substitute for the decision on these tools.

What nothing written down actually means

Nothing written down does not mean staff are hiding work in a dramatic way. It means the quality manual never named unapproved AI tools. It means the information security notes never named personal AI accounts. It means no one signed a list of allowed uses. It means no one signed a list of forbidden inputs. The habit grew because the tools were easy and the work was late.

A verbal warning in a meeting is not a record. A reminder in email is not a controlled document. A laptop folder is not the system of record the customer expects to see. If the plant later needs the draft that became a specification, the personal account may hold it. If the person leaves, that account leaves with them. The plant then owns a finished part and does not own the words that defined it.

Customers who buy from plants near this port already live inside document control. They expect a specification to have an owner, a revision, and a place it must live. They expect a vendor comparison to show sources that still exist. They expect confidentiality clauses to mean data did not travel to a login the company does not hold. When nothing is written about these tools, those expectations have no answer that will survive a follow-up question.

The gap is not moral and it is not about intelligence. People used what was on the machine to finish work the plant asked them to finish. The gap is legal, commercial, and procedural. A customer review is a poor place to discover that the procedure never existed. Write the gap down in plain language before anyone tries to defend it.

What purchasing already puts into personal accounts

Purchasing staff write requests for quotation when a buyer needs a price that can travel with a ship schedule. They compare pack sizes, lead times, and terms that mention the Charleston port. They rewrite vendor emails into a clean bid table. They ask a tool to turn a messy quote into a short comparison. They paste part numbers, target dates, and sometimes the customer name that sits on the order. That material is not public color commentary. It is the commercial spine of the plant.

A personal AI account does not know that a quote is confidential. It does not know that a vendor’s price is a competitive fact. It does not know that a customer forbids disclosure of a program name. The account will still accept the text because the person has a login. The plant has no contract with that login. The plant has no retention hold on that history. The buyer may believe the draft is harmless because it never left their screen. The copy is no longer only on that screen.

Vendor pricing is a special problem because it is both sensitive and reusable. A table that ranks three suppliers is exactly the kind of compact text these tools handle well. It is also exactly the kind of file a customer, a rival, or a later dispute might want. If the only copy lives in a personal account, the plant cannot produce it on request. If extra copies live in that account, the plant cannot destroy them on request. Either failure can surface in a review that was supposed to be about delivery and quality.

Purchasing also handles terms that mention drayage, dwell, and the terminal. Those details look operational and dull. They still identify volume, timing, and sometimes the commodity. Combined with a part number they become a map of what moves through the port. Unapproved AI tools should not be the place that map is polished. The owner can say that without accusing anyone of theft.

What engineering already puts into those tools

Engineering staff write specifications under time pressure that purchasing never sees. They turn a marked print into a paragraph a supplier can bid. They sort tolerance notes into a list a machinist can use. They restate a customer requirement in language the plant can inspect. They summarize a failure from the floor so a vendor can propose a change. All of that text can contain process knowledge the plant treats as its own.

A specification is not only a technical letter. It is a controlled promise about material, method, and acceptance. If the first draft was born inside a personal AI account, the controlled copy may be a later cleanup. The cleanup may drop a note that mattered. The cleanup may add a phrase no engineer would sign. Without a trail, no one can say which words came from the person and which words came from the tool. The customer will still treat the signed file as the plant’s voice.

Engineering also handles special characteristics, process notes, and packaging rules for export. Those lines often include the customer’s language. That language may be restricted by a purchase order. Putting it into an unapproved AI tool is a disclosure even when no rival is in the room. The person did not mean to publish a drawing. They meant to finish a paragraph before a meeting. Intent will not satisfy a confidentiality clause.

The owner should assume this work already happened on some laptops. That assumption is not a charge. It is a planning fact. If the review is close, hunting every prompt is a waste of the remaining days. Gathering finished files into the real document system is not a waste. Naming what may never be entered again is not a waste either.

What the customer will ask for in the room

A customer review near this port is rarely a tour of machines alone. The visitor will ask how a specification is approved. The visitor will ask where vendor quotes live. The visitor will ask who can change a requirement after a bid. The visitor may ask whether production data or drawings leave the company network. Those questions are ordinary now. They are not a surprise reserved for a scandal.

If the plant says the specification lives in the controlled folder, the visitor may ask to see the revision history. If the history starts at a clean file with no draft trail, that can still pass. If someone then says the first text came from a personal AI account, the visitor has a new subject. The new subject is not the font. The new subject is whether customer information left a system the plant does not control. That subject can consume the rest of the meeting.

Some reviews include an information security list. The list will ask about unapproved tools in simple language. An honest no, with a written rule, is cleaner than a long story. An honest we did not write a rule yet is still better than a claim that no one uses such tools. The visitor can often tell when a shop has a habit the manual ignores. Plants that ship through Charleston already know how fast a finding travels to a buyer.

The owner should rehearse one sentence that is true. Staff used personal AI accounts because no rule existed, and that use stops for named classes of data until a rule exists. That sentence is calm. It is specific. It is something a quality manager can repeat. It is better than a claim that the laptops were clean when no one checked.

What leaves a laptop and does not come back

A personal AI account is not a drawer in the plant. The login belongs to a person. The history belongs to that login under terms the company never signed. Copies can remain after a person deletes a window. The plant cannot certify destruction it cannot see. The plant cannot certify retention it does not control. Those limits are the whole problem, not a side issue.

Unapproved AI tools on a laptop can also sit beside drawings, quote books, and customer packets. The person may not think they submitted a packet. They submitted a paragraph that still identifies the packet. A part number plus a tolerance plus a customer nickname is often enough. Port timing plus a supplier name can be enough. The tool does not need a full drawing to hold a useful fragment.

Once a fragment is outside, the plant’s remedies shrink. A letter to a staff member is not a letter to the tool. A collection from a laptop is not a collection from a personal account in a private browser. If the review asks whether data left the company, the true answer may be yes for some files. The owner needs that answer before the visitor asks. Guessing in the room is how a small habit becomes a finding.

This is why the decision cannot wait for a perfect inventory. The inventory will take longer than the calendar. The decision can still freeze new use of named data. The decision can still require finished work to live in the controlled system. The decision can still require staff to copy what they still have into that system. Those acts are available this week.

Why a draft in a personal account has no owner

Document control assumes a file has a person, a date, and a place. A draft in a personal AI account has a person only while that person remembers it. It has a date the plant cannot audit. It has a place the plant cannot open without that login. If two engineers polish the same requirement in two accounts, the plant has two unofficial owners. The signed specification may match neither draft.

Ownership matters when a part fails or a vendor disputes a line. Someone will ask what the plant required on the day the order was placed. The controlled file should answer. If staff remember a different paragraph from a tool session, the plant now has a shadow requirement. Shadow requirements create rework, credit claims, and angry calls. They also create a story the customer will not like, because the story says the plant did not know its own words.

Engineering changes make this worse. A revision should start from the last approved file. If someone starts from a remembered tool output, the revision may restore a retired note. It may drop a safety line. It may alter a finish that purchasing already quoted. None of that requires bad faith. It only requires two sources of truth. Personal AI accounts are a third source the quality system never listed.

The fix is dull and it works. Finished specifications live in one system. Drafts that still matter get copied there before anyone is asked to forget them. New drafts that include customer or process detail do not start in a personal account. The owner can write those three lines without a lecture about technology.

How vendor pricing becomes a copy you cannot recall

A bid comparison looks harmless because it is a table of numbers and names. It is also a compact record of what the plant is willing to pay and whom the plant might drop. Personal AI accounts are good at compact records. That is why buyers use them. That is also why the plant should not let the only copy live there.

If a vendor later says the plant leaked a price, the owner will want a file with a date. If a customer later asks how a source was chosen, the owner will want the same file. If a buyer leaves for another company, the owner will want the file to stay. A personal account fails all three wants. The account can also keep the table after the plant thinks the matter is closed.

Purchasing can still move fast without that risk. The comparison can be built in the plant’s own quote workbook. The narrative can be written in the plant’s own document system. An unapproved AI tool can stay out of any file that names a supplier or a figure. That is a clear line. Staff can follow a clear line. They cannot follow a mood that changes after each rush order.

The owner should not turn this into a hunt for old tables. Ask for copies of comparisons that still govern open awards. Place those copies in the purchasing record. Then say that new comparisons do not start in personal AI accounts. The review can be told that sequence. It is a sequence a visitor can understand.

What a freeze looks like without stopping the plant

A freeze is not a shutdown of purchasing or engineering. A freeze is a stop on a method, not a stop on shipping. Staff may still write specifications. Staff may still price vendors. They may not use unapproved AI tools or personal AI accounts for that writing when the text names sensitive facts. They use the systems the quality manual already named. That is the entire freeze.

Sensitive facts should be listed in short lines. Customer names and program names are sensitive. Part numbers tied to a customer are sensitive. Process steps unique to the plant are sensitive. Vendor prices and rankings are sensitive. Drawings, markups, and inspection notes are sensitive. Port volumes and timing tied to a customer are sensitive. If the text contains one of those, it does not go into a personal AI account.

Work that is truly public can wait. A rewrite of a public standard in the staff member’s own words is not the emergency. The emergency is the specification that will be shown next month. The emergency is the quote package that still sits in a private history. Direct time at those files. Do not spend the week arguing about a public paragraph.

Tell supervisors the freeze in one meeting and one follow-up note. Name the start as now, not after a later workshop. Name the owner as the person who will answer the customer. Name the quality manager as the person who will check that finished files landed in the right folder. Then leave people to do the plant’s real work.

How to speak with staff before anyone deletes files

Assume good intent because that assumption is likely true. People used unapproved AI tools to finish work the plant wanted finished. A hunt will teach them to erase history. Erased history helps no one when the customer asks what happened. The first conversation should ask for copies, not for confessions.

Speak with purchasing and engineering separately so each group can be specific. Ask which jobs from the open book used a personal AI account. Ask whether the finished file already lives in the controlled system. Ask whether any customer packet, drawing, or price table might still sit only in that account. Write the answers down. Thank people who tell you the truth. Do not punish honesty for a rule that did not exist.

Do not ask anyone to demonstrate how a public model receives text. That demonstration teaches nothing the owner needs. The owner needs the output files and a stop on new sensitive inputs. Curiosity about the tool is a delay. Collection of the work is the task. If someone is afraid, say the freeze is about the review date, not about their job.

If a person has already left, do not pretend the plant can open their personal account. Collect what remains on the company laptop and in the shared folders. Note the gap in a private file the owner holds. If that gap touches an open customer job, fix the specification from the controlled copy and from the engineer of record. Do not rebuild a missing tool history.

What the owner should do with the remaining calendar

Count the remaining working days against the open customer jobs, not against a wish for a perfect program. List the jobs the visitor is most likely to sample. Pull the specifications and the vendor files for those jobs first. Confirm each file has an owner inside the plant. Confirm each file is in the place the quality manual already named. Then write the freeze page and sign it.

Meet purchasing and engineering the same day the page is signed. Read the sensitive facts out loud. Tell people to copy what they still have. Tell people not to open personal AI accounts for those facts again. Give them a person to ask if a job is unclear. Then let them return to the floor and the dock. A long workshop is not required. A clear hour is required.

Keep the customer review about the plant’s product if the files are in order. If a gap remains, name the gap in private before the visitor names it. Offer the controlled file and the new rule. Do not offer a story about how a public tool works. The visitor does not need that story. The visitor needs to know the plant can still specify a part and still price a vendor without a hidden copy.

If more reading on method would help after the date passes, the FAQ page is further reading on technology management questions. It will not make this week’s decision. The decision is already small enough to finish. Allow the practice with a written limit, stop it until the limit exists, or forbid sensitive use outright. Pick one. Put it on paper. Make sure the laptops match the paper when the customer sits down.

The plant near the Charleston port can keep its purchasing judgment and its engineering judgment. It cannot keep a private habit that leaves no file. Unapproved AI tools and personal AI accounts are that habit when nothing is written down. The next customer review will not write the rule for the owner. Third Shift Group LLC leaves this note for owners who still have time to write it themselves and to answer honestly if asked how they chose.

Further reading: Dashboard Maintenance — Monthly Check on the Numbers | Third Shift.