Erica Monton

Erica Monton smiling, in a pink gingham photo frame decorated with a butterfly, bows and tulips

I am Erica Monton, a computer science student who is passionate about biology, data science and research. I am eager to gain experience in the field of biotechnology.

I approach every project with a problem-solving mindset, using existing algorithms to transform difficult problems into solvable ones.

My goal is to master my skills in data science and programming and excel in the field of bioinformatics.

Relevant skills

Python · C++ · Google Colab · Jupyter Notebook

Bioinformatics
Biology
DATA
SCIENCE
Algorithms
Programming
Research
tap a skill, drag the stickers, tap the envelope to close it

Software and Skills

Projects

Askademic

A campus-based system that allows student to instructor appoint consultation.

Tech Stack used: React + JSX build + vite + Supabase DB + lucide react + vercel

Tugma

A community-based lost and found system that allows automatic matching of item reports using Levenshtein algorithm and rule-based algorithm.

Tech Stack used: HTML + CSS + Vanilla JS + Node.JS + Supabase
Case Studies

Projects and case studies

case study

Askademic

A web system where students request consultation slots, instructors approve them and record what happened, and the department can review how consultations go.

Askademic on a laptop
Askademic on a phone
Askademic app logo

Move your pointer over the devices to tilt them. Pick a tab to change the screen.

Overview

The product
Askademic is a web-based consultation system designed for college students to request appointment slots with faculty members. Instructors can approve requests and document the consultation details, while program chairs and department deans review student feedback and ratings. Overall, the platform streamlines student-instructor communication and enhances the consultation experience.
Duration
February 2026 to November 2026
Users
Students, instructors, program chairs, and department deans.

The problem

Students can’t tell when an instructor is really available, instructors have no record of consultations that happened or didn’t, and the department has no evidence of how consultations go.

The goal

Make booking clear, close every consultation with a recorded outcome, and give the department a fair basis for evaluating instructors.

My role

Project lead, documentation lead, and design assistance.

  • Assigned tasks to team members efficiently.
  • Monitored progress to ensure all standards and deliverables were met.
  • Led and guided the team across the project duration.
At our final defense the panel returned 13 critiques, and a follow-up round added more. Much of this case study is about how that feedback reshaped the system.

What the team covered

  • User research: a survey and interviews with faculty members and students.
  • Role design: the student, instructor, program chair and department dean views.
  • Design: a first prototype, a revision round, and a refined, deployed system.
  • Documentation: use cases, class, sequence and state diagrams.

Design thinking process

We followed the five stages of design thinking. Pick a stage to see what we did there, what we found, and the decisions it led to.

Understanding the users

User research: summary

The team already assumed that our target users experienced the problem. To check, we ran a survey and interviews with the college’s faculty members and students. Once we had the data, the assumption became a confirmed hypothesis.

User research: pain points

1

Unclear availability for students

Students can’t tell when an instructor is actually free, so they chase them through chat or the faculty room and often find no one there. Every screen shows real, bookable slots and clear request statuses, so a student never has to guess.

2

Part-time instructors who can’t maintain a calendar

Part-timers have little time to update their availability every day, which leaves schedules outdated and students distrustful of the system. Setting availability is quick and recurring by default, with the department’s blocked dates applied automatically so instructors only handle exceptions.

3

No record of whether a consultation happened

Without an outcome, the department has no evidence of how consultations go, and a no-show looks the same as a held session. Every appointment ends in a recorded outcome (“Closed · Held” or “Closed · No-show”), so nothing is left ambiguous.

4

Leaders who are also instructors

Program chairs and the department dean teach too, so one account has to act as both a manager and an instructor without conflicts of interest. A role switcher separates the two views, and ratings of a chair or the department dean route to the next level up.

Personas

User journey maps

We mapped one journey for each side of the booking. The curve is a rough guess of how the person feels at each step, and the last line of each step is the opportunity we turned into a feature.

The first design

