Mastering Guide Permits Citations Smarter Commuting Essentials

Understanding the Legal Framework of Permits for Smarter Commuting

Regulatory Distinctions Between Local, State, and Federal Permits

Influence of Zoning Laws and Transportation Master Plans on Permit Approvals

1. Zoning Overlays and Land-Use Restrictions
Zoning ordinances dictate how commuting infrastructure can be integrated into urban areas. For instance:

2. Transportation Master Plans as Permit Gatekeepers
Master plans (e.g., the Los Angeles County Transportation Commission’s 2050 Scenario Planning) define priority corridors and funding allocations. Permits for projects outside these plans face higher scrutiny:

3. Environmental and Equity Mandates
Modern zoning and master plans increasingly incorporate environmental justice and climate resilience requirements. Permits may be denied or modified if they:

Key Takeaway:
Permit applicants must proactively align projects with zoning maps and master plans to avoid last-minute rejections. Pre-application workshops with local planning departments can identify zoning loopholes or master plan gaps that could derail approvals.

Case Studies: Permit Denials and Delays in Smarter Commuting Programs

Case Study 1: Denver’s E-470 Express Lanes Expansion (2016–2020)
Permit Issue: The $1.2 billion dynamic tolling pilot for E-470 faced a 2-year delay due to:

Federal NEPA objections over wetland impacts near the Platte River.

State-level funding disputes between CDOT and the Colorado Department of Transportation (CDOT) over toll revenue sharing.

Local NIMBY opposition from adjacent neighborhoods citing increased traffic noise.

Resolution:

CDOT secured a Section 4(f) permit by relocating a wetland buffer.

Negotiated a public-private partnership (P3) to share toll revenues with local municipalities.

Key Takeaway: Early engagement with federal environmental agencies and affected communities could have reduced delays by 18 months.

Case Study 2: Portland’s Protected Bike Lane Network (2018–2021)
Permit Issue: The $100 million "Missing Sidewalk" project to add protected bike lanes on SE Division Street was stalled for 18 months due to:

Local business objections (restaurants feared reduced parking would hurt foot traffic).

State DOT resistance to temporary lane closures during construction.

Zoning conflicts with the Portland Development Commission’s (PDC) short-term rental ordin

Citations and Compliance: Avoiding Legal Pitfalls in Smarter Commuting Projects

Smarter commuting initiatives—such as microtransit corridors, shared mobility zones, and dynamic lane management—require rigorous adherence to permit conditions to mitigate legal exposure. Non-compliance often results in citations, project delays, or forced modifications, with municipalities and private operators facing recurring violations in environmental assessments, right-of-way encroachments, and public participation deficiencies. Below is an analysis of the most frequent citations, structured compliance protocols, and risk mitigation strategies tailored to high-risk project types.

Most Common Citations in Smarter Commuting Permits

Permit violations in commuting projects typically stem from procedural oversights or operational deviations. The following citations are ranked by frequency based on enforcement patterns in U.S. and EU jurisdictions, with examples from case studies in cities like Los Angeles, Barcelona, and Singapore:

1. Incomplete or Untimely Environmental Reviews

Issue: Failure to conduct required assessments (e.g., NEPA in the U.S. or EIA in the EU) or submit findings before project commencement. Common in microtransit corridors where noise/vibration impacts on residential areas were underreported.

Example: A 2022 citation in Portland, Oregon, resulted in a $120,000 fine after a shared mobility pilot failed to disclose baseline air quality data during the 30-day public comment period.

2. Right-of-Way Violations

Issue: Unauthorized use of public streets for dedicated lanes, loading zones, or mobility hubs without proper easements or permits. Private operators often misclassify temporary installations as permanent.

Example: In Barcelona, a €85,000 penalty was issued to a ride-sharing platform after installing bike-sharing racks on sidewalks without a Public Space Use License, violating municipal zoning bylaws.

3. Public Notice and Participation Deficiencies

Issue: Missing or inadequate notice periods (e.g., <30 days for major projects) or failure to engage affected stakeholders (e.g., businesses, disabled communities). Courts often scrutinize lack of bilingual notices in diverse urban areas.

Example: A 2021 lawsuit in Chicago against a scooter-sharing program was dismissed after proving the operator had not translated notices into Spanish, violating the Americans with Disabilities Act (ADA) accessibility requirements.

