Close Task Status, who owes what by when

A close has two heartbeats. Consolidation Status tells you whether the data is fresh; this one tells you whether the people are done. Task Manager holds the checklist, the owners, the deadlines, and the trail of when each thing happened.

Fifth page on the reports shelf of the FCCS reference. Older writing calls this Close Manager; it has been Task Manager everywhere in the product since early 2019, same machinery, and the whole reference is mapped on the FCCS index.

RuleRun the close from one schedule, deployed from a template, dependencies wired, alternates named. The dashboard becomes the status meeting, and the meeting gets shorter.

Nevertrack the close in a spreadsheet beside Task Manager. The two lists diverge by day three, and the audit trail ends up living in neither.

◆ How it runs— template to schedule to done, and the machinery underneath.

Piece	What it does
Templates	The month-end, quarter-end, and year-end checklists built once, tasks with owners, alternates, dependencies, and deadlines. A new period deploys the template and the schedule generates itself, the repeatability the spreadsheet never had.
The schedule opens	A deployed schedule sits Pending until someone sets it Open, and Open is what starts the clock. Assignees get email with a direct link to their task, provided an administrator enabled notifications, and integrated tasks open the exact consolidation or ERP screen where the work happens.
Alerts and reassignment	A blocked assignee raises an alert that lands with approvers; a bottleneck or an absence gets the task reassigned to the alternate. The manager's dashboard shows all of it live, overdue in red.
The trail	Every completion is timestamped, which turns last month's close into data: which tasks ran late, whose queue jammed, where the critical path really was. The close retro stops being opinions.

◆ Three fixes from the field— the recurring tickets, each with its documented cause.

Symptom	The cause, and the fix
Tasks stuck at Pending though the schedule looks ready	Two documented causes: the schedule itself is still Pending, not Open, or the task's responsibility was never selected. And when the responsibility field is greyed out and unselectable, the setting is missing back on the template. Open the schedule, set the responsibility, redeploy if needed.
An integrated task opens a 404 or a blank page	The connection URL is wrong in the connections setup, usually a mistyped or stale environment address. The task is fine; the door it opens is mislabeled.
Evidence added after completion	Raised as a governance question in the field: comments and files can still attach to a completed task while the schedule stays open, a risk window between the first task closing and the last. The mitigation is procedural, close the schedule promptly once the period signs off, and put reviewer sign-off after evidence, not before.

The close's real dashboard is both heartbeats read together: every entity OK on Consolidation Status, every task done here, and the journal list empty of drafts. In the owned warehouse, the star schema we recommend building beside FCCS on your own cloud, mapped here, task completion history lands beside the data, so close cycle time by task, by owner, by month is a trend line, not a memory. Mechanics, the rename, and all three cases verified against Oracle's documentation and support notes, July 2026.

Close retros running on opinions?

We land the task trail beside the numbers, and the retro opens with a chart: what ran late, what always runs late, and what to move.

Talk to us

Terms on this page

template: The close checklist built once, deployed every period.
Open: The schedule state that starts the clock. Pending starts nothing.
integrated task: A task that opens the exact screen where its work happens.
the two heartbeats: Data status and task status. The close is done when both say so.