Copper data:
baseline and recurring updates

1. Work the product supports

Build an annual project baseline with operator, country, period, production basis and original evidence. Maintain guidance history with prior and revised values. Track disruptions by affected activity, effective date, disclosure date and follow-up evidence.

Different periods, products and ownership bases are kept distinct. The sample does not produce a supply forecast or trading recommendation.

2. Product and delivery

• One-time baseline: a dated snapshot in Excel and CSV, field and coverage notes, and a source index. Complete means the included set is delivered in full; it does not mean global coverage.
• Single-commodity updates: a monthly change log, current complete workbook and bilingual newsletter, against a disclosed monitoring list and source coverage.
• All-commodity updates: commodities with a proven delivery process, plus a cross-commodity summary. Coverage and gaps remain explicit for each commodity. A bundle discount versus separate purchases is planned; its size is not yet set.
• Team access: named users and internal collaboration rights to be agreed before purchase.

The proposed baseline is available separately, with updates optional. Existing baseline rights should not be charged twice when starting a subscription. Cancellation stops future updates; downloaded files remain usable under their applicable license. Historical access, upgrade credits, seats and pricing remain to be finalized.

3. Proposed monthly cadence

The proposed cutoff is 23:59 Singapore time on the last day of each calendar month, with delivery targeted by the fifth business day of the next month. This is a service target to validate in two delivery rehearsals before making a commitment. Billing periods and publication periods will be explained separately.

Weekly summaries may follow later. The first version does not promise real-time alerts. Late disclosures retain their original publication date and appear in a later issue, with the date first included and the date checked.

Corrections preserve the prior version and identify the changed records, revision and reason.

4. Data and change records

Stable project IDs connect the baseline, change log and newsletter. Values retain units, periods, product and ownership bases, status, source and location. Missing values stay blank; undisclosed publication dates are not invented.

Changes preserve old and new states. Effective dates remain separate from announcement dates. A point forecast has equal lower and upper bounds and a point-value label; withdrawal has blank active numeric bounds.

Transport interruption, affected mining area and confirmed production loss are separate fields. Expansion contributions remain under their parent project. Original facts, MGW organization and research-use guidance stay distinguishable.

5. Newsletter structure

Each issue identifies the records to update, what changed, when it was disclosed, the applicable reporting boundary, suggested table actions, remaining questions and original sources. Chinese and English editions share the same IDs, dates, values and limitations.

6. Try the sample

Complete the same research task with and without the workbook, check that results agree and record the elapsed time. No measured time-saving claim is made. Two monthly delivery rehearsals will test editorial effort, coverage, late sources, corrections and support needs.