Monthly case format · brief · constraint · decision · production record · measurement · next-time note

What a Monthly Merch Case Study Looks Like in Armenia

A monthly case file earns its place only when it says something the previous month’s file did not. Most merchandise programmes in Armenia accumulate a folder of production summaries that all read the same way — a quantity, a method, a delivery date, a total in dram — and a reader who has seen one has effectively seen all of them. The difference between a summary and a case is a constraint that removed the easy options, a decision that was made under that constraint, and an honest record of what the decision cost once the run was over. This page sets out a format that fits on two pages, works for a forty-piece board gift as well as for a two-thousand-piece staff rollout, and produces something a procurement team, a marketing team and a finance team can each read a different section of and still agree on.

Talk to us about a monthly format All B2B notes

Why a monthly case file that repeats itself stops being useful

The failure mode is not that the file is wrong. It is that the file is interchangeable. A monthly case that opens with a restated brief, lists the quantity and the decoration method, confirms the delivery date and closes with a total is factually correct in the same way a packing slip is factually correct, and it produces no knowledge a reader did not already have. Once three consecutive months read that way, the file stops being read at all, and the programme loses the thing it was paying for: a record that tells the team what worked, what did not, and what would be done differently.

What turns a record into a case is a constraint that genuinely narrowed the option set, and a decision that was taken inside that narrowing. An order where the quantity was known, the artwork was approved, the supplier had the blank in stock and the date was open is not a case; it is a transaction. An order where the quantity was uncertain until three weeks before production, or where the brand lock-up could not be changed because it was already on signage, or where the budget was fixed but the currency moved, is a case — because there was a moment when several approaches were defensible and only one was chosen. The written record of that moment is the part worth keeping.

A useful monthly case contains six blocks in a fixed order, and the order is what makes a series comparable at all. Each block answers a question the previous one raises, and the sequence set out below is the one the rest of this page uses. Six blocks, two pages, no slide titles.

Brief: Stated before the outcome, in the words the requester used
Constraint: What was fixed, what could move, and by how much
Decision: Option chosen, option rejected, reason given
Production record: Quantity, method, spec version, shipped date
Measurement: What was tracked, how, and what it produced
Next-time note: One specific change, not a general intention

Four blocks that carry the weight

Of the six blocks, two are administrative and can be handled in a sentence: the production record is largely a restatement of the purchase order, and the next-time note is one line. The four below are the blocks that take real work, because each one requires someone to remember something that was decided in a conversation and write it down before the detail fades. Each is described with the failure it prevents and the question it answers.

The brief, stated before the outcome

The brief block is the request as it arrived, not the request as it was eventually satisfied. That distinction sounds pedantic and is the single biggest source of retrospective fiction in case files. Once a run has gone well, the temptation is to write a brief that was always achievable — to describe a brief that has been quietly improved by everything that went wrong. The honest brief keeps the awkward parts: the quantity range that was wide, the deadline that was described as flexible and was not, the internal approval chain that nobody had mapped, the artwork that arrived as a screenshot. Written at the start of the month rather than the end, the brief also captures the requester’s own priorities, which is often the only reliable record of what the programme was actually for. A brief that reads as clean and tidy in retrospect is a sign that it was written too late.

The constraint that removed the easy options

A constraint is the fact that made the obvious approach unavailable. Constraints in Armenian corporate merchandise work cluster into a small number of families: a fixed date that cannot move because an event, a conference session or a reporting cycle sits downstream of it; a budget ceiling set in a currency that is not the currency the production cost arrives in; a brand or compliance lock that prevents a substitution; a headcount range rather than a headcount; and a delivery address model — a single office, a distribution centre, or a courier-to-home model — that changes the packaging decision before the item decision is even made. Naming the constraint is what allows a reader to learn from the case, because without it the decision looks arbitrary, and an arbitrary decision is not worth copying or avoiding. A case that records a choice but not the reason for it is a case that will be repeated wrongly.

The decision, with the option that was rejected