This was our first prototype, then called FACS (Faculty Appointment and Consultation System). It had the full student booking flow, and it is what the final defense panel reviewed. Tap a screen to enlarge it.

Faculty directoryStudents see every instructor, when they are next available, and a Book button.
Request appointmentA seven-day picker shows how many slots are left each day.
My appointmentsA table of every request with a status badge and filters.
Appointment detailsPending requests can be rescheduled or cancelled until they start.
Declined with a reasonThe instructor’s reason and time of decision are shown to the student.
Instructor notificationsNew requests, cancellations and waiting responses in one place.

Usability study: findings

We didn’t run lab sessions. Our usability studies were two rounds of review by the people who would judge and use the system: the final defense panel on May 8, 2026, and a follow-up from the faculty representative. Each round gave us concrete findings about how the design worked for real roles.

Round 1: final defense panel

1

Several students can want the same last slot. Students can now request it, and once the instructor approves one, the others are cancelled automatically.

2

A no-show had no way to end a record. Instructors can mark “No-show,” and “Completed” became “Closed” so it matches the remark chosen.

3

The hierarchy wasn’t clear. Program chairs were view-only and the department dean’s role was missing, so we built interfaces for both.

Round 2: faculty representative

1

Availability should be trackable per day. The calendar now works like a familiar month view, with appointment counts per day and long names shortened with an ellipsis.

2

A no-show needs a required note and clearer features. The no-show flow is being tightened so the outcome is obvious to everyone.

3

Records need limits and a way out. Chairs and the department dean get Reports, and history limits and export are being finalized.

Smaller findings were fixed too: a blurred background behind dialogs, a subtle wave background, and a calmer, more polished sign in.

From prototype to final

After the revision round we refined the look and the logic. Each row puts the first design next to the system we deployed, with what changed and why.

Sign in

Prototype
Final
  • The Student and Faculty switch is gone. One form reads the account and shows a “Student account” or “Faculty account” badge.
  • One field for ID or email, a password reveal, and a Terms link in the footer.
  • A softer card on a calm background, so the logo and the form get the focus.

Welcome

Prototype
Final
  • Same four-step guide and policies, with larger type and more space so they are easier to read.
  • The sidebar gained About and Terms & Policy, and Log Out is red to set it apart.
  • The signed-in student is shown with initials and program, and the bell shows an unread count.

Student dashboard

Prototype
Final
  • A new “Faculty you can consult today” row answers the first pain point directly: who is available, right now.
  • Empty states say what to do next, with a “Book one now” button.
  • The weekly strip starts from today, and the next consultation card keeps its place at the top.

Instructor calendar

Prototype
Final
  • Institution-closed dates are shaded automatically, so part-time instructors don’t block them one by one.
  • An activity panel counts Approved, Pending, Declined, Closed, Cancelled and Follow-up. “Closed” replaced “Completed” after the no-show question.
  • Month navigation, a Today button, and past days dimmed so the future stands out.

Final screens

More screens from the deployed system, plus the review views for program chairs and department deans. Tap to enlarge.

Faculty sign inThe badge changes to “Faculty account” as soon as the email is recognized.
RequestsFilter by pending, approved or history, and search by student, topic or note.

Roles beyond the student and instructor

The student rates the consultation, and the program chair and department dean review the results.

Faculty evaluationAfter a held consultation, the student rates four areas from 1 to 5 and can add a comment.
Program chair viewCounts for one program, with tabs for appointments, reports, ratings and feedback.
Department dean overviewSystem-wide counts, filters by program, and a ratings tab that flags items needing attention.
Account managementEvery user in one table, with role, status, join date and request count.

Accessibility considerations

Not color alone

Status badges and calendar legends carry words as well as color: Pending, Approved, Closed, Declined, Follow-up. A color-blind user can still tell them apart.

Forms that guide

Every field has a visible label and an example, the active field gets a clear outline, and the password can be revealed so mistakes are easy to catch.

Readable and reachable

