SharePoint Activity Tracker
Budget: $10 – $30 USD
I need a reusable SharePoint List (or an Excel template I can import) that lets me manage launch-readiness activities across multiple locations. To start I’ll be tracking 6-10 sites, but the structure must let me add the next wave without rebuilding anything.
List structure
• Master dashboard – one place that shows every Site Name, its overall Completion Status, and a link to that site’s detailed list.
• Site-specific lists – ten “weeks” per site: nine pre-launch (T-9 weeks, T-8 weeks, T-7 weeks, etc. until Go Live) and one post-launch. T-9 weeks also holds 3–4 Ticket Number fields. In every week I need a Script text column that teammates can copy into Slack, plus a “Complete” button (JSON-formatted column or Power Apps toggle—whatever is simplest) that rolls status up to the master view.
Key data points
• Site Name (drives lookup from master)
• Ticket Number(s) for Week 1
• Completion Status per week and overall
Organisation preference
Scripts and ticket info live in each site’s own list, while the master list aggregates progress.
Deliverables
1. Excel .xlsx (or .csv) ready for “Import to SharePoint List,” with all columns, choice sets and formatting in place.
2. Step-by-step instructions—screenshots or short Loom welcome—for importing the template, creating a new site list, and adding a fresh site to the master tracker.
3. JSON / Power Apps snippet that renders the “Complete” button and updates status.
4. Brief note on how to extend the template if week count changes later.
If anything here is unclear, let me know before you start—once this template is solid I can roll it out company-wide.
List structure
• Master dashboard – one place that shows every Site Name, its overall Completion Status, and a link to that site’s detailed list.
• Site-specific lists – ten “weeks” per site: nine pre-launch (T-9 weeks, T-8 weeks, T-7 weeks, etc. until Go Live) and one post-launch. T-9 weeks also holds 3–4 Ticket Number fields. In every week I need a Script text column that teammates can copy into Slack, plus a “Complete” button (JSON-formatted column or Power Apps toggle—whatever is simplest) that rolls status up to the master view.
Key data points
• Site Name (drives lookup from master)
• Ticket Number(s) for Week 1
• Completion Status per week and overall
Organisation preference
Scripts and ticket info live in each site’s own list, while the master list aggregates progress.
Deliverables
1. Excel .xlsx (or .csv) ready for “Import to SharePoint List,” with all columns, choice sets and formatting in place.
2. Step-by-step instructions—screenshots or short Loom welcome—for importing the template, creating a new site list, and adding a fresh site to the master tracker.
3. JSON / Power Apps snippet that renders the “Complete” button and updates status.
4. Brief note on how to extend the template if week count changes later.
If anything here is unclear, let me know before you start—once this template is solid I can roll it out company-wide.