Proposal Writing

Document Structure - EXACT ORDER (no deviations):

1. Abstract
2. Chapter 1 — Introduction
3. Chapter 2 — Literature Review
4. Chapter 3 — Methodology
5. Chapter 4 — Expected Outcomes
6. Time Frame / Schedule (with Gantt chart Fig reference)
7. Budget Estimate
8. References

Overview

This guide specifies the exact structure, word counts, and content requirements for writing research and project proposals. Proposals differ fundamentally from dissertations: they are future-tense, system-focused, and operationally detailed. All proposals follow a global-to-local funnel structure for contextualisation, but with condensed literature review, objective-driven methodology, and practical budget/timeline sections.

Abstract (~150–200 words)

Purpose

Single plain-English paragraph summarizing the entire proposal.

Mandatory Content (in sequence)

1. The Problem: Specific dysfunction or gap at the study site (e.g., poor coordination, paper-based records, equipment failure prediction gaps)
2. The Proposed Solution: Concrete intervention or system being designed (e.g., real-time mobile data collection system, predictive maintenance platform)
3. Tools to be Used: Specific technologies, platforms, software (e.g., KoboToolbox, Power BI, Python, Stata)
4. Expected Benefits: Anticipated outcomes and wider impact (e.g., reduced downtime, improved forecasting, operational efficiency)

Closure

End with a Keywords line listing 5–6 core terms separated by commas.

Language Note

Monolingual English only — unlike dissertations, there is no French Résumé. The abstract is the sole introductory summary.

Chapter 1 — Introduction (~900–1,000 words | ~5–6 pages)

Purpose

Contextualise the research through a global-to-local funnel structure, culminating in specific operational problems at the study site.

Mandatory Funnel Structure

1. Global/International context (e.g., statistics from international bodies, World Bank, FAO)
2. African/Continental context (e.g., regional challenges, Sub-Saharan trends)
3. National context (e.g., Cameroon-specific issues, regulatory environment)
4. Study site context (e.g., Carrière Moderne in Nkoloman, Yaoundé; daily operational problems)

Mandatory Sub-sections

1.1 Background of the Study (~4 pages, longest section)

• Follow the global-to-local funnel structure above
• Begin with international evidence on digital tools/systems in the relevant sector
• Transition through African/continental challenges
• Narrow to Cameroon's context
• Arrive at the specific study site with detailed description of daily operational problems
• End by establishing that the site is emblematic and the system has potential for wider adoption

1.2 Statement of the Problem (~half a page)

• Short, focused paragraph naming the core dysfunction(s) clearly
• Examples: slow information flow, reactive (not predictive) maintenance, absence of production forecasting, workflow inefficiencies
• Conclude by stating explicitly what the study intends to fix

1.3 Research Questions (split into two levels)

• 1.3.1: Single main research question (broad, overarching)
• 1.3.2: Four specific research questions, each corresponding to one dimension of the problem
  • Example dimension 1: Information sharing/reporting
  • Example dimension 2: Machine failure prediction
  • Example dimension 3: Production estimation
  • Example dimension 4: Workflow coordination/efficiency

1.4 Objectives of the Study (mirrors Research Questions exactly)

• 1.4.1: Single main objective (broad, general framing of intent)
• 1.4.2: Four specific objectives worded as actions
  • Language: "To build…", "To develop…", "To create…", "To design…", "To implement…", "To evaluate…"
  • Example objectives:
    • To build a real-time mobile data entry system
    • To develop predictive maintenance models using machine data
    • To create production estimation models using drilling/blasting parameters
    • To evaluate system impact on quarry workflow and user adoption
  • Critical note: These four specific objectives become the spine of the entire proposal — every subsequent chapter references them directly

1.5 Scope of the Study (~half a page)

• Define research boundaries clearly
• State what is INCLUDED (thematic, geographic, temporal scope)
  • Example: "This study encompasses drilling, blasting, machine performance monitoring, production planning, and real-time data collection systems within Carrière Moderne"
• State what is EXCLUDED explicitly
  • Example: "This study does not address market demand forecasting, sales logistics, or supply chain optimization"

1.6 Significance of the Study (~half a page)

• Identify stakeholders who benefit (e.g., quarry managers, equipment operators, maintenance staff, local businesses)
• Explain why the work matters beyond the study site
• Frame the system as a potential model or template for other quarries in Cameroon and similar low-resource settings
• Close with broader development or sustainability implications

