| Course | MMPA 6451 Public Policy Analysis |
|---|---|
| Week | Week 5 |
| Paper type | Assessment paper |
| Length | About 1,040 words, 6 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Master of Public Administration (MPA) |
| Updated | October 2026 |
Free sample paper for MMPA 6451 Week 5
Is the Fare System Ready? A Component-by-Component Readiness Grid for Fare Capping and a Reduced-Fare Program at the Corliss Area Transit Authority
Student Name
Walden University
MMPA 6451: Public Policy Analysis
Instructor Name
Month Day, Year
Is the Fare System Ready? A Component-by-Component Readiness Grid for Fare Capping and a Reduced-Fare Program at the Corliss Area Transit Authority
Purpose
The Week 4 comparison favored fare capping on automaticity and directness, with a reduced-fare program as the main alternative. A tool that looks right on paper may still fail if the agency cannot deliver it. Moore (1995) treats operational capacity as one of three tests every public proposal must pass, alongside public value and authorization. This assessment tests capacity directly, by asking whether each component of the Corliss Area Transit Authority's fare system is ready to support each instrument. The authority and its systems are composite.
Readiness Grid
Table 1
Readiness of Fare System Components for Two Instruments
| Component | Fare capping | Reduced-fare program | |
|---|---|---|
| Account-based fare tracking | Ready; cards already record every tap and fare by account | Ready; reduced-fare cards can be a card type in the same system | |
| Cash rider path | Not ready; cash paid on board cannot be linked to any account | Conditional; enrolled riders could receive a card, but cash riders who do not enroll are not reached | |
| Retail loading network | Conditional; 42 retail locations load cards, but only 9 are on the east side | Conditional; same network, same gap | |
| Eligibility verification | Not needed | Not ready; no partner or system to confirm benefit enrollment | |
| Customer service capacity | Conditional; staff can answer cap questions with a script and a progress lookup tool | Not ready; applications, document checks and renewals would exceed current staffing | |
| Vendor contract | Conditional; the fare vendor offers capping as a configurable feature, requiring a change order | Ready; reduced-fare card types are already configurable | |
Ready means usable now; conditional means usable after a defined fix; not ready means a new capability is required.
Read across the rows, capping has one not-ready cell, the cash path, and three conditional cells. The reduced-fare program has two not-ready cells, verification and customer service, and its gaps are larger.
Commentary
Fare capping: the cash rider gap
Capping works by adding up what an account has paid. A rider who pays cash on board has no account, so no amount of cash riding ever reaches a cap. According to the Week 3 statement, roughly one boarding in five is paid in cash, mostly on east-side routes. Some cash riders may be unbanked or prefer cash for budgeting; nationally, about 4.5 percent of households had no bank account in 2021 (Federal Deposit Insurance Corporation [FDIC], 2022). A cap that reaches only card users could widen the gap between card and cash riders even as it closes the gap between pass and single-fare riders. The fix is to make cards easy to get and load with cash: free cards for the first year, cash loading at more east-side retail locations and loading machines at the two east-side transit centers.
Fare capping: retail and customer service
Only 9 of 42 retail loading locations are on the east side. Before capping launches, the authority should add at least six, targeting the neighborhoods identified in Week 3. Customer service can handle capping with a short script and a lookup tool showing each account's progress toward the cap; the vendor's account portal already displays fare history, so the tool is a configuration rather than a new system.
Reduced fares: the verification gap
A reduced-fare program requires the authority to confirm that each applicant is enrolled in a qualifying benefit program. The authority has no way to do this today. It would need either a data-sharing agreement with the state human services agency or a process for reviewing benefit letters by hand. A data-sharing agreement would take months to negotiate and would raise privacy questions; manual review would require staff the authority does not have.
Reduced fares: customer service
Applications, document checks and annual renewals would add work the current staff cannot absorb. Salamon (2002) noted that tools low in automaticity carry administrative costs that are easy to underestimate at the design stage, and this is an example: the discount is cheap to announce and expensive to run.
The Vendor Change Order
Capping requires a change order to the authority's contract with its fare system vendor. The change order would be a configuration change to enable account-based capping rules for daily and thirty-day caps, plus testing in a staging environment, updates to the account portal display and staff training. It would not require new hardware. The authority should request a fixed-price change order with a testing period long enough to cover a full month of simulated riding, since thirty-day caps can only be fully tested over thirty days.
Sequencing the Fixes
The conditional cells for capping can be resolved in about six months if work begins in parallel. In the first two months, the authority would sign the change order and begin recruiting retail locations on the east side. In months two through four, the vendor would configure and test the caps while the authority installs loading machines at the two east-side transit centers and begins free card distribution through libraries and clinics. In months four through six, customer service staff would be trained and the progress lookup tool released, followed by public communication. Launching before the cash path is improved would deliver the benefit mainly to riders who already use cards.
What the Grid Does Not Show
A readiness grid describes systems, not behavior. Three risks lie outside it. Riders may not understand capping at first and may keep buying passes, so communication matters as much as configuration. Some riders may share cards to reach the cap faster, a small revenue risk the authority can monitor through account data. And operators, who handle most rider questions in practice, may resist another fare change if they are not briefed, which the implementation plan in Week 8 addresses.
Conclusion
Fare capping is closer to ready than a reduced-fare program. Its one not-ready gap, cash riders, can be narrowed with card distribution and cash loading, but not eliminated. The reduced-fare program's gaps, verification and staffing, would require new capabilities and partners. If the board wants a targeted discount later, the authority could revisit a reduced-fare program once a verification partner exists, layering it on top of capping rather than replacing it.
References
Federal Deposit Insurance Corporation. (2022). 2021 FDIC national survey of unbanked and underbanked households.
Moore, M. H. (1995). Creating public value: Strategic management in government. Harvard University Press.
Salamon, L. M. (2002). The tools of government: A guide to the new governance. Oxford University Press.
Reading the MMPA 6451 Week 5 instructions
Readiness assessments ask students to evaluate whether an organization can deliver a chosen policy instrument. Prompts usually require a structured assessment of systems, staff, partners and contracts, often as a grid, with commentary on gaps and how to close them. Instructors expect the assessment to compare at least two instruments on the same components. Specific fixes and a sequence are valued. Expect roughly five pages. One version of the prompt wants a single instrument examined closely; another wants two compared. Instructors expect students to define ready, conditional and not ready before applying them. Instructors also look for each not-ready cell to carry a reason and an owner.
How the MMPA 6451 Week 5 example is put together
The paper links readiness to Moore's capacity test. A grid rates six components for two instruments. Commentary takes each conditional or not-ready cell in turn, with national data on unbanked households for the cash gap. A section describes the vendor change order, including a thirty-day test. A sequencing section lays out six months of parallel work. A section names behavioral risks outside the grid. The conclusion compares the instruments and notes a possible later layering. The commentary explains that cash riders are concentrated on east-side routes and that free cards and cash loading could narrow, though not close, the gap. The customer service section notes that a progress lookup tool is a configuration, not a new system.
Where the marks sit in the MMPA 6451 Week 5 rubric
Graders reward a grid with clear definitions of each rating and commentary that explains every gap. Identifying the cash rider gap, and its equity implications, often lifts a paper. A realistic sequence for fixes shows practical sense. Describing contract changes by type, without inventing prices, is appropriate. Naming risks the grid cannot capture shows judgment. Connecting the cash gap to who would be left out shows the student is thinking ahead to equity. Separating system readiness from rider behavior shows that a grid is a tool with limits. A clear comparison in the conclusion helps the decision maker. Describing the vendor change by type and test period, without inventing prices, keeps the assessment credible. Sequenced fixes show realism. Admitting what the grid cannot capture, such as rider confusion in the first months, signals realism.
MMPA 6451 Week 5 help: mistakes that cost marks
List every component your instrument depends on, from data systems to staff to contracts. Rate each for each instrument and define your ratings. For every gap, describe the fix and how long it would take. Arrange the fixes in order. Ask what could still go wrong if every cell were ready. For a custom sample readiness grid for another policy, send us the components. Talk with the people who run each component, if you can, before rating it. Write the basis for each rating in the cell so a reader can challenge it. Keep fixes concrete, with locations, numbers and months. Define your three rating levels before you start.
Get a MMPA 6451 Week 5 example written to your instructions
List the instruments your comparison left standing; the Week 5 prompt and rubric go with them. Your MMPA 6451 readiness assessment rates each component with its basis and names the gaps, delivered in 24 to 48 hours, the first without a fee. Its vendor, fare system and transit authority are stand-ins, and no product is identified.
More MMPA 6451 papers and MPA samples
- MMPA 6451 Week 1: Broadband Inaction Post
- MMPA 6451 Week 2: Voucher Public Value Memo
- MMPA 6451 Week 3: Fare Burden Problem Statement
- MMPA 6451 Week 4: Transit Policy Tool Comparison
- MMPA 6451 Week 6: Policy Entrepreneur Profile
- MMPA 6451 Week 7: Farebox Revenue Memo
- MMPA 6451 Week 8: Backward Mapping Memo
- MMPA 6451 Week 9: Pilot Performance Measures
- MMPA 6451 Week 10: Fare Equity Analysis
- MMPA 6451 Week 11: Transit Board Decision Memo
- WMBA 6000 Week 5: Outage Crisis Leadership Post
- MMHA 6220 Week 5: Fit-for-Duty Policy
- HLTH 8451 Week 5: Criteria Weighting Protocol
- MMHA 6205 Week 5: Clinic Discrimination Case
MMPA 6451 Week 5 questions, answered
Where can I find a free MMPA 6451 Week 5 sample paper?
The fare system readiness assessment is on this page.
What is the main gap for fare capping?
Cash riders, whose payments cannot be linked to an account.
What is the main gap for a reduced-fare program?
Eligibility verification, since no partner can confirm benefit enrollment.
What would the vendor need to do?
Configure the cap rules, update displays and portals and test over a full thirty days.
How long would the fixes take?
About six months if work runs in parallel.