Import recurring close tasks cleanly
How to prepare spreadsheet rows so recurring close tasks keep ownership, review, timing, entity context, and capacity data.
A clean import is an operating decision
Importing the checklist is not just moving rows into software. It is the point where a recurring accounting process becomes explicit: who prepares the work, who reviews it, what evidence is expected, when it is due, and what other tasks depend on it.
If a task will repeat next close, give it enough structure now that the next cycle does not need manual cleanup.
Imported recurring tasks should start in TODO, preserve the correct entity or client, and include the owner-reviewer pairing that controls handoff quality.
Fields to clean before import
The best import files use the language already familiar to the team, but remove ambiguity from ownership, review, timing, and dependencies.
| Field | How to prepare it |
|---|---|
| Entity or client | Use recognizable names. Match existing entities where possible before creating new ones. |
| Task name | Make the expected accounting output clear enough that a preparer can act without guessing. |
| Assignee | Map the person preparing the work. Imported tasks should not launch without ownership. |
| Reviewer | Add the person accountable for sign-off. Review-required work should not skip this step. |
| Close day | Use a reusable close-day number so the task can roll forward cleanly in future cycles. |
| Estimate and tags | Capture expected hours, accounting area, and recurring context so capacity planning has useful data. |
| Prerequisites | Link upstream work when a task should not begin until another item is complete. |
Clean up the spreadsheet before upload
Most import problems come from inconsistent names, vague task labels, and missing reviewer assignments. Fix those before upload instead of expecting managers to repair every task after the first cycle starts.
- Standardize entity and client names.
- Separate preparer ownership from reviewer ownership.
- Replace vague due dates with close-day timing where possible.
- Mark tasks that require evidence before review.
- Identify recurring tasks that should roll forward into future cycles.
- Remove duplicate rows that represent the same close activity.
What to inspect after import
After importing, review the active cycle before inviting the full team. Look for missing owners, missing reviewers, tasks without timing, overloaded preparers, and critical dependencies that did not come through clearly.
Managers should also check whether imported work appears in the command center and whether review-required tasks enter the review workflow rather than jumping straight to completion.