ChundR

Master Your Terrain
Secure Sign In

Welcome to ChundR

Sign in with your ChundR account.
Today • Live Operations

ChundR

Loading…
● Live • ready
Live Weather & Trail Conditions
Loading field weather…
Official warnings + forecast-based trail guidance
LIVE
Loading weather and trail operating guidance…
Live RadarTap to view precipitation nearby
Radar loads when opened.
Live precipitation radar • organization weather location
Today Command
See the day. Catch the risk. Move the work.
Home is the operational command surface—not a duplicate of every ChundR module. Use it to understand today, spot what needs attention, and jump directly to the next action.
✦ Talus Field Intelligence
Reading today’s operation…
AI
ChundR will combine the operational data already loaded on this device and surface the most useful field takeaway.
Why?
  • Waiting for current project and weather context.
Decision support only • live records and safety rules remain authoritative

1. Today

What is happening right now
A fast read of staffing, equipment, project state, and production for the active workday.
Today’s Crew—Loading
Active Equipment—machines + vehicles in service
Current Project—Loading
Today’s Production—
goal loading0%

3. Next Move

What should happen next
Choosing the next field action…
Ready to RollCan today’s work start safely and correctly?
ChundR checks people, work area, directives, assets, access, and operating risks. Open this when you need the full readiness checklist.
FIELD PLAN
Loading…
—
READY
Precon — • Crew — • Requests — • Issues — • Weather —
Project Pulse
Checking project status…
CHECKING
0 / —0%
Crew
—
Machine
—
Truck
—
Precon statusChecking directives…
✓Precon
Precon

Review Precon

Current directives
Loading current Precon…
＋Progress
Project Progress

Record Progress

Current field day
Current Today0 LF
Daily Goal400 LF
Today’s completion0%
LF
Enter only the new progress since your last update. ChundR adds it to today’s total.
⚠️Issue
Field Issue

Report an Issue

Current project
Photo evidenceCapture equipment damage or the trail condition that is slowing the crew down.
＋Request
Team Lead Request

Request Field Support

Current project
📷Field Photo
Field Photo

Document Today’s Work

Current project • today’s field log
Use this for progress, before/after work, completed features, or anything worth showing management in the EOD. Problems belong under Issue.
Field DetailsHours • mileage • time • issues • EOD
⏱Machine Hrs
Field Details

Machine Hours

Today’s field log
Choose the machine used today.
Enter the actual hour-meter readings. ChundR calculates today’s machine hours automatically and carries them into EOD.
⌁Truck Miles
Field Details

Truck Miles

Today’s field log
Choose the truck used today.
Enter the actual odometer readings. ChundR calculates today’s miles automatically and carries them into EOD.
⏱Time Tax
Field Details

Time Tax

Today’s field log
Capture delays or gains that explain why today’s production changed. Each entry becomes part of the EOD story.
✓Inspection
Field Details

Inspection

Today’s field log
3
Fair / workable
1 Poor2345 Excellent
Today’s TimelineChundR builds the story automatically
Signals from crew, Keepers, production, issues, and WHY events.
No timeline loaded yetOpen this section to build today’s operational story.

My Assigned Work

What you are responsible for right now
5. Field ContextActivity • team • handoff
Supporting information stays one tap away without competing with today’s primary actions.

Recent Activity

What changed most recently

Today’s Team

Who is assigned to today’s project

Field Handoff

What the next person needs to know
Building today's handoff…
Schedule Command
Plan the work. Balance the team. Catch conflicts early.
Schedule is for future and current work planning: where crews are going, what they are doing, who is leading, what equipment is committed, and what changed.
Choose the view for the question you are asking.
Today = execute the current plan. 7-Day = look ahead and catch risks. Crew Board = compare staffing and committed equipment side by side. Calendar = navigate by date and open the plan for any day.
Upcoming Work0scheduled blocks in the next 7 days
Needs Review0changes / holds requiring attention

7-Day = Plan Ahead

Rolling 7-day operating window
Use this view to understand the upcoming sequence of work, spot changes, and correct conflicts before crews arrive in the field.

Schedule Intelligence

Conflicts and readiness risks before they reach the field
ChundR checks overlapping crews, Team Leads, committed equipment, schedule changes, and Precon readiness. This is a warning layer—not another schedule.
Scanning crews, leads, equipment, and Precon readiness…

Look-Ahead Work Blocks