Critical Difference from Dissertations

NO Research Hypotheses in proposals. Proposals are engineering/applied science projects focused on system-building and evaluation, not on testing statistical relationships. This is a structural and conceptual break from dissertation structure.

Chapter 2 — Literature Review (~700–800 words | ~4–5 pages)

Purpose

Shorter and thematically organized (not conceptual/theoretical/empirical). Each section covers one topic area directly relevant to the proposed system.

Mandatory Structure (five thematic sub-sections)

2.1 Introduction (~paragraph)

• Short orienting paragraph explaining the chapter's purpose
• Signal the gap to be identified: "While tools and models exist in academic literature, few have been applied to small quarries in low-resource settings"
• Preview the five topic areas covered

2.2 Quarry Operations and Workflow Challenges (~1–2 paragraphs)

• Review literature on coordination problems in quarry environments
• Cover: delays from manual reporting, lack of systematic digital systems in African quarries, communication breakdowns
• Reference specific case studies or regional reports on small-scale mining/quarrying challenges

2.3 Predictive Maintenance in Quarrying (~1–2 paragraphs)

• Review research on using machine data to forecast equipment failure
• Cover: vibration analysis, fuel consumption patterns, run hours, thermal data
• Note existing work focuses on large-scale mining; small local quarries rarely adopt these approaches
• Gap: "Limited literature on predictive maintenance implementation in small quarries in low-resource Africa"

2.4 Production Estimation Models (~1–2 paragraphs)

• Review approaches to forecasting blast output using drilling and blasting parameters
• Cover: burden, spacing, hole depth, explosive type, geological factors
• Include machine learning approaches where relevant
• Gap: "Few models tested in small Cameroonian quarries"

2.5 Digital Data Input Systems for Field Operations (~1–2 paragraphs)

• Review tools used in other sectors (e.g., healthcare data entry, agricultural monitoring, disaster response)
• Platforms: KoboToolbox, ODK, CommCare, etc.
• Make case that these tools have untapped potential in quarrying
• Connect: mobile data systems have proven adoption in Africa; quarrying can benefit from similar approaches

Structure Notes

• Each section is 1–2 paragraphs only
• No standalone conceptual framework diagram (unlike dissertations)
• No formal "Research Gap" sub-section — instead, weave the gap into each thematic section's closing sentence
• End Chapter 2 with a concluding sentence summarizing the combined gap: "While individual tools and methods exist, an integrated system linking real-time data collection, predictive maintenance, and production estimation — tailored to small quarries — remains lacking."

Chapter 3 — Methodology (~700–800 words | ~4 pages)

Purpose

Most structurally distinctive chapter. Rather than generic headings, each sub-section is titled using the specific research objective it addresses. Direct, transparent linkage between objectives and methods.

Mandatory Structure (four objective-driven sub-sections)

3.1 [Objective 1]: Building the Real-Time Data Entry System (~1.5–2 pages)

• Corresponds directly to Objective 1.4.2a (or equivalent)
• Describe activities:
  • Field observations at the quarry (ethnographic exposure to current workflows)
  • Semi-structured interviews with quarry staff (drilling crews, maintenance teams, supervisors) to understand pain points
  • Workflow mapping and process documentation
• Describe design approach:
  • How mobile data entry forms will be designed based on interview findings
  • Form logic, branching, data validation rules specific to quarry operations
  • Adaptation of tools (e.g., KoboToolbox form design)

3.2 [Objective 2 & 3]: Developing Predictive Maintenance and Production Estimation Models (~1.5–2 pages)

• Corresponds to Objectives 1.4.2b and 1.4.2c
• Predictive Maintenance component:
  • Quantitative data to be gathered: machine run hours, fuel consumption, downtime records, maintenance history
  • Modelling approach: time-series analysis, threshold-setting, or machine learning (specify algorithm if known)
  • Validation approach: backtest against historical data
• Production Estimation component:
  • Quantitative data to be gathered: hole depth, burden, spacing, explosive type, blast outcome (tonnage)
  • Modelling approach: regression, statistical calibration, or ML (specify)
  • Validation approach: compare model predictions to actual blast results during pilot phase

3.3 [System Integration & Architecture]: Integrating Data, Models, and Dashboards (~1–1.5 pages)

