Volunteer Shift with ASP.NET Core: A 2027 Project Guide

The starting point for this ASP.NET Core exercise is a volunteer coordinator working with shift records. Their question is specific: How many completed volunteer hours belong to each activity? Building a typed web endpoint around that question gives the project a manageable scope and makes the result possible to verify.

This is a 2027 study-edition project brief. All example records and operational situations are fictional. Start with basic ASP.NET Core knowledge, the ability to inspect structured data and a local practice environment. The complete first version should answer the stated question before adding accounts, real integrations or additional screens.

Define the project rule

Completed shift hours represent recorded participation in this exercise. A cancelled shift cannot contribute hours, and fractional hours must use an agreed precision. For this exercise, one row represents one shift. The stable key is record_id; activity_name is the grouping or filtering label. The numeric shift_hours field uses hours. Accepted states are planned, completed, cancelled.

The summary selects status completed and applies sum to the selected numeric values. Keep this definition visible in the interface, response or report so another learner can reproduce it. Use positive finite values in the starter fixture and define any future zero or missing-value policy explicitly.

Choose the ASP.NET Core approach

Use a dedicated request model and validate it before calling the domain service. Keep transport concerns separate from the calculation so tests can call the service directly. Document dependency lifetimes and avoid sharing mutable request data across users. Return structured errors that are useful to a client without exposing internal configuration.

The three design decisions to explain in your project notes are:

• Request and domain model separation. Apply this choice to shift records and explain its effect on shift_hours.
• Dependency ownership. Apply this choice to shift records and explain its effect on shift_hours.
• Structured validation responses. Apply this choice to shift records and explain its effect on shift_hours.

Work through a small sample

The three records below are deliberately small enough to inspect by hand. They are a compact specification for the data shape and expected result, and can later be expanded into a larger synthetic fixture.

[
  {
    "record_id": "volunteer-shifts-01",
    "activity_name": "Welcome Desk",
    "shift_hours": 1.5,
    "status": "completed",
    "recorded_on": "2027-01-04"
  },
  {
    "record_id": "volunteer-shifts-02",
    "activity_name": "Project Showcase",
    "shift_hours": 2.0,
    "status": "planned",
    "recorded_on": "2027-01-05"
  },
  {
    "record_id": "volunteer-shifts-03",
    "activity_name": "Library Help",
    "shift_hours": 0.5,
    "status": "completed",
    "recorded_on": "2027-01-06"
  }
]

Only the first and third records match completed. Their shift_hours values are 1.5 and 0.5; the full-fixture result is 2 hours, with 2 matching records. Selecting activity_name = Welcome Desk leaves the first record, so the result becomes 1.5 hours, with 1 match. This provides two independent checks for the filter and aggregation.

The full-fixture output contract is:

{
  "matching_count": 2,
  "operation": "sum",
  "value": 2.0,
  "unit": "hours"
}

Check the result by activity_name

The overall figure answers the all-records version of the question. Grouping by activity_name produces the following separate expectations, using the same completed rule. The middle group has a record in the source fixture but no qualifying observation.

Use this breakdown when answering the group-level question. Compare like-for-like units and keep the matching count visible, especially for averages. A different filter changes which records enter the calculation; it does not change the meaning of the metric.

The code blocks describe sample data and an expected result. Implement the surrounding feature using the installed version of your chosen tools, then save the actual run evidence separately from these expectations.

Build the feature in three passes

1. Describe the request contract

Define a read operation for the shift collection and an optional activity_name filter. Document accepted status values and the positive numeric shift_hours field. Decide how the client receives validation details before implementing a write operation.

2. Place the rule in a service

Calculate the sum for completed records inside a request-independent function. Keep persistence access separate. Return a count, value and hours label so a consumer can distinguish an empty set from an actual measured result.

3. Verify the stored outcome

Start with the fixture, execute one controlled change, and read it back. A rejected update must leave the collection unchanged. If the application uses memory only, document its restart behaviour instead of implying that the data is durable.

Find the mistake before polishing the result

A useful defect to introduce deliberately is: A rounded display value is reused as the stored quantity. First reproduce it against the fixture, then identify the smallest rule or state transition that explains the mismatch. Fix that boundary and rerun the full-fixture and selected-label examples. This creates a stronger explanation than changing several unrelated parts until the screen looks right.

The scenario-specific acceptance check is: Sum unrounded values and round only the final presentation. Preserve before-and-after evidence. Add a missing activity_name, a negative shift_hours, an unrecognised status and a duplicate record_id as separate invalid cases. Define the rejection or duplicate-handling policy before testing, and verify that invalid input does not silently change valid existing records.

Check the ASP.NET Core concerns as well:

• A failed request must leave stored state unchanged.
• Two requests must not share mutable input.
• A response must serialize the agreed field names.

For an empty filter match, the expected sum value is 0. Keep matching_count at zero. This distinction prevents an empty dataset from being interpreted as a measured observation.

Explain the finished work in a portfolio

Show the volunteer coordinator question, the record definition and the expected calculation first. Then demonstrate a activity_name filter and the acceptance check. Include the fixture, setup instructions, chosen tool versions, actual test output and one remaining limitation in the repository. If you show a screenshot, pair it with the input that produced it. Another learner should be able to repeat the same result from a clean checkout.

For a focused extension, add a second activity_name selection and compare the two groups using the same rule. Specify how missing groups appear and keep the original fixture as a regression case. Expand scope only after the current calculation, state handling and recovery path remain understandable.

Questions learners often ask

Which shift records belong in the result?

Select records whose status is exactly completed and that satisfy the chosen activity_name filter. Other states remain in the source data and can have separate summaries. Follow the domain rule above when a record changes state.

What should happen when no records match?

Return a zero total with a matching count of zero and a clear empty-result message. Keep the applied filter visible so the user can change it. Avoid using a loading indicator for a completed request that simply has no matching data.

How can I prove the shift_hours result is correct?

Reconcile the first and third sample records, then repeat the calculation for Welcome Desk alone. Save both expected and actual outputs, and rerun the scenario-specific acceptance check after making a change.

Continue learning with Groot Academy

Use this exercise as a concrete discussion point when choosing a learning path. Browse the current Groot Academy course directory and ask about the current syllabus, learning mode and project practice. Course availability and batch details should be confirmed directly with the academy.

For implementation details, consult the official ASP.NET Core documentation matching the tools you install. This project defines an original practice brief; it does not depend on a forecast about 2027 software releases.

Continue with Lost and Found Register using ASP.NET Core, or compare Volunteer Shift using MERN Stack. These companion practice guides are part of the 2027 learning collection.