Illustrative idea · PUBLIC DATA
Refresh a regional indicator list
Bring a selected period of public country-level statistics into a shared team view.
Bring a public data file into a list your team can review.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
A published data file can provide useful information for a team’s shared spreadsheet. Retrieve the selected file, choose the records that meet the agreed country and reporting-period rules, create a stable way to recognize each row, and review the resulting updates.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
A public data fileA CSV available from a selected public source, containing country and reporting-week records
“Review the published testing data, keep records for Germany, Austria, and Switzerland from 2023, identify each country-week entry consistently, and add or update its spreadsheet row.”
Work through the request.
Clear tasks, with review where it matters.
- Confirm the public source and reporting scope
- Review the country and week fields
- Select the matching records
A spreadsheet updated with the selected 2023 country-week records, with a consistent matching value to help avoid repeated rows.
What this workflow could do
Helps a team bring a defined slice of publicly available tabular information into a spreadsheet for review and use.
Review points proposed in this idea
Public data can change, omit context, or arrive in an unfamiliar format. Confirm the source and reporting period, check country and week values, and review the resulting row count before relying on the spreadsheet.
How the idea could work
Select an illustrative task to explore its proposed role. No workflow runs here.
-
Check that the selected file is the intended testing dataset and that the team needs 2023 records for the three agreed countries.
-
Make sure country identifiers and reporting weeks are clear enough to apply the team’s selection rule.
-
Keep entries for Germany, Austria, and Switzerland within the 2023 reporting period and set aside other rows.
-
Use a consistent country-and-week identity to find an existing entry or determine that a row is new.
-
Add new entries or refresh their existing rows, then review a sample and the total number of selected records.
Step 1 of 5
Confirm the public source and reporting scope
Check that the selected file is the intended testing dataset and that the team needs 2023 records for the three agreed countries.
Proposed setup considerations
These are planning notes for the concept, not instructions for a currently available template.
- 01
Select the public file and destination spreadsheet
Choose the source maintained for this data and the shared sheet where approved records should appear.
- 02
Set country, year, and record identity rules
Document which countries and reporting weeks are in scope and how each country-week row is recognized.
- 03
Decide how new and existing rows are handled
Specify which spreadsheet fields may be updated and how records outside the selected scope are left alone.
- 04
Review a sample and its record count
Check records near the period boundary, confirm the country selection, and compare the result with the source before using it.
Read the prelaunch status
Published templates and verified customer availability remain pending.
A little help with the whole task
A little less busywork.
A little less busywork.
A little more room for you.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation