Предложение генеральному директору

<!-- Faithful paraphrase of Barbara Minto, The Minto Pyramid Principle
(2010), Chapter 3, Exhibit 5 and the surrounding top-down analysis.
The wording is original to this evaluation fixture. -->

Fixture 01: Big Chief proposal

Mode: write
Language: en

Context

The company supplies beverages. Drivers send delivery tickets to Finance; each
ticket identifies the customer, outlet, delivery, amount, and date. The tickets
feed the national-accounts settlement process.

Big Chief, a major multi-outlet customer, wants to replace individual ticket
settlement with a monthly computer file and one payment. Finance reviewed how
the proposed process would work and sent management the memo below.

Before

To: Robert Salton
                From: John Jackson
                Subject: Big Chief request
                
                We reviewed Big Chief account 8306's request to submit delivery-ticket data
                electronically and settle it through one prepaid monthly payment. Our findings
                follow.
                
                1. Any external account file must contain the parent number, outlet number,
                   ticket number, ticket amount, and delivery date. If Big Chief cannot provide
                   the first two identifiers, we can supply them from the customer master file
                   for inclusion in later submissions.
                
                2. Big Chief will build an extraction program for its accounts-payable file.
                   The resulting file will use the format accepted by our national-accounts
                   cash-receipt system. Big Chief will send the file to Data Processing and
                   send its cheque, with a detailed listing, to the lockbox. We will balance
                   the file under the prescribed procedure. The cheque total and file detail
                   must net to zero.
                
                3. Once balanced, the monthly file will run through the national-accounts
                   system, match ticket numbers against statement history, and produce the
                   relevant billing records.

Task

Rewrite this as a short management memo using the Minto Pyramid Principle.
Do not invent benefits, savings, or operational facts that are absent from the
source.

Gold 01: Big Chief proposal

Source structure: Minto (2010), Chapter 3, Exhibits 4-6.

Expected structure

The book illustrates three possible benefits: obtaining the required
information, increasing cash flow, and reducing clerical work. Only the first
is directly supported by this fixture. Literal reproduction of all three is
therefore not required and unsupported benefits count as inventions.

Strong outputs:

• answer the management question before explaining the file mechanics;
• use two to four same-kind reasons grounded in the supplied facts;
• place field lists, file format, routing, balancing, and matching below those
  reasons as evidence or implementation detail;
• retain the literal reader question in the delivered memo.

Main defect in the source

The source explains how the proposed system would operate but never answers
whether management should accept it. A technically tidy list is still the wrong
key line if the reader is deciding whether to act.

Scoring notes

• 2 for key-line composition: every first-level point is a grounded benefit,
  loss avoided, or reason for acceptance.
• 1: benefits and mechanics are mixed.
• 0: the first level is entirely fields, file handling, or balancing steps.

Do not reward unsupported claims about savings, speed, or cash flow.