Dark navy text on light surfaces, generous spacing, and big touch targets. On phones, the navigation pairs each icon with a text label.

Takeaways and next steps

Impact

Askademic replaces chasing instructors with bookable slots and a recorded outcome for every consultation. Its dashboard already tracks 46 consultation requests across 8 faculty and 5 students, with 14 closed with a recorded outcome.

What I learned

Understand how an organization is structured before designing for it. We built an admin because it was a familiar pattern, but the panel’s question exposed that the real structure was a chain of review: instructor, program chair, then department dean. As project lead and documentation lead, I also learned that keeping the diagrams, the database and the screens in agreement matters as much as the screens themselves.

Next steps

Integrate Google Calendar
Students and instructors already plan their days in Google Calendar. Syncing approved consultations there would save part-time instructors from keeping a second calendar, and it answers the faculty representative’s call for a calendar they already know.
Deploy across the whole campus
Every department has the same problem of chasing instructors with no record of what happened. The system already supports roles, program views and school-wide closed dates, so it can grow beyond the CCS department.
case study

Tugma

A lost-and-found system where residents report an item, the system suggests likely matches, and barangay staff confirm them.

Tugma on a laptop
Tugma on a phone
Tugma app logo

Move your pointer over the devices to tilt them. Pick a tab to change the screen. All reports shown are simulated data from the study.

Overview

The product
Tugma is a web-based lost-and-found system for Barangay Sta. Rita in Olongapo City. Residents report a lost or found item through a form. The system compares every report with the others and ranks likely matches for barangay staff, who check them and confirm the right one.
Duration
August 2026 to November 2026
Users
Barangay staff, and residents who lost or found something.

The problem

Reports sit in a logbook or a chat thread, and matching is done by eye. A staff member has to remember what was reported weeks ago and hope the descriptions line up.

The goal

Keep every report in one place and rank possible matches by score, so staff check the best candidates first and can see why they were suggested.

My role

Researcher and developer.

  • Ran the needs assessment with barangay staff and residents.
  • Built and tested the matching logic against a simpler baseline.
  • Built the report form, the staff screens and the server behind them.
A fair question for any matching system is “why not use AI?” We chose rules staff can read, because they can see how every score is made up and can trust or overrule it.

What the work covered

  • Needs assessment: a survey of 10 barangay staff and 30 residents.
  • Matching logic: a weighted, rule-based score from 0 to 100.
  • Evaluation: 50 lost and 50 found simulated reports, compared as 2,500 pairs.
  • Interfaces and server: a resident report form and a staff area with sign in.
  • Acceptance: a technology acceptance survey with staff and residents.

Process

The project moved through five stages. Pick a stage to see what we did, what we found, and the decisions it led to.

Understanding the users

What we asked

We started from the assumption that matching lost and found items was slow. To check it, we surveyed 10 barangay staff and 30 residents. The survey asked how reports are recorded, how matches are found, and what each group would want from an online form.

Pain points

1

Reports live in different places

Nine of 10 staff record reports in a logbook, and one uses Facebook or messaging apps. Staff agreed that matches get missed because reports are in different places or formats. Tugma keeps every report in one list.

2

Matching is slow, or not done

Six of 10 staff said finding a possible match takes a day or more, and two said matching is not done. Tugma compares a new report with every other report straight away.

3

Words are hard to compare

All 10 staff rated this 4 or 5: describing an item in words makes it hard to tell whether two reports are about the same thing. Tugma scores each description word by word instead of asking a person to judge it by eye.

4

Many residents are left waiting

Of the 16 residents who had lost or found an item, seven had no match yet. Staff get a ranked shortlist, so the likeliest match is the first one they check.

Personas

These two personas are composites based on the survey answers. They are fictional people.

User journey maps

One journey for each side of a lost report. The curve is a rough guess of how the person feels at each step, and the last line of each step is the opportunity Tugma answers.

How matching works

Every pair of one lost and one found report gets a score from 0 to 100. The score is the sum of five parts, and each part has its own weight.