The decision block should name two options, not one. One is the approach that was taken; the other is the approach that was considered and set aside, with the reason. The rejected option is the more valuable half, because it is the half that the next person in the role would otherwise propose again — the cheaper blank, the later date, the consolidated order across departments, the different decoration method — and it is the half that the file most often leaves out. Recording it also protects the decision from being relitigated in six months by someone who has not seen the reasoning, which is a common and entirely avoidable cost. The block does not need to be long: two options, one line each on why one won, is sufficient. What matters is that the rejected option is named specifically enough that a reader can recognise it when they next see it in a proposal.

What was produced and what it measured afterwards

The production record and the measurement block belong together because the second one is meaningless without the first. The production record fixes the denominator: what was ordered, at what specification, in which colour and method, shipped when, delivered to how many addresses. The measurement block then reports what happened after delivery — how many items were still in use at the follow-up point, how many went to a second recipient, what feedback came back unprompted, what the recipient asked for a second time. The discipline is to report only what was actually tracked and to say so plainly when something was not tracked. A measurement section that reports a retention figure nobody counted is worse than an empty one, because it will be quoted later as though it were evidence. Where the programme is too new to measure, the honest entry is a statement of what will be tracked and when the first reading will exist.

A worked illustration: a 400-unit onboarding kit

The illustration below is a composite built from the shape of requests that arrive regularly in Yerevan. It is not an account of a named client and it is not a claim about a specific delivered project; it is the format populated with the kind of detail a real monthly file contains, so that the structure can be judged on something other than an empty template. Any figure in it is illustrative and should not be read as a quotation or as a market rate.

The brief. A 240-person organisation with a Yerevan office, an operations floor, and staff who work on site at client locations, needed an onboarding kit for people joining in the second half of the year. The request arrived in June with a quantity range rather than a number, a start date in September, and an instruction that the kit should carry the company logo and nothing else. The requester described the kit as something new joiners would keep and use, rather than something handed over at a desk.

The constraint. Three constraints arrived together and they interacted. The headcount was a range of roughly 300 to 460 rather than a figure, which meant the production quantity could not be fixed until closer to the date than is comfortable. The logo was locked because it had already been applied to signage and recruitment material, so no alternative mark could be proposed. And the delivery address model was one office, not a distribution centre and not home delivery, which meant a single bulk delivery date had to work rather than a staggered release. The date itself was the fourth constraint, sitting downstream of an onboarding cohort schedule the requester did not control.

The decision. Two approaches were on the table. The first was to order for the top of the range in one run, which secured the best per-unit position and put the whole spend in one month, and which risked leaving a visible surplus on a shelf if the cohort came in at the bottom of the range. The second was to order in two releases, at a lower position on the volume curve and with a second setup on the second release, which kept the spend aligned with the actual cohort and kept the shelf clean. The second was chosen. The reason recorded in the file was not the price; it was that a surplus of branded goods sitting in an office for a year is a visible cost to the organisation in a way that a modest unit-cost difference is not. That is the kind of reasoning the block exists to preserve, and it is not something a reader could have reconstructed from the order alone.

What was produced. The first release covered the confirmed cohort and the second was sized after the roster firmed. Two decoration methods rather than one: a printed mark on a durable everyday item and a stitched mark on a second item, with each method chosen for the surface rather than for a single uniform treatment. Packaging was the decision that changed most late, because a single-office delivery meant the packaging had to survive a store room and a desk rather than a courier hand, which pushed the specification toward a box with an insert over a sleeve. That change was made after the first sample was reviewed rather than before, which is exactly the kind of thing the next-time note exists to correct.

What was measured. The programme was measured on two things it could actually count. The first was reconciliation: how many items went out against the roster, and how many were still unissued at the follow-up point. The second was an unprompted signal rather than a survey — whether new joiners came back for a second item, recorded through the normal onboarding channel. Both are weak measures and the file says so; neither supports a claim about brand reach. Their value is that they are reproducible next month without new instrumentation.

The next-time note is the block most formats drop

Ask a team which block of their monthly file they find most useful and the answer is usually the measurement section. Ask which block they write first and the answer is usually the production record. The next-time note sits between those two habits and is therefore the block that never gets written, even when the format on paper requires it. It is also the block that turns a series of monthly files into a body of knowledge rather than a running invoice.