• Corresponds to the systems-level operationalisation of Objectives 1, 2, and 3
• Data flow pipeline:
  • KoboToolbox captures mobile field data (what, where, when)
  • Data syncs to central database (specify platform: PostgreSQL, cloud storage, etc.)
  • Python scripts run predictive models on fresh data (maintenance and production models)
  • Power BI dashboards visualise real-time status: machine health, upcoming maintenance windows, production forecasts
• System architecture diagram (optional but recommended): boxes for data entry → database → models → dashboard
• User roles: quarry manager sees dashboard; field operators enter data via mobile forms; Python backend runs overnight/continuous analysis

3.4 [Objective 4]: Evaluating System Impact and User Adoption (~1–1.5 pages)

• Corresponds to Objective 1.4.2d
• Describe pilot phase:
  • Timeline: e.g., 4–6 weeks live deployment at Carrière Moderne
  • Participant sample: all (or subset of) quarry staff; focus on regular system users
• Key Performance Indicators (KPIs) to monitor:
  • Operational: downtime reduction, reporting speed improvement, forecast accuracy
  • User-level: system uptake, error rates in data entry, user satisfaction
• Evaluation methods:
  • Quantitative: KPI tracking via system logs and database records
  • Qualitative: follow-up interviews and structured questionnaires with users
  • Analysis: before-and-after comparisons; thematic coding of user feedback

Critical Differences from Dissertations

• No Cochran formula for sample size (this is not a quantitative survey)
• No Cronbach's Alpha reliability test (this is not survey-based measurement)
• No OLS regression model specification (no equations; this is system development, not causal hypothesis testing)
• Methods are tied directly to objectives, not to generic research headings

Chapter 4 — Expected Outcomes (~400–500 words | ~2–3 pages)

Purpose

Replace what would be Chapters 4 and 5 (Results + Conclusion) in a completed dissertation. Written entirely in future tense — describes what the research will produce, not what it found.

Mandatory Structure

4.1 Introduction (~paragraph)

• Brief framing statement
• Clarify that this chapter presents intended results and their anticipated value to the field
• Signal that outcomes align with the four objectives from Chapter 1

4.2 Main Expected Outcomes (four numbered outcomes)

• List four outcomes, each as:

  • Bold heading (concise, parallel to the four objectives)
  • Paragraph of explanation (2–3 sentences detailing what will be delivered and why)

• Outcome 1 [corresponding to Objective 1]: A working real-time mobile data entry system

  • "By the end of the project, the quarry will have a functional KoboToolbox-based mobile application that captures drilling, blasting, and maintenance data in real-time from the field. Field operators will input data directly via smartphones or tablets, eliminating paper-based reporting and reducing information delays by [estimated %]. The system will be designed based on staff workflows identified in preliminary interviews and will include training materials and user documentation."

• Outcome 2 [corresponding to Objective 2]: Predictive maintenance models tailored to local quarry equipment

  • "The project will develop regression-based or machine learning models that forecast equipment failure windows based on historical run hours, fuel consumption, and downtime patterns. These models will generate maintenance alerts to the quarry manager 7–14 days in advance, allowing preventive rather than reactive maintenance scheduling. Estimated impact: [reduction in unplanned downtime]."

• Outcome 3 [corresponding to Objective 3]: Production estimation models for blast forecasting

  • "Using drilling and blasting parameters (hole depth, burden, spacing, explosive type), the project will calibrate statistical or ML-based models that forecast blast tonnage output. Quarry planners will use these models to align production with demand and adjust blasting parameters for better yields. Estimated improvement in forecast accuracy: [%]."

• Outcome 4 [corresponding to Objective 4]: Rigorous evaluation of system impact and adoption insights

  • "Through pilot deployment and user feedback, the project will document: (a) operational improvements in downtime rates and reporting speed; (b) user adoption patterns and training needs; (c) technical challenges and system refinements required for broader deployment. A written case study and user feedback report will serve as a model for replicating this system in other Cameroonian quarries and similar low-resource contexts."

Tone and Language

• Use conditional language: "will deliver", "is expected to", "will demonstrate"
• Be specific: avoid vague claims; tie each outcome to metrics or concrete deliverables
• Create closed loop: each outcome directly mirrors its corresponding objective from Chapter 1

Time Frame / Schedule (~1–2 pages)

Purpose

Unique to proposals. Demonstrates realistic project planning and feasibility.