The upcoming field plan, one scheduled block at a time
Each block is a planned piece of field work. Open one to see the trail, crew, Team Lead, timing, equipment, work plan, and any change notes.
Operations Workboard
One workboard. Three clear lanes.
Daily Ops handles planning and setup. Trail Crew handles reported field work through completion. Keepers handles volunteer assignments and Trail Days. Each lane has a different purpose, but all records stay connected.

Daily Operations

Build and communicate the day’s operating plan
Today’s operational setup
Use this lane before and during the workday to confirm staffing, project responsibility, Precon directives, required documentation, and operational requests.

Staffing Board

Who is covering each active project
Use this to spot missing coverage, staffing gaps, and conflicting assignments before they affect field work.

Project Team

The Team Lead and crew responsible for this project
Team change historyPrevious staffing changes

Precon Directives

Current instructions that must be understood before work begins
Management instructions, current revision, and team acknowledgements will appear here.
Precon historyPrevious versions & acknowledgements

Required Photo Documentation

Photos management requires before, during, or after work

Open Operational Requests

Requests that still need action or a response

Trail Crew Work

Turn field observations into assigned, trackable work
Report it once. Track it to completion.
Every field issue becomes a saved operational record that can be reviewed, mapped, assigned, worked, resolved, and verified without losing the original report.

Open Trail Issues

Reported problems that are not yet closed

Field Inspections

Recent condition checks and verification records

Active Trail Crew Work

Assigned work orders currently moving toward completion
Trail Crew historyAssignments • report changes • audit record

Work Assignment History

Who work was assigned to, reassigned to, and when

Issue & Request History

Protected history of operational reports, requests, and status changes

Keeper Operations

Keeper stewardship, Trail Days, hours, and support
Keeper stewardship stays in its own lane.
Use this lane to organize Keeper assignments, Trail Days, volunteer hours, time corrections, and staff support without mixing volunteer work into professional trail-crew work orders.

Assigned Gear

Keeper program resources only
Keeper Manager
Only what management assigned to you.
This is a read-only field view of vehicles and tools assigned to your Keeper program. Full inventory, maintenance administration, access points, and organization-wide assets remain with Managers.

Vehicles

Assigned to you
Loading assigned vehicles…

Tools

Assigned to you or your vehicle
Loading assigned tools…
Asset Command
Know what it is. Know where it is. Know who has it. Know what it needs.
ChundR separates inventory, field accountability, maintenance, and protected history so machines, vehicles, tools, QR codes, checkouts, and trackers never feel like the same kind of record.
How Assets is organized
Inventory = what ChundR owns or manages. Field Accountability = where it is and who has it. Maintenance = what needs service and what was completed. History = protected changes and corrections.

1. Inventory

What the organization owns or manages
Start here when you need to find, add, identify, edit, assign, or attach a tracker to a machine, vehicle, tool, or access location.

2. Field Accountability

Where assets are and who is responsible for them
Use this area during the workday.
QR actions, open checkouts, today’s assigned gear, and tracker-connected locations answer the field questions: “Who has it?” and “Where should it be?”

Asset QR Actions

Scan once to open the correct workflow
A QR code is a shortcut—not a separate asset. Each code points to the correct ChundR action for that asset or location.

Checked Out Now

Shared equipment currently assigned to a person
These are open checkouts that remain the responsibility of the listed person until the equipment is returned.

Today’s Assigned Gear

The vehicle, access, and tools tied to today’s operation
Use this for the field-ready view. It avoids searching the full inventory when you only need the gear connected to today’s work.
Loading assigned truck…
Loading access points…
Loading tool locations…

3. Maintenance

What needs attention and what work was completed
Service status stays separate from asset identity.
An asset can still be active inventory while also being due for service. This section tracks the maintenance lifecycle without changing what the asset is.

Service Due

Overdue, due soon, or scheduled maintenance
ChundR compares service dates and meter targets so equipment needing attention is visible before it creates downtime.
Service & asset historyCompleted service • meter corrections • protected changes

Completed Service

Recent maintenance actually performed

Meter Corrections

Protected corrections to machine hours or vehicle mileage

Asset Record History

Protected inventory, assignment, and record changes
Operational Record
Understand today. Close it correctly. Learn from the pattern.
Records separates the current workday, closeout status, performance trends, forecasts, evidence, and protected history so each record has one clear purpose.
How Records is organized
Today = what happened in the current workday. Closeout = whether the day is complete and finalized. Performance = what finalized data says about pace and efficiency. Forecast = what current pace means for upcoming work. Evidence & History = photos, past work, and protected change records.

1. Today’s Record

