Timecard Management Configuration
About 5% of the CIS-SPM exam — see all 10 domains.
Time Card Management captures time worked against tasks, projects, demands, problems, or other configurable targets in SPM and ITSM. Know the structure: a Time Sheet (weekly) contains Time Cards, and each time card holds hours by day. Time can be entered via the time sheet portal/UI and mobile time cards.
Approval & rollup. Time cards follow an approval workflow (Pending → Approved/Rejected); approved hours become actual effort/actual cost that roll up to project tasks and feed resource actuals and financials. Configuration covers time card policies (what can be billed to, rate type), time sheet periods, approver assignment, and auto-population of assigned tasks.
Sample questions from this domain
Three of the 15 in this domain, with the reasoning. The full set is in the question bank.
What is the primary purpose of Time Card Management in SPM?
- A. To allocate resources
- B. To capture actual time/effort worked by resources against tasks, projects, or other categories ✓
- C. To submit ideas
- D. To define currency
Why: Time Card Management records actual effort against work. It does not allocate resources, submit ideas, or define currency.
A Time Sheet Policy primarily governs:
- A. The functional currency rate
- B. The rules for time sheet periods, submission, approval, and which categories are allowed ✓
- C. The sprint cadence
- D. The WBS structure
Why: Time sheet policies define period length, submission/approval rules, and allowed categories. They do not set currency, sprints, or WBS.
Which period length is commonly configured for time sheets in SPM?
- A. Always exactly one fiscal year
- B. Per sprint only
- C. Per idea campaign
- D. Weekly (or other defined cadence) controlled by the time sheet policy ✓
Why: Time sheets typically use a weekly (or policy-defined) period set in the policy. They are not fixed to a fiscal year, sprints, or campaigns.