4. Operational Non-Compliance with Permit Conditions

Issue: Deviations from approved designs (e.g., exceeding speed limits in shared zones, altering vehicle types in microtransit routes). Automated enforcement (e.g., traffic cameras) has increased citations for real-time violations.

Example: London’s Transport for London (TfL) issued £42,000 in fines to a mobility-as-a-service (MaaS) provider after its electric shuttles exceeded 8 mph in bus lanes, violating Transport Act 2000 conditions.

5. Failure to Secure Insurance or Liability Waivers

Issue: Operating without commercial general liability (CGL) insurance or failing to obtain waivers from property owners for shared mobility zones. Subcontractors (e.g., third-party charging providers) are frequent culprits.

Example: A $75,000 claim in Austin, Texas, arose when a microtransit operator lacked umbrella liability coverage for a collision involving a shared vehicle, leading to a temporary suspension of its permit.

6. Non-Compliance with Accessibility Standards

Issue: Designing mobility zones or transit stops without ADA-compliant features (e.g., tactile paving, wheelchair ramps, audible signals). Retrofitting costs often exceed original budget allocations.

Example: A $150,000 settlement in New York City was reached after a dockless bike program’s stations lacked sloped approaches, violating Section 504 of the Rehabilitation Act.

Pre-Approval Compliance Checklist for Smarter Commuting Projects

Proactive compliance reduces citation risks by ensuring all legal and procedural requirements are met before project initiation. The following checklist aligns with U.S. federal (NEPA, ADA), state (e.g., California’s CEQA), and EU (SEA Directive) frameworks, with adaptations for private-sector operators.

Environmental and Regulatory Reviews
Environmental assessments are non-negotiable for projects with potential impacts on air quality, noise, or habitat. Jurisdictions may require Categorical Exclusions (CEs) for low-impact projects or full Environmental Impact Statements (EIS) for high-risk corridors.

Conduct a preliminary screening to determine if the project triggers NEPA (U.S.) or EIA (EU) thresholds (e.g., >100 vehicles/day in a shared zone).

Engage an environmental consultant to prepare a Tier 1 Assessment for noise, emissions, and traffic congestion, including baseline data collection (e.g., 24-hour monitoring for 30 days).

Submit Tier 2 Mitigation Plans for identified impacts (e.g., low-emission zones for electric microtransit, buffer zones for residential areas).

Public Notice Requirement: Publish notices in local newspapers, community bulletin boards, and official portals (e.g., Regulations.gov for U.S. projects) with a minimum 45-day comment period for major projects.

Provide multilingual translations if the project area has limited-English-proficient (LEP) populations (required under Title VI of the Civil Rights Act).

Right-of-Way and Land Use Agreements
Shared mobility and transit corridors often require temporary or permanent easements. Unauthorized use leads to immediate cease-and-desist orders.

Obtain written approvals from city engineers, public works, and traffic departments for street modifications (e.g., flexible post installations, lane markings).

Secure Right-of-Way Permits for:

Dedicated lanes (e.g., bus-only or microtransit lanes).

Loading/unloading zones for shared vehicles.

Parking conversions (e.g., car-to-bike ratios in shared mobility hubs).

Negotiate indemnification clauses with property owners for private land encroachments (e.g., charging stations on sidewalks).

Insurance Requirements: Maintain $2M in commercial liability coverage and $1M property damage insurance for all operational assets.

Public Participation and Transparency
Lack of stakeholder engagement is a leading cause of legal challenges. Courts often invalidate permits if disproportionate harm to communities is not addressed.

Host public workshops with translated materials and ASL interpreters if applicable.

Conduct household surveys in affected areas to assess equity impacts (e.g., low-income access to shared transit).

Publish draft permit applications on open-data portals (e.g., Data.gov, EU Open Data Portal) for 30 days before submission.

Appoint a community liaison to address concerns during the permit review phase.

Operational and Safety Compliance
Real-time monitoring of operational parameters (e.g., speed, vehicle types) is critical to avoid citations.

Implement GPS-tracked fleet management to enforce speed limits in shared zones (e.g., <15 mph in urban areas).

Vehicle Certification: Ensure all shared vehicles meet local emissions standards (e.g., Euro 6 in the EU, California’s LEV II).

Accessibility Audits: Verify compliance with ADA/EN 1721 for:

Drop-off/pick-up zones (minimum 5-foot clearance).

Digital interfaces (screen reader compatibility for MaaS apps).

Emergency Response Plans: Submit fire department pre-plan approvals for battery storage facilities in microtransit depots.

Legal Risks: Retroactive Permit Modifications vs. Proactive Compliance

Retroactive permit modifications—whether through administrative corrections or judicial review—pose significant legal and financial risks compared to proactive planning. The following comparison highlights key differences for microtransit corridors and shared mobility zones:

Risk Factor	Retroactive Modifications	Proactive Compliance Planning
Timeframe	6–24 months (litigation delays common)	3–6 months (aligned with permit timelines)
Cost Overrun	2–5x higher (retrofitting infrastructure, legal fees)	1.1–1.5x baseline (integrated into initial budget)

Strategies for Streamlining Permit Processes in Smarter Commuting

Accelerating permit approvals for smarter commuting projects—such as bike lanes, transit signal priority, and micro-mobility corridors—requires targeted administrative reforms that reduce bureaucratic friction while maintaining compliance. Cities like Portland (Oregon) and Copenhagen have demonstrated how integrated digital platforms, pre-application stakeholder engagement, and tiered approval pathways can cut processing times by up to 70% for low-impact infrastructure. This section outlines high-impact reforms, step-by-step fast-tracking protocols, and negotiation frameworks to resolve conflicts with utilities or preservation boards, alongside comparative timelines and decision matrices for experimental projects.

The efficiency gains from streamlined permit processes extend beyond project timelines; they also improve public trust by demonstrating responsiveness to mobility needs while mitigating legal risks. Below are evidence-based strategies, including real-world case studies, to operationalize these reforms.

High-Impact Administrative Reforms in Accelerated Permit Systems

Portland and Copenhagen have implemented three key reforms that serve as models for other cities seeking to expedite smarter commuting permits:

1. Unified Digital Permit Portals
Portland’s Permit Portland platform consolidates submissions, tracking, and approvals for transportation projects into a single interface, reducing cross-departmental delays. Copenhagen’s Digital Bygnings- og Miljøportal (Digital Building and Environment Portal) automates compliance checks for bike infrastructure, cutting review times by 40% for minor projects. These portals integrate with GIS mapping tools to pre-validate site feasibility, flagging conflicts with utilities or preservation zones before submission.

Key Feature: Automated conflict detection (e.g., underground utilities, historic easements) at the point of submission, with real-time notifications to relevant agencies.

2. Pre-Application Workshops with Stakeholders
Copenhagen’s "Mobility Lab" holds mandatory workshops 90 days before project submissions, where city planners, utility providers, and preservation boards collaboratively resolve potential issues. Portland’s Bike Lane Accelerator Program offers similar sessions, where engineers and community groups pre-negotiate design adjustments (e.g., temporary lane widths) to avoid later disputes. These workshops reduce permit denials by 35% by aligning expectations upfront.

Outcome: 60% of pre-workshop participants report fewer post-approval modifications, as conflicts are addressed in collaborative design reviews.

3. Tiered Approval Pathways for Project Risk
Both cities categorize projects into three risk tiers based on impact:

Tier 1 (Low Risk): Pop-up bike lanes, e-scooter pilot zones (approved in <14 days).

Tier 2 (Moderate Risk): Dedicated bus lanes, transit signal priority (approved in <45 days).

Tier 3 (High Risk): Major street redesigns (full environmental review).

Tier 1 projects bypass certain reviews (e.g., historic preservation for temporary installations), while Tier 2 projects trigger automated utility coordination meetings. This system ensures faster turnarounds for reversible or experimental interventions.

Step-by-Step Guide for Fast-Tracking Low-Impact Smarter Commuting Permits

Pop-up bike lanes, real-time transit signal priority (TSP), and e-scooter pilot programs often face unnecessary delays due to over-applied regulations. The following 5-step protocol aligns with Portland’s "Quick-Build" program and Copenhagen’s "Temporary Mobility Zones" framework, reducing processing time to <30 days for eligible projects.

1. Pre-Submission Feasibility Assessment
   Conduct a 30-minute GIS-based conflict check using city-provided tools (e.g., Portland’s StreetSaver or Copenhagen’s Trafikplanlægning). Verify:
   