A next-time note is not a lesson and it is not a resolution. It is narrower than both. It names one change that would have been made if the run were being done again with the same information available at the start, and it names the condition under which the change would apply. The difference matters: a lesson claims something general, a resolution claims something about the future, and a next-time note claims something specific about this run. “Communicate earlier” is a lesson. “Lock the quantity range before the supplier prices the second release” is a note. The first cannot be actioned; the second can.

The best next-time notes are conditional rather than absolute, because the circumstances of a given month are usually what produced the friction. A note that reads “move the packaging decision before the first sample” is useful only when the next run also has a single-office delivery model; on a staggered courier-to-home run the packaging decision genuinely belongs where it was. A note that reads “ask for the roster two weeks earlier” is useful when the roster is owned by someone outside the requester’s team and the answer is no; it is not useful when the same person is the requester. Writing the condition alongside the change costs one extra sentence and turns the note from a slogan into something the next planner can actually evaluate.

There is a compounding effect that only shows up after several months of consistent format. In month one, the notes are largely defensive — the note records what went wrong. By month four, the notes begin to describe where the specification itself is weak, because the same correction keeps appearing in different guises across unrelated runs. A programme that writes its notes properly usually arrives at the conclusion that its own standard specification needs a second entry point for a different audience, not that its suppliers need replacing. That conclusion is expensive to reach any other way, and it is why the format is worth the discipline in months where nothing much happened.

Questions buyers ask about monthly case formats

Should a monthly case name the client it describes?

It depends on what the file is for, and it is worth deciding that before the series starts. An internal programme record can name the internal requester and the department, because the value is in tracing a decision back to the person who has to live with it. A file that is shared outside the organisation has a different problem: the client’s approval for a public description takes time, and the parts most worth describing — the constraint, the rejected option, the shortfall — are often the parts nobody wants in public. A workable compromise is to keep the descriptive detail and remove the attribution, which is why a composite format like the one illustrated above is a reasonable pattern for anything circulating outside the company. Deciding this once, at the start, avoids renegotiating it every month.

What goes in the measurement section when the programme is too new to measure?

What was tracked, plus a statement of when the first real reading will exist. A new programme can usually count three things without any new process: how many units were issued against how many units produced, whether the quantity range given in the brief matched what arrived, and how many unprompted requests or returns came back through ordinary channels. Those three are enough for an honest first entry. The thing to avoid is filling the gap with a figure that sounds like a result. A retention rate nobody counted, a reach estimate built from the recipient count, or a satisfaction number inferred from the absence of complaints will all be quoted later as though they had been measured, and once that has happened the file cannot be corrected without losing its authority entirely.

How long before a monthly case series is worth the writing time?

The series pays for itself once a correction has recurred twice, because the second occurrence is the point where the pattern becomes visible rather than anecdotal. Before that, the writing is mostly overhead and a shorter log is the right format. The practical version is to run the first two or three cycles as a plain production log, start the full format at the point where a decision actually felt contested, and then keep it going for at least two more cycles after that — the next-time note only becomes readable once the team can see whether the change it named was actually made. Teams that abandon the format usually do so at the month where nothing went wrong, which is precisely the month where the note is most valuable and least interesting.

Is Corp-Merch the official supplier or affiliate of any case-study programme, methodology, or industry reference on this page?

No. Corp-Merch is an independent B2B merchandise supplier operating in Armenia. The format described on this page — brief, constraint, decision, production record, measurement, next-time note — is a reasoned working structure, not a recognised standard, and the worked illustration is a composite rather than an account of a delivered project. Nothing here implies partnership, sponsorship, endorsement or an official-supplier relationship with any organisation, and no result described on this page is a guarantee of any outcome on a future programme.

This page is written for marketing, brand and procurement leads running a recurring merchandise programme in Armenia who want a written record rather than a folder of production summaries. Corp-Merch is an independent B2B merchandise supplier. The six-block format set out here is a reasoned synthesis of how programme records are usefully structured, and the worked illustration is a composite rather than a client account; neither is a benchmark, an audit standard or a certification, and the format should be adjusted to fit the actual measurement discipline available on a given programme. Any reference to a named method, structure or industry practice is informational only and implies no partnership, endorsement or official-supplier relationship with the body that publishes it.