What happened during the current operating day
Use this first when you need the current day’s production, staffing, machine use, truck mileage, weather, or other recorded field details.

Today’s Active Records

Crew-by-crew field records for today
Managers can see every crew record active today. Open any record for its full staffing, equipment, evidence, issue, inspection, and closeout story.

Focused Daily Record

The daily record currently driving this screen
Production—latest log
Team—staffing
Machine—usage
Truck—mileage

Recorded Field Details

Inputs captured for today
These are the underlying inputs for the focused daily record above. Use Today’s Active Records to open another crew’s operational story without confusing it with this focused record.

2. Day Closeout

Confirm the day is complete before it becomes final history
Finalizing locks in the operational record.
Use closeout to verify today’s information, finalize the day when complete, or reopen it when a legitimate correction is required.

Closeout Status

Current day status

Closeout Lifecycle

Protected record of finalization and reopening
3. PerformancePace • efficiency • trends • 7-day summary

Performance

What finalized work tells you about output and efficiency
Performance uses completed operational data—not unfinished daily entries.
Use these sections to compare pace, weather impact, labor efficiency, machine efficiency, project results, and recent trend direction.

Production Intelligence

Pace, weather impact, and efficiency
Clear / No Impact—avg ft/day
Weather Impacted—avg ft/day
Impacted Days—minor + major
Major Impact—days
Crew Efficiency—needs labor hours
Machine Efficiency—needs meter hours

Recent Performance Trend

How recent finalized results are moving
Recent Pace—finalized days
Pace Change—vs prior period
Goal Hit Trend—recent finalized days
Weather Cost—estimated lost production

Project Performance

Results by project from finalized days

7-Day Operations Summary

Automatic rollup of finalized work
Finalized Days—last 7 calendar days
Production—finalized work
Labor Hours—completed staffing
Machine Hours—recorded usage
4. ForecastScope + recent pace → planning outlook

Forecast

What current scope and pace suggest about upcoming work
Forecast is forward-looking.
It uses known scope and recent pace to estimate what may happen next. Forecasts are planning guidance, not completed production records.

Project Forecast

Estimated progress based on scope + pace
5. Evidence & HistoryPhotos • archive • protected changes

Evidence & Protected History

Proof of work and records of what changed

Photo Evidence

Before / after documentation
Use photos to verify field conditions, work completed, and before/after results without confusing images with production data.

Operational History Archive

Search finalized and open daily records
Find an older field day by date, project, work area, or crew. Open any result for its complete operational record.

Daily Record Changes

Protected history of edits to daily operational records
Use this when you need to verify what changed in a daily record, who changed it, and when.
6. Keeper RecognitionKeeper milestones • rewards • claims

Keeper Recognition

Keeper milestones and reward administration
Keeper recognition is stored here as a record, not mixed into professional production performance.
Keeper hours, milestones, available rewards, and claims remain visible without being mistaken for crew productivity metrics.

Keeper Rewards

Keeper hours, milestones, and available rewards
Loading Keeper progress…
Team Command
People, permissions, onboarding, and communication—each with a different job.
ChundR keeps the team connected while separating who someone is, what they can access, how they join, and how they receive operational messages.
How Team is organized
People = who is on the team and how to reach them. Roles & Access = what each person is allowed to see or manage. Invites = how a new user joins with the correct role. Messaging = operational outreach to opted-in people. Organization Settings = shared ChundR terminology and configuration.

1. People

Who is on the ChundR team

Team Directory

People, roles, and field contact information
Your ChundR team
Use the directory to identify managers, Keeper Managers, Team Leads, crew, and Keepers and quickly find the right person for field coordination.

My Profile

Your own ChundR identity and role
Loading your ChundR profile…

Team Members

Current people in this ChundR organization

2. Roles & Access

What people are allowed to see and manage
Role is not the same thing as a contact record.
Permissions control the ChundR experience. Managers see the full operation. Keeper Managers stay focused on volunteer operations. Team Leads see assigned execution. Crew and Keepers receive the field visibility appropriate to their role.

4. Messaging

Reach opted-in people without maintaining a separate contact list
Email outreach and SMS serve different purposes.
Use outreach for planned Trail Days, announcements, and newsletters. Use field messaging for immediate operational texts such as meeting points, work changes, safety updates, and crew reminders.

My SMS Consent

Your personal opt-in or opt-out setting
ChundR work texts
Checking preference…
This controls only your own ChundR operational text consent. By opting in, you agree to receive operational ChundR text messages from Bentonville Trailblazers. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help. Privacy Policy • SMS Terms