Mandatory Components

Written Activities and Timeline Table

• Rows: each of the four main objectives (or major project phases)
• Columns: Key Activities, Weeks/Dates, Responsible Party
• Example:

  Objective	Key Activities	Timeline	Responsible
  1. Data System	Workflow analysis, form design, KoboToolbox setup	Week 1–3 (May)	Researcher + IT Support
  2 & 3. Models	Data collection, model development, validation	Week 3–6 (May–June)	Researcher + Data Analyst
  System Integration	Database setup, Power BI dashboard build, Python integration	Week 5–7 (June)	Researcher + IT
  4. Evaluation	Pilot deployment, KPI monitoring, interviews, analysis	Week 7–9 (June–July)	Researcher + Field Assistant

Gantt Chart (Figure)

• Visual timeline spanning the full project window (e.g., May 2025 to July 2025, nine weeks)
• Bars showing: objectives/phases, milestones, dependencies, final defence week
• X-axis: weeks or dates; Y-axis: objectives or phases
• Label final week as "Defence" or "Project Defence"
• Include legend distinguishing between planning, execution, and evaluation phases

Specificity

• Give exact dates if possible; at minimum use weeks and calendar months
• Identify dependencies (e.g., "Model development follows data collection")
• Allocate realistic time for pilot, feedback collection, and refinement

Budget Estimate (~half a page)

Purpose

Unique to proposals. Demonstrates realistic, responsible project planning to the supervising institution.

Mandatory Components

Itemised Cost Table

• Currency: FCFA (Cameroon)
• Rows: specific cost categories with descriptions and quantities
• Columns: Item, Quantity, Unit Cost, Total Cost
• Include all anticipated costs, such as:
  • Transportation and lodging (field visits to quarry)
  • Internet subscription (mobile data for field operations, cloud sync)
  • KoboToolbox subscription or licensing
  • Field assistant allowance (per day or per month)
  • Power BI and Python setup/licensing (if applicable)
  • Printing and binding (project reports, questionnaires)
  • Database hosting or cloud storage
  • Miscellaneous contingency (~10%)

Total Estimated Budget

• Sum all line items
• State in FCFA
• Example: "Total Estimated Budget: 235,000 FCFA"

Tone

• Realistic and detailed
• Shows due diligence and responsible stewardship of institutional resources
• No inflated or speculative costs

References (~1 page)

Mandatory Format

• APA format (strict adherence: authors, year, title, journal/publisher, DOI/URL)
• Typical count: 11–15 sources
• Date range: Prioritize recent publications (2017–2022, or within 5–7 years of proposal year)
• Source types: Mix of peer-reviewed journal articles, institutional reports (World Economic Forum, Deloitte, FAO, World Bank), case studies
• Thematic coverage: Drawn from the lit review sub-sections (quarry operations, predictive maintenance, production models, digital data systems)

Notes

• No appendices in the proposal document itself
• Instruments (observation checklist, interview guide, questionnaire, data entry forms) will be attached separately in the final project submission, if required by the institution
• References section ends the proposal; it is not followed by appendices

Critical Structural Distinctions from Dissertations

Key Principles for Proposal Writing

1. Funnel structure: Global → Continental → National → Site-specific (shared with dissertations)
2. Objective-driven methodology: Methods are organized by objectives, creating transparent linkage
3. Future-tense outcomes: Everything is what will be delivered, not what was found
4. System-focused: Emphasis on design, integration, and implementation, not hypothesis testing
5. Operational detail: Budget, schedule, KPIs, and user roles are explicit and realistic
6. Monolingual: English only; no French component
7. Feasibility first: Proposal demonstrates that the project is achievable within stated resources and timeframe
8. Broader model potential: Frame site-specific project as a replicable model for wider adoption

When Applying This Guide

• Full proposal: Use all sections (Abstract through References, including Schedule and Budget)
• Proposal chapter: Use the specific chapter structure (e.g., "Write Chapter 2 Literature Review following proposal format")
• Proposal revision: Ensure objectives in Chapter 1 are mirrored in Chapter 3 methodology and Chapter 4 outcomes
• Multi-site proposals: Adapt the funnel structure to each site, or create parallel sections for each geographic context
• Cross-checking: Always verify that Chapter 3 methods map one-to-one to Chapter 1 objectives, and Chapter 4 outcomes mirror Chapter 1 objectives