2. No underground utilities within 2 meters of proposed lane edges.
3. No historic preservation overlays for temporary installations.
4. Alignment with existing mobility master plans.
Example: Copenhagen’s "Cykelspor" tool flags 90% of utility conflicts before submission.
5. Stakeholder Pre-Notification
   Email or invite utility companies (e.g., Portland General Electric, Copenhagen Energy) and preservation boards to a mandatory 2-hour virtual meeting. Present:
   
6. Project scope (e.g., "1-mile pop-up lane for 6 months").
7. Mitigation plans (e.g., phased utility cuts, detour signs).
8. Timeline for installation and removal.
Note: Copenhagen requires utility responses within 48 hours for Tier 1 projects.
9. Submission via Accelerated Portal
   File using the city’s unified permit portal with:
   
10. Signed Tier 1/Tier 2 designation form.
11. Digital site plans (PDF or CAD) with conflict-free zones highlighted.
12. Public notice (if required) via city-approved channels (e.g., Portland’s "Notice of Intent").
Automated Response: The system routes the application to a dedicated "Mobility Fast-Track" team within 24 hours.
13. 14-Day Review with Conditional Approval
    The fast-track team issues a conditional approval within 14 days, listing:
    
14. Required modifications (e.g., "Reduce lane width by 0.5m near hydrant").
15. Utility coordination deadlines.
16. Inspection dates for installation.
Example: Portland’s Bike Lane Accelerator achieves 92% conditional approvals in this phase.
17. Installation and Compliance Monitoring
    
18. Inspection: City engineers verify compliance before opening (e.g., 2-hour site visit for pop-up lanes).
19. Real-Time Adjustments: Use IoT sensors (e.g., Copenhagen’s "Smart Cycle Tracks") to monitor usage and utility impacts, triggering adjustments without new permits for Tier 1 projects.
20. Automatic Renewal: For projects under 180 days, renewal applications are pre-populated with usage data, reducing paperwork by 80%.

Negotiation Tactics for Resolving Permit Disputes with Utilities and Preservation Boards

Conflicts over dedicated bus lanes, underground cable relocations, or historic district adjustments often stall smarter commuting projects. The following five-lever negotiation framework, adapted from Copenhagen’s "Conflict Resolution Toolkit" and Portland’s "Utility Coordination Playbook," systematically addresses objections while preserving project viability.

1. Anchor with Phased Implementation
   Tactic: Propose a pilot phase (e.g., 3-month bus lane) to demonstrate minimal disruption.
   Example: When Copenhagen expanded dedicated bus lanes on Amager Boulevard, they initially limited the lane to peak hours only, reducing utility relocation costs by 60% while proving demand.

   Key Phrase: "We’ll commit to a reversible design for the first 90 days to mitigate risk for all parties."

2. Leverage Utility Incentives
   Tactic: Offer cost-sharing or priority access to city-owned utility corridors in exchange for expedited approvals.
   Example: Portland’s StreetSaver program provides utilities with discounted right-of-way fees for projects that align with their underground infrastructure upgrades.

   Data Point: 78% of utility disputes in Copenhagen were resolved within 10 days when tied to shared infrastructure goals.

3. Preempt Historic Preservation Objections
   Tactic: Frame changes as temporary or adaptive reuse (e.g., "This bike lane uses existing street furniture, not new construction").
   Example: When Copenhagen proposed a pop-up bike lane on Nørrebrogade, the preservation board approved it as a "temporary activation of public space" under Denmark’s Cultural Heritage Act §42.

   Legal Reference: Many preservation boards classify reversible interventions (e.g., removable bollards) as non-destructive modifications, exempt from full review.

