Work notes & team training
These are notes from my daily work in packaging sales, project follow-up and team training. Each starts with a real question and leaves practical actions for a similar situation. Project identity and commercial details have been removed.
From your current question
Section titled “From your current question”Samples & validation
Section titled “Samples & validation”| Note | What you can use |
|---|---|
| Which white is the agreed white? | Turn a visual disagreement into an agreed acceptance range. |
| An improved sample is not yet a golden sample | Separate sample improvement from approval for production acceptance. |
| What does this prototype actually prove? | Define the question before choosing the prototype and evaluation scope. |
| A drawing change has a document trail | Carry revision changes through drawings, samples, artwork and production inputs. |
| Define the test before ordering trial tooling | Determine sample quantities with the test purpose, conditions and recording needs. |
Quoting & development
Section titled “Quoting & development”| Note | What you can use |
|---|---|
| Why total volume does not settle every MOQ | Agree how quantities are grouped before discussing MOQ and price. |
| Map the steps behind a decoration lead time | Turn a process explanation into an artwork-to-production plan. |
| When does an approved saving actually take effect? | Separate technical agreement, stock transition and price implementation. |
| When a customer gives a target price, clarify the conditions first | Separate validation, production readiness and cost reduction. |
| After a trial, how should we calculate unit cost? | Record input, recovery, losses and accepted output together. |
| A new pack: adapt an existing platform or develop from scratch? | Align the use case, structure, development scope and tooling responsibilities. |
Quality & delivery
Section titled “Quality & delivery”| Note | What you can use |
|---|---|
| A pack-out change can change the freight quote | Keep carton, weight and pallet data aligned when pack-out changes. |
| Restarting production takes preparation | Plan returning demand together with materials, people and line readiness. |
| Ready goods still need a shipping plan | Track production completion, release, allocation, booking and shipment separately. |
| Why raising a quality concern does not close it | A warning needs batch scope, disposition, ownership and closure evidence. |
Materials & data
Section titled “Materials & data”| Note | What you can use |
|---|---|
| Define the basis before printing a sustainability percentage | Define the object, measurement basis and evidence before discussing a claim. |
Customer communication
Section titled “Customer communication”| Note | What you can use |
|---|---|
| What to ask after an interested enquiry | Turn customer interest into inputs that can be assessed. |
| A follow-up email needs a decision point | State the missing input, affected milestone and next check point. |
| Turn a launch ambition into usable planning inputs | Turn a growth plan into assessable inputs and stages. |
Commercial follow-up
Section titled “Commercial follow-up”| Note | What you can use |
|---|---|
| Sending an invoice may not start the payment clock | Separate sending, receipt, entry, acceptance, due date and payment. |
Work observations
Section titled “Work observations”| Note | What you can use |
|---|---|
| Describe a concept at the right development stage | State whether an exhibit is a concept, prototype, validated option or production product. |
| What to verify in an AI-generated meeting note | Verify commitments, numbers, revisions and ownership before using AI minutes. |
Sales reporting
Section titled “Sales reporting”| Note | What you can use |
|---|---|
| Emails sent, meetings held—what changed in the project? | Turn an activity list into a result, supporting facts and a next step. |
Team training
Section titled “Team training”| Note | What you can use |
|---|---|
| Turn “please support ASAP” into an actionable request | Name the owner, deliverable, deadline and consequence. |
| Ask a new colleague to explain the process, not just say they understand | Use one page to explain inputs, decisions and outputs. |
| A long meeting—but did the customer’s problem move forward? | Bring internal discussion back to the customer’s issue and a concrete action. |
Three exercises for the team
Section titled “Three exercises for the team”- Report a result: explain the changed state, supporting facts and next action in 90 seconds.
- Explain a process: map inputs, decisions and outputs on one page.
- Move a customer issue forward: leave a decision, an open gap, an owner and a deliverable.
About the records
Section titled “About the records”These notes combine actual work records and team training. Suggestions and sample wording are offered for the next similar situation, without claiming that a particular project has been resolved. Methods depend on the actual product, responsibilities and approval scope. Every note has a complete Chinese version.