5. Organization Settings

Shared ChundR terminology and organization configuration
Organization settings affect ChundR as a whole.
This is not an individual user profile. Use it for organization-wide terminology, industry context, and shared configuration.

Organization Profile

Shared terminology and industry settings
Loading organization profile…

6. Protected Team History

Who changed team records and when

Team Directory Changes

Protected record of team and role updates
Use this when you need to verify changes to team records, roles, or directory information. It is history—not the current directory.
Field Map
Know where you are. See what matters nearby. Act on the field.
The map connects trail coverage, assigned work, issue reports, access, assets, trackers, and field locations in one geographic view.
How the map works
Navigate = find your work area, trails, and directions. Report = drop a field issue at the exact location. Layers = choose which operational information is visible. On Trail Mode = use your live position to alert you when you approach a reported issue.

1. Current Map

Your active geographic work view

2. Map Layers

Choose what operational context is visible
Layers do not create new records. They only show or hide existing trail, work, issue, access, asset, and field-location information on the map.
Map location not set yet
Set or select a work location to activate the map, directions, nearby context, and location-based issue reporting.
Notifications
Operational Inbox
Only the things that need awareness, action, or review. Routine hours, miles, and progress stay in the EOD.

Needs Action

Checking live alerts…
Loading notifications…

Recent Updates

Meaningful changes without the noise
Loading recent activity…
Tool Drawer
Secondary tools, intentionally out of the way.
More keeps the main field navigation focused. Open this area when you need administration, records, assets, people, or guidance rather than today’s core field workflow.

Field Tools

Available to every ChundR user

Pilot Feedback

Capture it where it happens
Found a bug or have an idea?
Send it directly into ChundR with your current role and screen attached automatically.
PILOT

Staff Tools

Administration, records, people, and support
Open a tool for a specific job.
Assets manages what the organization owns. Records stores operational history and intelligence. Team manages people, permissions, onboarding, and messaging. Guides contains training, field playbooks, and presentation support.
ChundR Field Tools
Measure it. Calculate it. Build it.
Fast field math built into the job. Core calculations run on-device, so the math still works without cell service.
Field context will appear when a project or daily log is active.
Tool Navigator
Get to the right tool fast.
Favorites and recent tools stay first.
Organization Field DefaultsMaterial allowance • truck capacity
Saved per organization on this device.
Grade / Slope

Rise + Run

Enter vertical change and horizontal run. ChundR returns percent grade, angle, ratio, and rise per 100 ft.
Phone Measure

Measure Grade / Angle

Place the phone lengthwise on a straightedge or trail surface, then measure. ChundR averages sensor readings to reduce hand shake.
Sensor idle
Field measurement only. Verify feature geometry, structures, and drainage requirements before construction.
Quick Convert

Length Conversion

Convert common field dimensions without leaving ChundR.
Area / Volume

Trail Section Volume

Calculate surface area and material volume from length, width, and average depth.
Materials

Material Order Estimate

Turn calculated volume into an order quantity with compaction/waste allowance and optional truck-load planning.
%
yd³/load
Allowance is a planning factor, not a fixed engineering value. Adjust for compaction, waste, moisture, and supplier practices.
Excavation

Cut / Fill Estimate

Estimate excavated or placed material from a rectangular average section. Use average depth across the work zone.
Drainage

Culvert / Drain Fall

Enter the horizontal run and measured drop from inlet to outlet. ChundR returns drainage slope in percent and degrees.
Positive values mean the outlet is lower than the inlet. A negative result indicates backfall.
Drainage Planning

Required Drop

Know the run and target slope? ChundR calculates the vertical drop needed between inlet and outlet.
%
This is a field geometry calculation, not culvert sizing or hydraulic engineering. Verify design requirements and site conditions before construction.
Jump Planning

Idealized Flight Geometry

Explore how speed, takeoff angle, and landing elevation affect idealized projectile travel.
degrees
Idealized physics only. This does not model rider input, suspension, lip shape, drag, wheel path, landing transition, or construction tolerances. Do not treat it as a safety certification.
Berm Planning

Speed + Radius

Estimate the idealized frictionless bank angle associated with a speed and turn radius.
Planning reference only. Real berm design depends on tread width, soil, traction, rider line, transition shape, drainage, and site constraints.
Bridge Builder

Decking + Material Count

Estimate deck area and board count for a simple rectangular trail bridge deck.
%
Decking estimate only. Structural sizing, span, stringers, foundations, fasteners, railing, live load, and local code require project-specific design.
Conversions

Field Unit Toolbox

Convert length, area, volume, speed, and grade without leaving the field screen.
Ask ChundR

Describe the field math

Type a plain-language calculation. ChundR handles common field math locally before any AI is needed.
Understands common requests for volume/material quantity, grade from rise/run, required drainage drop, and unit conversion. If a request is ambiguous, ChundR tells you exactly what information is missing.
Saved in the Field

Recent Calculations

Results stay on this device immediately. When attached to an active EOD, they also become part of the daily project record.
No field calculations saved yet.
ChundR Smart Builder
BETA
See what the terrain could become.
Capture a real field zone, explore a build concept, and move the best idea into ChundR's approval workflow without touching live work until it is intentionally approved.
1Capture2Explore3Pitch4Build
Concept first. Approval second.
Keepers and Crew can pitch field ideas up for review. Managers and Leads can pitch concepts back down to field teams.

1. Capture the Zone

Camera or photo library
📷
Capture the actual ground.
Use a clear, wide field photo that shows the trail line, slope, drainage path, or structure area you are considering.
No photo selected yet
Location optional • no location saved yet

2. Measure the Ground

Bubble level + angle tool
Field Level
Measure slope, culvert fall, and feature angles.
Lay the phone flat on the surface or align the long edge with the direction you are measuring. For culverts, point the top of the phone toward the intended outlet.
OFF
Long-axis angle0.0°
Awaiting sensor
Side-to-side0.0°
Cross slope
Positive/negative sign follows the phone-top direction. Use Zero Here when you want relative angle from an existing surface.

3. Describe What You See in Your Head

Your idea + this terrain = the design brief
How should ChundR think?
Describe your idea
Constraints / must keep
GPT-5.6 Sol reads the terrain and design brief • GPT-Image-2 creates the visual concept

Recent Smart Builds

Reuse a brief without starting over
No recent concepts yetCompleted Smart Builds will appear here on this device.

Idea Exchange

Ideas shared with you and ideas you sent
No ideas loaded yetOpen Smart Builder to load the current exchange.
Field check required
Photo-based concepts cannot confirm exact grade, soil structure, hydrology, utilities, property boundaries, bridge loading, permitting, or structural requirements. Use Smart Builder to generate ideas, then verify the site before construction.
Keeper Field Guides
Guidance for the work in front of you.
Keeper Guides contains volunteer field support only. Presentation tools, pilot administration, and organization-wide configuration remain outside the Keeper experience.

Recommended Guide

Most relevant guidance for the current context
ChundR will surface the most relevant Keeper field guide.

Keeper Playbooks

Reusable volunteer field guidance
Use these playbooks to brief volunteers, handle common Trail Day situations, and keep work consistent across different locations and leaders.
Guides & Training
Learn the system. Run the field. Present the product.
This area contains reference and support tools—not live operational records. Use it for presentation readiness, onboarding, field playbooks, and pilot feedback review.
How Guides is organized
Presentation = safely demonstrate ChundR. Training = teach someone how to use the app. Playbooks = field guidance for real work. Pilot Feedback = review friction reported by testers.

1. Presentation

Show ChundR without risking production data

Friday Presentation

September 18 • readiness and safe demo mode
Presentation Readiness Check
Run this before the meeting to verify the screens and capabilities you plan to demonstrate.
CHECK
Checking presentation device capabilities…
Presentation Mode is read-only: live write actions are temporarily locked so an accidental tap cannot change, assign, text, finalize, or delete production data.

Live Presentation Q&A

AI-assisted executive answers during the demo
Use ChatGPT for audience questions about ChundR.
The prepared context supports concise answers about security, roles, mapping, offline use, rollout, integrations, commercialization, and technical architecture.
READY
Open ChatGPT
Presentation workflow: audience asks → repeat the question → dictate or paste it into ChatGPT → answer with ChundR-specific context.

2. Training

Teach the ChundR workflow without using presentation mode
Guided Walkthrough
Use the in-app training tour for onboarding and product education. It explains the workflow without turning on the protected Friday presentation experience.

3. Field Playbooks

Reference guidance for real trail operations

Recommended Playbook

Most relevant guide for the current context
ChundR will recommend a field guide based on current conditions.

Crew Playbooks

Reusable field guidance
Use playbooks for consistent field decisions, training, and reference. They guide work; they do not create or change operational records by themselves.
ChundR V1 • authenticated live pilot