We take your Google Forms, Sheets and Apps Script prototype for the Rotary District 5170 Youth Speech Contest, harden it, install it, test it hard and hand it to your committee. It stays on free Google tools, so running it costs $0 a year.
Two projects we delivered that are close to this one. Both clients recorded a video review for us.
Built for Moolah Fundraising
A custom fundraising platform that replaced PledgeDrive. It has roster upload with admin approval, online payments through Stripe, role-based access and reporting for each organization. That is the same shape as your registration, approval and tracking workflow. It is a custom React and Node.js build rather than Apps Script, and we still maintain it.
myroster.co
A project we delivered for MyRoster. Their own video review tells you what it was like to work with us.
We read your developer brief, the Apps Script code (about 750 lines), the landing page, the test guide and the setup guide. The prototype is well organised and matches the brief closely, so we are comfortable taking it to production.
The brief says the prototype has been checked with simulated data but not run end to end in a live Google account. We have read the code and have not run it. Our first step is a full live run in your test account. If that turns up work beyond this proposal, we tell you before spending the time.
Our first guess in chat was 30 to 40 hours. After reading Section 9 the job is bigger than hardening: 14 launch-blocking items, two installs, browser testing, a handover call and 30 days of support. The estimate also includes our QA engineer's independent testing, which you asked for. That is why it is now 80 to 100 hours across the team.
This follows Section 8 of your brief.
Assumes we start the week of Oct 12. If the start moves, the dates move by the same amount.
Run the prototype live in your test account and fix what turns up
Build the 14 Must items and our additions
Independent QA: volume, email limit and device testing
Production install, DACdb page and browser checks
Handover call and one-page how-to (target Fri Oct 30)
Buffer before your early-November outreach push
30 days of bug-fix support, counted from launch
We are an agency. Our development team is based in Pakistan, so your morning (Pacific) is our evening.
Builds the system and owns the technical decisions.
Tests independently of the builder, with the volume and edge-case runs you asked for.
Takes your calls and is your point of contact through launch and support.
14 Must items block launch. 7 Should items are wanted. 2 are already handled. Where we suggest a change to your list, it is marked.
Before each send, the script checks how many emails are left for the day. What does not fit is queued and goes out the next morning, parent consent emails first. The row shows "Email queued", and one failed email never stops the others.
The form asks for a personal email, and known school domains are flagged.
A "Confirm parent email" field must match. We also scan the contest inbox for bounced mail and flag the row.
A warm-up and send-volume plan before launch, and advice on Google Workspace for Nonprofits if it is needed.
Any failure sends the committee a clear alert and is logged on a visible "Errors" tab.
A likely duplicate (same student name and parent email, or same student email) is marked and the second parent email is skipped. The committee resolves it.
Each child already gets their own row, code and link. The email and form will name the child prominently and say each child needs their own signature.
A nightly check makes sure every form response has a Tracker row. Missing rows are created or flagged.
We match questions by their internal ID instead of their title, so a rename cannot break anything. If a question goes missing, the committee gets an alert that names it.
A "Withdrawn" status stops all emails for that row.
The row is flagged for committee review. Registration is not blocked.
Flagged for review, since the student may have signed for the parent.
We check date of birth against the club's contest date, or the latest club contest date if the student is not placed yet. We ask for date of birth only from students who say they are 18 or older, so we collect less data from minors with the same protection.
No change. Unknown codes alert the committee. Anyone with the link can sign, which is an accepted risk.
A Spanish version of the parent email and permission form, priced separately (see Price and terms).
Every row in a multi-row edit is processed, or the edit is blocked with a visible note.
The student, the new chair and the old chair are all emailed.
Columns are found by header name, and the header row is protected.
Key tabs are protected, and the script fails with a clear message.
The form's club dropdown refreshes whenever the club sheet changes. If a club is not on the form yet, the page falls back gracefully.
Names are encoded and trimmed the same way everywhere, and tested with names like these.
Several addresses separated by commas or semicolons all work. Blank or invalid chair emails are flagged to the committee.
No change. The page shows a message and Register still works.
What we would change in your list, and what we found that it does not cover.
You asked for testing with a meaningful amount of data, by someone other than the developer.
Reply in our Upwork chat or bring them to the call.