labs@atheron:~/industries/associations/rescue$ recover --codebase --modernise

Grievance rescue

Old case files, moved and made safe.

Many unions and associations depend on a database a staff member built long ago, on one computer, with deadlines kept elsewhere. We review it first and tell you plainly what we find, then move every record into a system that warns before deadlines pass and keeps each case private.

Start a project See the example projects

// what matters here

What is different in this industry.

A review before the build

A short look at the old system and how you use it, with a plain recommendation.

Every case moved and counted

Records checked with your staff, with any differences shown before the old system is retired.

Deadlines from your agreement

Each step's time limit set from the agreement, with warnings before it passes.

Private by role

Stewards see their own cases, staff see all of them, and every view of a file is logged.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb app

Grievance case files, rebuilt

Hypothetical. Not a client, not a result.

// The problem

A union tracks grievances in an old Access database on one staff computer, with deadlines in a paper diary, and nobody is sure every step was filed in time.

// What we would build

We begin with a short review of the old database and how cases move through it. Then we move every case into a web app where each grievance has its steps, deadlines from your agreement, documents and notes, stewards see their own cases, and staff are warned before a deadline passes.

// What is in it

A review of the old database and a plain plan before we build
Every past case moved in and checked with your staff
Steps and deadlines set from your agreement, with warnings
Documents and notes kept with each case
Stewards see their own cases; staff see all of them

// Stack

Next.js
PostgreSQL
Access import
DigitalOcean Toronto

// estimate

Build: ≈ US$70,300 to US$108,000, delivered within 17 weeksCAD 100,100 to 153,100
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.9 to 4.9 weeks
Core features: 2.4 to 3.9 weeks
Full build: 1.4 to 2.4 weeks
Testing and fixes: 0.9 weeks
Moved records checked with your staff: 0.9 weeks
Launch: 0.9 to 1.4 weeks

How it is paid

Deposit 20%: CAD 20,020 to 30,620
Discovery 6.8%: CAD 6,806.80 to 10,410.80
Design approved 6.8%: CAD 6,806.80 to 10,410.80
Core features 20.4%: CAD 20,420.40 to 31,232.40
Full build 13.6%: CAD 13,613.60 to 20,821.60
Testing and fixes 6.8%: CAD 6,806.80 to 10,410.80
Moved records checked with your staff 8.7%: CAD 8,708.70 to 13,319.70
Launch 6.9%: CAD 6,906.90 to 10,563.90
Holdback, 30 days after launch (10%): CAD 10,010 to 15,310

Start from this example

// questions

Questions we get about this.

Our grievance database runs on FoxPro. Can you still read it?

Usually. FoxPro, Access, FileMaker and spreadsheets can be read directly. We check a copy of yours before we quote.

Can we keep using the old grievance system during the move?

Yes. It stays in use until the new one is checked, then it is kept read-only for as long as you want.

Does the case system decide deadlines under our agreement?

No. Your staff set each step's time limit from the agreement; the system tracks them and warns.

Back to the industry: Associations, unions and membership organisations About the service: Rescue and modernization

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call