Document hedge relationships and effectiveness

Suppose the copper forward offsets Cedar Trail's forecast purchases almost perfectly. That observation is useful risk evidence. It is not, by itself, hedge accounting.

Build a designation sheet with the hedging instrument, hedged item or forecast transaction, designated risk, hedge type, risk-management objective, quantities, dates, forecast location, assessment method, excluded components, and required documentation date. Use exact contract and transaction identifiers. “Copper exposure” is too broad to trace.

Next assemble effectiveness evidence. The file should distinguish the prospective assessment at inception, ongoing assessment, and any quantitative work. It should preserve critical terms, market data, probability support, method consistency, counterparty evidence, and signals that could require dedesignation or discontinuation. A period-end offset calculated with hindsight cannot substitute for the required process.

For the course calculation, the designation and effectiveness conclusion are supplied. Put that stipulation above the schedule. Then ask what would change the conclusion: volume shortfall, delayed purchase, different location or grade, amended notional, contract novation, counterparty concern, or a changed assessment method.

The review output is a relationship card and an exception log. If any required designation field is missing, keep the derivative's fair-value accounting visible and hold the hedge overlay open. That produces a defensible result without inventing qualification.