CONNECTED WORKFLOW

From approved time to project cost

Understand when submitted hours become actual effort and financial input.

Example companyMC
◫▤◎▥
Time reviewIllustrative view
Review project timeApproval-required example
EntryHoursReview state
Design validation · Maya10.0Approved
Design validation · Maya3.5Pending
Submitted13.5 hApproved + awaiting review
Counts as actual10.0 hPending time is excluded
Corrections keep their context

A correction records a reason and revision. Corrected approved time returns to review under an approval-required policy.

Illustrative workflow · sample data
01

Submit own time

Choose one project task or company To-Do, work date and hours. Company policy controls the daily cap and review requirements.

02

Review the entry

When approval is required, pending and rejected time is excluded from approved actuals.

03

Read the project effect

Approved project hours contribute to actual labor cost through the configured task cost rate.

04

Correct with context

A correction requires a reason. Under approval-required policy, corrected hours need review again before counting.

A useful distinction

Company To-Do time updates company effort, not project financial cost. Discuss any payroll or accounting integration requirements separately.

MAKE THE CONNECTION

Start with the way
your company works.

Bring a real workflow to the conversation.
We’ll explore where MCT Orbit fits.

Request your walkthrough Have a specific question? Get in touch →