A progress matrix works when a team can see at a glance which file needs attention without losing the detail of individual steps. Put files on one axis and fixed sections on the other, and limit cell statuses to not started, in progress, submitted and not applicable.
The matrix is not management decoration. It needs to produce a work queue. If every cell contains a percentage, colour, icon and tooltip, interpreting it takes longer than opening the files. Start with a small set of status meanings and a clear link to detail.
Build the matrix on valid comparisons
Compare only published sections that apply to the file. Yindle Portal groups published questionnaires by category, counts excluded questions for each file and derives status from submissions and answers. A section that is entirely inapplicable gets its own ‘N/A’ status, not zero per cent.
Also define the sorting order. Category order and the order within each category need to follow the customer journey, not the date an administrator created a section.
Never let colour convey meaning alone
Use text or a symbol alongside colour so the matrix remains understandable with colour blindness or on a greyscale screen. Choose quiet shades for completed and not applicable; reserve strong emphasis for work that is actually blocking progress.
An ‘in progress’ cell can have several causes. The detail page needs to show which questions have been answered and what is still missing. Otherwise an employee may call the client without knowing where they are stuck.
Worked example: a fictional grant adviser
In a fictional scenario, consultancy GroenStap helps twenty business owners with a grant application. The columns are ‘company details’, ‘energy assessment’, ‘quote’ and ‘signature’. The energy assessment is not required for three small businesses.
The coordinator first sorts by the number of open sections and then by the next deadline. She sees that file F-014 has not started three sections and opens the detail view. File F-006 has one ‘N/A’ and is therefore not incorrectly counted as behind. The matrix directs focused investigation rather than an automatic conclusion.
Use an attention score outside the cell
Avoid twenty colours by calculating priority at row level. For example, use this simple decision sequence:
- Has an applicable deadline passed? Put it at the top.
- Is the deadline within seven days and something not started? Put it next.
- Has a submission arrived and is it awaiting internal review? Assign it to the team.
- Is progress being made with no imminent date? Use the normal order.
- Are all applicable sections complete? Move it to completed.
This score is an example, not a built-in Portal rule. Define time windows and responsibilities based on your process.
Test scale and exceptions
Do not populate a test matrix with five tidy files. Use at least fifty rows, long names, sections without questions, one client with several files and a file with many exclusions. Check horizontal scrolling, fixed headings, keyboard use and export needs.
Also set limits on reminders from the matrix. A single ‘remind everyone’ button is quick, but may reach people who have just asked for help or have a different agreement. Show the selection and reason before sending.
Above the matrix, show when the data was last calculated. With integrations, also indicate when a source is running behind. Without information about freshness, an employee may trust a green cell while the underlying submission has not yet been processed.
A second edge case is a change to the form. If you add a new required question halfway through the journey, previously submitted files may suddenly appear incomplete. Decide deliberately whether the new question applies only to future files, opens a new action or leaves existing submissions untouched. Do not present that choice as an ordinary fluctuation in progress.
Use the same definitions for exports as on screen. If ‘in progress’ is calculated differently in a spreadsheet, two work queues emerge. Prefer exporting the raw status, reference date and applicability to an unexplained percentage. Ask a team leader to trace five random rows back to their source files each month.
Explore Yindle Portal for the combination of files, choices and progress. The guide building a customer portal helps structure the underlying process agreements. To test a matrix with your actual columns, develop an anonymised example with Yindle.