4. Escalate to Cross-Departmental Mediation
   Tactic: If deadlocked, request a joint meeting with the Mayor’s Office or City Council Transportation Committee to align priorities.
   Example: Portland resolved a 6-month stalemate over a dedicated bus lane on SE Division Street by presenting it as a climate action priority in a public hearing, overriding utility objections.

   Statute: Under U.S. Code §23 U.S.C. 109(j), federal transit funds can be withheld
   

   Data-Driven Permitting: Leveraging Technology for Smarter Commuting Approvals

   The evolution of smart city infrastructure demands dynamic, real-time permit approvals that align with commuting project impacts. Data-driven permitting integrates IoT sensors, predictive analytics, and blockchain to automate compliance monitoring, reduce administrative overhead, and enhance transparency. This approach shifts from reactive enforcement to proactive risk mitigation, ensuring permits reflect real-world operational conditions while minimizing legal exposure for municipalities and private stakeholders.

   Technological advancements enable permit systems to evolve from static approvals to adaptive frameworks that respond to live data. For instance, IoT sensors embedded in traffic signals or air quality monitors can feed real-time metrics into permit databases, triggering automated alerts for deviations from approved project parameters. Predictive models further refine this process by analyzing historical permit violations to preemptively identify high-risk scenarios. Below, the technical and operational components of this system are detailed, including sensor integration, analytics pipelines, compliance dashboards, API workflows, and blockchain applications for shared mobility governance.
   

   Technical Specification for IoT Sensor Integration in Permit Applications

   The integration of IoT sensors into permit approval workflows requires standardized protocols for data collection, transmission, and validation. Sensors must be deployed at critical commuting infrastructure nodes—such as intersections, transit hubs, and roadway segments—to monitor metrics such as traffic volume, congestion levels, noise pollution, and particulate matter (PM2.5/PM10) concentrations. Below is a technical specification for sensor deployment and data ingestion:

   # IoT Sensor Specification for Smarter Commuting Permits
   

   1. Sensor Types and Deployment

   Traffic Flow Sensors:

   Inductive loop sensors (embedded in roadways) for vehicle classification and speed.

   Bluetooth/Wi-Fi sniffers (e.g., Roadside Units) for anonymous vehicle tracking and origin-destination analysis.

   Camera-based systems (AI-powered) for lane occupancy and pedestrian movement.

   - Environmental Sensors:
   

   Low-cost air quality monitors (e.g., PurpleAir, AQR-300) for CO₂, NO₂, and particulate matter.

   Acoustic sensors (e.g., Infrasound microphones) for noise pollution mapping.

   - Infrastructure Health Sensors:
   

   Vibration sensors on bridges/tunnels to detect structural stress from increased traffic.

   Temperature and humidity sensors for pavement condition monitoring (e.g., freeze-thaw cycles).

   ## 2. Data Transmission Protocol
   

   Communication: LoRaWAN or NB-IoT for long-range, low-power sensor networks.

   Data Format: JSON payloads with timestamps, geolocation (GPS/WGS84), and sensor metadata.

   Encryption: AES-256 for data-in-transit; TLS 1.3 for cloud ingestion.

   ## 3. Data Validation Rules
   

   Anomaly Detection: Statistical thresholds (e.g., ±3σ from baseline) to flag sensor malfunctions.

   Geofencing: Only accept data within predefined permit zones (e.g., project boundaries).

   Timestamp Synchronization: NTP (Network Time Protocol) for sub-second accuracy.

   ## 4. API Endpoints for Permit Systems
   

   POST /api/sensors/data: Ingest sensor payloads with validation.

   GET /api/sensors/health: Query sensor operational status.

   PATCH /api/sensors/calibrate: Trigger remote calibration for drift correction.

   Sensor data must be cross-referenced with permit conditions (e.g., "Permit #SC-2024-0432 requires ≤50% increase in PM2.5 during rush hour"). Automated workflows can then trigger compliance alerts when thresholds are breached, enabling preemptive corrective actions (e.g., traffic rerouting, construction schedule adjustments).
   

   Predictive Analytics for Preemptive Violation Detection

   Predictive analytics transforms historical permit data into actionable insights by identifying patterns that precede violations. Machine learning models—trained on datasets from past enforcement actions, traffic simulations, and environmental studies—can forecast high-risk scenarios with 70–90% accuracy (e.g., Portland’s Traffic Prediction Model). Key components of this system include:

   ### Data Sources for Model Training
   Permit databases must integrate the following datasets to build robust predictive models:
   

   Historical Violation Records: Dates, types (e.g., noise, emissions), and resolution times.

   Traffic Simulation Outputs: Microsimulation tools (e.g., VISSIM, Aimsun) to model congestion under permit scenarios.

   Weather and Seasonality Data: NOAA APIs for temperature, precipitation, and wind patterns affecting air quality.

   Public Complaints: 311 call logs and social media sentiment analysis (e.g., Twitter hashtags like #TrafficJam).

   ### Model Architectures
   

   Supervised Learning: Random Forest or XGBoost classifiers to predict violations based on features like time-of-day, project phase, and sensor anomalies.

   Time-Series Forecasting: LSTM networks to detect emerging trends (e.g., gradual increase in PM2.5 over 30 days).

   Anomaly Detection: Isolation Forest or Autoencoders to flag outliers in real-time sensor streams.

   ### Example Use Case: Noise Violation Prediction
   A model trained on 5 years of noise permit data in New York City could identify that construction permits issued on Tuesdays between 8–10 AM have a 60% higher violation rate due to school traffic patterns. The system would then:
   1. Flag the permit during approval for additional mitigation requirements (e.g., sound barriers).
   2. Schedule proactive inspections using computer vision to detect non-compliance (e.g., missing barriers).
   3. Auto-generate warnings to contractors via SMS/email when sensor data nears thresholds.
   

   Dashboard Mockup for Permit Compliance Monitoring

   A real-time compliance dashboard consolidates sensor data, predictive alerts, and administrative workflows into a unified interface for permit officers, engineers, and city planners. Below is a descriptive mockup of key widgets and their functionalities:

   .class="dashboard" {
   / Header: Project Overview /
   .widget {
   title: "Permit SC-2024-0432: Downtown Bike Lane Expansion";
   status: "Active | Compliance: 89% (Threshold: 90%)";
   timeline: "Phase 1 (May–July 2024) | Phase 2 (Aug–Oct 2024)";
   critical-path: [
   "Traffic Impact Analysis (Due: June 15)",
   "Noise Mitigation Inspection (Due: June 22)"
   ];
   }

   / Row 1: Real-Time Metrics /
   .widget {
   id: "live-metrics";
   panels: [
   {
   title: "Traffic Flow",
   value: "12,450 VPD (Target: ≤15,000)",
   trend: "↓ 3% (24h)",
   sensor-locations: ["Intersection A", "Bike Lane Segment B"],
   color: "#4CAF50" / Green /
   },
   {
   title: "Air Quality (PM2.5)",
   value: "18 µg/m³ (Threshold: 25 µg/m³)",
   trend: "↓ 12% (Weekly)",
   sensor-locations: ["Monitor Station 3"],
   color: "#FFEB3B" / Yellow /
   }
   ];
   }

   / Row 2: Violation Trends /
   .widget {
   id: "violation-trends";
   chart-type: "Bar + Line";
   data-series: [
   {
   label: "Noise Violations",
   data: [0, 1, 3, 2, 0], / Last 5 days /
   threshold: 2,
   color: "#F44336"
   },
   {
   label: "Traffic Delays",
   data: [0, 0, 1, 0, 0],
   threshold: 1,
   color: "#2196F3"
   }
   ];
   callout: "⚠️ 1 noise violation detected at 10:47 AM (Location: Construction Site C)";
   actions: ["View Incident", "Escalate to Contractor"];
   }

   / Row 3: Inspection Schedules /
   .widget {
   id: "inspections";
   table-columns: ["Date", "Type", "Inspector", "Status", "Notes"];
   rows: [
   ["2024-06-22", "Noise Mitigation", "Officer Smith", "Scheduled", "Contractor notified"],
   ["2024-06-25", "Traffic Count", "Officer Lee", "Overdue", "Sensor calibration issue"]
   ];
   calendar-integration: "Google Calendar API";
   }

   / Row 4: Public Feedback /
   .widget {
   id: "public-feedback";
   sentiment-analysis:

   Transforming commuting systems through permits and citations is not merely a bureaucratic exercise—it is a strategic imperative for sustainable urban development. The insights provided here underscore the necessity of proactive compliance planning, technological integration, and collaborative negotiation to overcome permit-related barriers. From comparative jurisdiction analyses to real-time monitoring dashboards, the strategies outlined empower stakeholders to turn regulatory challenges into opportunities for innovation. By adopting a data-driven, reform-oriented mindset, cities can accelerate the transition toward smarter, more efficient commuting solutions while maintaining full legal and operational integrity.

   • permit compliance
   • regulatory frameworks
   • smarter commuting
   • transportation policy
   • urban mobility

   Leave a Comment

   Name

   Comment

   Post Comment

   Comments are moderated before appearing. The data you submit is processed according to the Privacy Policy of ir.msu.ac.zw.