Testing Tracking – KnightConnect Task Management

Table for Tracking Testing Process in Google Sheets

The following is a template for tracking your progress with members who have volunteered their valuable time to help you reach your goals of launching high quality and high value software. This tracker is not just a spreadsheet — it is your control center for managing the release candidate. Expanding from 6 testers to 20 or more means you cannot rely on memory, phone calls, or scattered notes. Professional software companies track every tester systematically, because perception matters: when testers feel that their feedback is valued, logged, and followed up on, they see you as a credible, disciplined company.

Use this table to record every stage of each tester’s journey: link sent, installation completed, first impressions shared, issues reported, and follow-up activity. Each row tells the story of one tester. By checking these boxes consistently, you’ll know at a glance who is engaged, who needs support, and where you stand with adoption.

Why it matters:

It reduces chaos and forgotten follow-ups.
It shows you care enough to be organized.
It allows you to measure progress, not just guess at it.
It positions you as leaders who run a structured, professional operation.

Fill this table in real-time as you communicate with testers. When a tester calls or emails, update their row immediately. This is how you will ensure no feedback is lost, no tester feels ignored, and your testing process builds both product quality and reputation.

Table Example

Member Name	Council #	Device / OS	Link Sent	Installed App	Initial Feedback Given	Issues Reported	Requests / Feedback / Questions	Follow-Up Needed	Last Contact Date	Notes
John Doe	1450	Android 13	✅	✅	✅	❌	Asked for easier login process	No	3/2/25	Needs help with screenshots
Jane Smith	2101	Android 12	✅	❌	❌	❌	—	Yes	3/1/25	Email follow-up sent

Why logging requests/feedback and questions matters:

It allows you to capture everything in one place (bugs, feature requests, usability questions).
It ensures testers feel heard and acknowledged, because their words are documented.
It creates a paper trail you can reference later when planning future releases.
It helps the CEO in conversations by having a record of what each tester said.

👉 In Google Sheets, you can make this column expandable (wrap text) so longer comments are easy to read.

Business Coach’s Cheat Sheet – Tester Follow-Ups

Coach’s Note: The goal of follow-ups is not only to gather feedback but also to show testers that their involvement is valued. Every touchpoint makes us look more professional and keeps testers engaged. Use these short, ready-made phrases to guide your conversations or emails at each stage.

1. After Sending the Link

Goal: Confirm they received it and encourage installation.

“Hi [Name], just checking that you received the download link. Once you’ve installed it, I’d love to hear your first impressions.”
“We know this isn’t the standard Play Store install, but we wanted to give you early access. Let us know if you run into any issues with the install process.”

2. After Installation (but before feedback)

Goal: Acknowledge progress and nudge them to try the app.

“Great to see you’ve got the app installed. When you have a chance, try a few features and let us know what stands out.”
“Even a quick first impression — what you liked or what felt confusing — is helpful to us.”

3. After First Feedback

Goal: Thank them and show that their voice matters.

“Thanks for sharing that feedback — it helps us strengthen the app for everyone.”
“We’ve logged your comments into our system so nothing gets lost. We’ll address issues and consider your ideas for future releases.”

4. After Issues Reported

Goal: Appreciate their report and set expectations.

“We appreciate you pointing that out. We’re focused on fixing bugs first, and your report helps us prioritize.”
“New feature ideas are logged for future releases — right now we’re in stabilization mode. That said, your input is valuable for shaping what comes next.”

5. If They Haven’t Installed Yet

Goal: Keep the relationship warm without pressure.

“Just following up to see if you’ve had a chance to install the app yet. No rush, we just don’t want you to miss the chance to be part of this early test group.”
“If you ran into any trouble with the download, let me know — we have a few quick tips that usually solve it.”

6. General Appreciation / Keeping Momentum

Goal: Reinforce their importance to the process.

“Your participation really helps us improve. You’re shaping the final version alongside us.”
“Thanks again for being one of the first to test this — your involvement will make a big difference when we go public.”

Reminders:

Always log their feedback into the tracking system immediately after each conversation.
Keep the tone positive and appreciative.
Never promise immediate features; instead, say:
- “That’s a great idea. We’ve logged it, and it will be considered for a future release.”
- “Right now we’re stabilizing version 1.0, but feedback like this helps guide where we go next.”

Testing Tracking Spreadsheet

Mobile App Testers

Initial link was sent Tuesday, Sep 16, 2025

Member Name	Council	Device / OS	Link Sent	Installed App	Initial Feedback Given	Issues Reported	Requests Feedback Questions	Follow-Up Needed	Last Contact Date	Notes
Carlos Mendez		Android 13								Developer
Jorge Ruiz	8157	Android 11	✅	✅	✅	✅				Co-Developer
Marc Evans	8157	Android	✅	✅	✅	✅	Could not add event to calendar	Yes	9/18/25	Google Calendar
Paul Ryan	8157	Android	✅	✅	Will provide feedback	❌		No	9/19/25	Sent messages
Allen Reitmeier	8157	Android	✅	✅ Jorge helped	✅	✅	Profile picture	Yes	9/17/25
T.J. Knight	11862	Android	✅	✅	✅	✅	Events Calendar	Yes	9/17/25	Updated event online, got kicked out of app when he clicks the event
Mike Fitzgerald	8157	Android	✅	✅	❌			Yes	9/16/25
Phil Holifield	8157	Android	✅					Yes	9/26/25
Juan Espinosa	8157	Android	✅					Yes	9/26/25
Joe Eubank	8157	Android	✅					Yes	9/26/25
Miguel Huizar	8157	Android	✅					Yes	9/26/25