Turn scattered requests into a useful tracker
Request: “We're tracking customer requests in this page and things keep getting lost. Set up a simple tracker so we can see what needs attention, who is handling it, and what is done. Keep the information we already have.”
Read the supplied page and follow links to an existing tracker before creating one. Suppose there is none, and the page contains three requests: an export issue Lee is investigating, a new invoice request with no owner, and a resolved login issue. The invoice request appears again in the next meeting's notes.
Create one tracker in the requested location with a request title, progress, and owner. Carry over the three distinct requests, retaining their details and links to the notes. The repeated invoice request becomes one record with both source links. Leave its owner unset; do not invent deadlines or sample work.
Choose views that answer the user's questions: requests needing attention, open work grouped by owner, and completed requests. Keep useful context in each request's page rather than adding a property for every detail. Preserve the original notes. If the connection cannot create the views, explain what was built and give the remaining setup steps.
Verify that the unresolved invoice request is visible, Lee's work has the right owner, and the resolved issue is separated from open work. Return the tracker link with a short explanation of where to start. The user now has a place to see and manage requests without having to design a database themselves.