Feature–mechanism–benefit writing, past performance, and orals
Terms for scoreable proposal content: a feature–mechanism–benefit chain, attributed , personnel commitments, and as another evidence channel.
1 / 2
Feature–mechanism–benefit chain
Traceable proposal writing connects feature → mechanism → evaluated benefit → support. Support may include accurately attributed past performance, process artifacts, metrics, and personnel commitments that the permits. Relative strengths that support the evaluation must be grounded in the proposal record, not in adjectives. Use evaluator-style review to strike claims that cannot survive the chain — before page count forces worse cuts.
Watch for
Don't confuse repetition with proof. Borrowed experience presented as the offeror's own is not support. Unsupported commitments are not strengths waiting to be believed.
2 / 2
Past performance attribution, personnel, and orals
Submit the strongest relevant permitted past-performance examples and clearly connect each entity's prior role to its proposed share of the work. Do not claim key-personnel commitment without a reasonable basis — obtain and accurately document , or propose someone you reasonably expect to furnish. When oral presentations are authorized, rehearse proposed presenters against stated factors, keep oral and written claims consistent, obey content limits, and preserve the agency's Q&A record. Align technical narrative, past-performance volume, resumes, and orals as one evidence system. Every major claim should name its mechanism and support location; past-performance entities should match proposed workshare; key-personnel commitments should exist as required documents, not hopes.
Watch for
Don't confuse orals with an informal sales pitch that silently revises price or staffing. Presenting a teammate's contracts as the 's own to avoid a neutral rating is not attribution. FAR 15.102 permits evaluated orals; it does not license new price data the bars.