The sign-in and supplier-record features are built and have passed initial tests. Online testing and final approval are still ahead.
Page updated
Sign in and save supplier records
Initial tests passed. Online testing and final approval are still needed.
Build customer questionnaires
Starts after sign-in and saved supplier records receive final approval.
Update account permissions
The hosting account owner must allow the team to set up the app’s secure online connection.
Project plan agreed. Initial tests passed; online testing is still ahead.
Six stages, 31 development tasks. Open a stage for details and estimated effort; items marked Planned are not yet available.
An invited customer can use a code sent by email to sign in, add a supplier and return later to their saved information.
Estimated effort: Large. Adds sign-in, saved records and protected access for invited users.
Customers can start with a template or a blank form, edit their questions, and preview the questionnaire before sending it.
Estimated effort: Large. Adds several question types and a way to check the questionnaire before sending it.
Customers can invite their team and decide who can manage settings, run day-to-day work, or only view information.
Estimated effort: Medium. Adds team invitations and controls for changing or removing access.
Customers can keep one record for a supplier company and separate records for its locations. They can choose whether a request covers the whole company or a specific location.
Estimated effort: Medium. Adds separate company and location records.
Customers can turn Word documents, Excel or CSV spreadsheets, and PDFs with selectable text into questionnaires they can review and edit.
Estimated effort: Large. Handles several file types and keeps useful results if a file cannot be fully read.
Customers can turn scans, photos, screenshots and handwriting into questions, then check and correct the results.
Estimated effort: Large. Reads scans, photos and handwriting, then lets a person correct uncertain results.
Customers can bring in a supplier list, review missing details or possible duplicates, and confirm the additions together.
Estimated effort: Medium. Adds list review, duplicate checks and confirmation before suppliers are added.
Customers choose the supplier contacts, documents and due date, then confirm the invitation. The app keeps a record of the exact questionnaire and documents each supplier received.
Estimated effort: Large. Brings invitations, supplier access and records of what was sent together.
Invited supplier contacts can work together, upload supporting files and return to unfinished answers. Customers see progress, but not answers or files that have not been submitted.
Estimated effort: Large. Handles shared answers, private working files and conflicting edits without losing work.
An authorized supplier contact signs and submits the completed response. The customer then reviews and approves it.
Estimated effort: Large. Coordinates signing, final checks, submission and customer review.
Suppliers can suggest teammates, while customers approve their access and decide who is allowed to sign.
Estimated effort: Medium. Adds approval of supplier teammates and separate permission to sign.
Suppliers can make customer-approved corrections without erasing the original response. The updated response needs a new signature and customer review.
Estimated effort: Medium. Adds approved corrections, new signatures and a record of earlier versions.
Customers can send an updated questionnaire to previous recipients. Earlier records stay available, and suppliers start new answers rather than carrying old answers into the changed questionnaire.
Estimated effort: Medium. Sends updated questionnaires without losing earlier responses or records.
Customers can add examples, explanations and upload instructions so suppliers understand what is being asked.
Estimated effort: Small. Adds question guidance while preserving the instructions already sent.
A supplier’s earlier answers determine which follow-up questions appear. Questions that do not apply are not treated as missing answers.
Estimated effort: Large. Adjusts follow-up questions as answers change, while keeping hidden answers private.
Customers can request clarification or additional evidence, set a due date, and review the supplier’s reply before closing the task.
Estimated effort: Medium. Adds follow-up tasks and replies, with the customer deciding when the work is complete.
Customers can download response summaries, answer spreadsheets and supporting files without exposing unfinished supplier work.
Estimated effort: Medium. Produces reports and evidence downloads without exposing private work.
Customers can set or extend deadlines, control reminders, and receive alerts when important work needs attention.
Estimated effort: Large. Keeps reminders and alerts aligned with whether suppliers have replied or more work is needed.
Customers can see when a response needs updating and confirm a new request. If the questionnaire is unchanged, previously approved answers can be reused with a new signature and customer review.
Estimated effort: Medium. Tracks when responses need updating and requires a new signature and review.
Customers can define their own grading approach and understand each result. Questionnaires can also remain information-only, without a score.
Estimated effort: Large. Adds customer-chosen rating rules and an explanation of each result.
Customers can review ratings, explain changes and choose to rate existing answers again using updated rules. Earlier results are kept.
Estimated effort: Medium. Adds reviewer decisions and updated ratings without changing earlier results.
Rules chosen by the customer suggest follow-up work for review. A person approves each task before it is sent to a supplier.
Estimated effort: Medium. Connects customer-set rules to follow-up suggestions that need approval.
A new review can link to related follow-up tasks already in progress. Finished tasks stay closed; any new work needs separate approval.
Estimated effort: Medium. Links related follow-up work without creating duplicate tasks or reopening finished ones.
Suppliers can create a step-by-step map of how cargo moves, including stops and handoffs. The customer reviews the submitted map.
Estimated effort: Large. Adds tools for creating cargo maps, saving drafts and reviewing them.
Suppliers can prepare changes privately and submit an updated map for review without losing earlier versions.
Estimated effort: Medium. Adds map updates and customer review while keeping earlier versions.
Customers can record concerns about locations or routes, along with supporting sources, dates and their reasoning.
Estimated effort: Medium. Adds research notes, supporting sources and a history of changes.
Customers bring questionnaires, cargo maps, concerns and follow-up work together. A reviewer records an overall assessment using the customer’s chosen method.
Estimated effort: Large. Combines several types of information for a reviewer’s overall assessment.
Customers can see newer information and decide whether another assessment is needed. Earlier conclusions remain unchanged.
Estimated effort: Medium. Shows newer information and supports another review without changing past decisions.
Customers can create or adapt inspection checklists, share them with suppliers and review completed inspection records.
Estimated effort: Large. Adds tools to create printable checklists and review completed inspection records.
The team will restore a separate copy of the app from backup. It will check that records, user access and supporting files are recovered without changing the working app.
Estimated effort: Large. Proves that the complete app, its records and original files can be safely recovered.
The full app will be checked against the agreed plan, including the steps customers and suppliers need to complete. It must pass final review before it is approved as complete.
Estimated effort: Large. Checks everyday customer and supplier use, ease of use and how much work the app can handle.
The stages show the planned order of work, not promised completion dates. The first sign-in and supplier-record work must be approved before questionnaire creation, team access or company and location setup can move forward.
These initial estimates compare the work in each task, including building and testing. They cover the whole task, including work already done, not just what remains.
Each estimate assumes the other features needed for that task are ready to use. Time waiting for access or approval is separate.
We do not yet have reliable completion dates because we are still gathering information about how long tasks take. Planning and work already done on unfinished tasks still count as progress.
Effort estimates reviewed .
What is blocking online testing and what still needs to be finished.
The development team needs permission to set up a secure online connection to the app. The person who manages the app’s hosting account needs to update the account permissions first.
Who needs to act Hosting account owner, then development team
The app must send working sign-in codes by email. The development team still needs to finish and test this before reviewers can sign in.
Who needs to act Development team
Confirm that a reviewer can sign in, add a supplier, leave and return to the saved information. This work can then be reviewed for final approval.
Who needs to act Development team and project owner
These records explain how the app’s features and review rules were chosen. Labels show which decisions were agreed, which plans are older and which research is not being pursued.
Defined the first product outline and the decisions needed before building.
Decision completedA broad competitor review was removed from the work required to finish the app. Existing research remains available as background.
Not proceedingThis broad research task is not being pursued as a separate part of the app project. It has not been marked as completed research.
Not proceedingDefined how customers prepare requests, suppliers answer them, and customers review the results.
Decision completedDefined who can see, edit, review and sign information, including the privacy of supplier drafts.
Decision completedDefined how responses can be corrected, when to request fresh information and how follow-up and reminders should work.
Decision completedRecorded the early development plan, which was later expanded into the full-app plan.
Decision completedKeeps the earlier questionnaire-focused plan for reference. The full-app plan below is the current plan.
Earlier planSets the agreed features for the complete app, including supplier questionnaires, cargo maps and overall assessments.
Current plan agreed