Scores are grouped into tiers so staff can scan quickly: High from 85, Medium from 70 to 84, and Low below 70. A score of 70 is the cutoff we used when we measured accuracy.

From a baseline to a better version

We first built a simple version (V1) to use as a baseline, then improved it (V2) and measured the difference.

V1 Baseline

  • Category and color must match exactly.
  • The whole description is compared as one string using Levenshtein distance, which counts the edits needed to turn one text into the other.
  • A different word order or a Filipino word for the same item lowers the score.

V2 Current

  • Descriptions are compared word by word, and a small typo still counts as the same word.
  • English and Filipino words are linked, so “pitaka” and “wallet” are treated as the same item.
  • Similar colors are grouped (“navy” counts as “blue”), and a found date cannot come before the lost date.

Results

We used 50 simulated lost reports and 50 simulated found reports, with 35 true pairs, which gives 2,500 possible pairs. We tuned the weights on 40 reports and kept the other 60 as a test set. The numbers below come from that test set at the 70 cutoff.

V1 baselineV2 current
Precision
51%
79%
Recall
90%
90%
F1 score
66%
84%
18 → 5wrong suggestions (false positives)
17 → 20of 21 lost items had the right match ranked first
0.90 → 0.98mean reciprocal rank of the true match

The difference holds up statistically: a Wilcoxon signed-rank test across 30 lost reports gave p = 0.018, with V2 making fewer errors on 10 reports and V1 on 2.

What I would not hide

Wider pools are harder

When each test lost report is compared with all 50 found reports, V2 precision falls to about 66% and it still makes 10 wrong suggestions. The result above is the cleaner setting, so I report both.

Simulated data

The reports were written for the study, so real reports may be messier. Recall did not improve either: V1 and V2 both missed 2 true pairs.

Did people accept it?

We used the Technology Acceptance Model on a 5-point scale. Staff rated usefulness 4.64, ease of use 4.40 and intention to use 4.75. Residents rated the system 4.23 overall, with ease of use the lowest of their scores at 3.96, so the resident form is where I would improve first.

Screens

Screens from the working system. The reports shown are simulated data from the study. Tap to enlarge.

Staff sign inOnly signed-in staff can open the records and the matches.
Report an itemOne form for lost and found, with category, color, description, place and date.
RecordsEvery report in one list that staff can filter.

Suggested matches

For any report, staff open a ranked list of candidates with a score, a tier and a breakdown of the five parts. They confirm a match only after checking it themselves.

Ranked candidatesThe highest score comes first, with a tier chip and a meter for each part.

On a phone

Sign in
Report
Records
Matches

Privacy and security

Lost-and-found reports include names and phone numbers, so the way the data is reached mattered as much as the matching.

Staff only

Names and contact numbers are shown only to signed-in barangay staff. Residents use the report form and never see other people’s reports.

Through the server

The browser talks to a small server on Vercel, and the server talks to the database. The database’s private key stays on the server, and the browser only holds the key used to sign in.

Honest about gaps

Some checks are still on my list, such as stricter database access rules and tests for injection and script attacks. I would finish these before any real deployment.

Takeaways and next steps

Impact

On the test set, the improved matching raised precision from 51% to 79% and F1 from 66% to 84%, without losing recall. Staff rated the system 4.64 for usefulness.

What I learned

A baseline is what makes an improvement believable. Building the simple version first let me show that the word-by-word rules were better, rather than only claim it. I also learned to report the weaker result next to the good one: the larger pool showed where the system still makes mistakes, and that is more useful than a single clean number.

Next steps

Test with real reports
The study used simulated reports. Running Tugma on real reports from the barangay would show how messy descriptions really are and which synonyms are missing.
Add photos and tighten security
A photo would help staff confirm a match, and I would finish the database access rules and the remaining security tests first.

Let’s connect

Open to learning opportunities, collaborations and sharing insights about scientific stuffs!

© erica monton