Workflow Basics & Common Examples

Looking to create live, actionable, time-trackable, invoice-able Jobs in your system?  How you arrive to that live Job is flexible, with 2 main paths to get you there. Please review this article to learn more.  

Path 1: Estimate > Job

Path 1: Estimate > Job

One method for generating a new Job in your system is to begin with an Estimate. Once an Estimate is in place, you can use the "Add Job" button, to create the live piece of work.

Learn more: Best Practice - Adding an Estimate & Job

Path 2: Schedule > Estimate & Job

Path 2: Schedule > Estimate & Job

The other method for generating a new Job in your system is to begin with a Schedule. Once a Schedule is in place, you can use the "Add Estimate" button, to produce both the estimated value of the scheduled work, as well as generate the Job.

Learn more: Create an Estimate & Job from a Schedule

Flexible Options for Each Path

The FP system offers a great deal of flexibility regardless of which path (above) you choose. With modules such as Briefs, Projects and Tasks, you can choose to enhance your workflows. Please find some common examples below, but keep in mind that you can "stick to the basics" as well, and simply create estimates or schedules in order to generate live work. You are also not stuck with following the same workflow for every job you create.

Example 1

Example 1

In this example, you would begin with the completion of a Brief (requirements gathering document) within your FP system. From the Brief Details page, you would then create a Project - which is the ideal tool to organize multiple estimates and jobs. From the Project, you would create an Estimate, and turn that Estimate into a Job. From the Job, you would create a full Schedule (Task Tree), or create stand-alone Tasks. Staff members would track their time, and input any Job associated expenses. You would invoice the client based on values of your choosing (estimated or actual), and once the work is complete, the Job would be closed.

Example 2

Example 2

In this example, you would begin by selecting and editing an Estimate Template. That Estimate would be turned into a Job. From the Job, you would create a full Schedule (Task Tree), or create stand-alone Tasks. Staff members would track their time, and input any Job associated expenses. You would invoice the client based on values of your choosing (estimated or actual), and once the work is complete, the Job would be closed.

Example 3

Example 3

In this example, you would begin with your receipt of a completed Brief into your FP system, that was filled in by one of your clients, using the FP Portal. From the Brief Details page, you would add an Estimate, and then turned into a Job. From the Job, you would create a full Schedule (Task Tree), or create stand-alone Tasks. Staff members would track their time, and input any Job associated expenses. You would invoice the client based on values of your choosing (estimated or actual), and once the work is complete, the Job would be closed.

Example 4

Example 4

In this example, you would begin by creating a new Project. From the Project Details, you would add individual Estimates, and convert those into Jobs. As needed, you could complete and associate Briefs (Requirement Gathering Documents) that connect to this overall Project, or just to certain Estimates and Jobs. From any Job, you would create a full Schedule (Task Tree), or create stand-alone Tasks. Staff members would track their time, and input any Job associated expenses. You would invoice the client based on values of your choosing (estimated or actual), and could invoice on a job by job basis, or at the project level. As Jobs finish, you would mark them as closed, and then mark the Project as closed once all the work is done.

Example 5

Example 5

In this example, you would begin by creating a new Schedule, and converting that Schedule into an Estimate and Job. Before or after, you can also choose to add in a Brief (Requirements Gathering Document). Once you land the work, and the work begins, you can update the Schedule to move Tasks into active statuses, so that your team members know their calls to action on this Job. Staff members would track their time, and input any Job associated expenses. You would invoice the client based on values of your choosing (estimated or actual), and once the work is complete, the Job would be closed.

Example 6

Example 6

In this example, you would begin by selecting and editing a Schedule Template. Once you finish creating your Schedule, you would convert it into an Estimate and Job. Once you land the work, and the work begins, you can update the Schedule to move Tasks into active statuses, so that your team members know their calls to action on this Job. Staff members would track their time, and input any Job associated expenses. You would invoice the client based on values of your choosing (estimated or actual), and once the work is complete, the Job would be closed.

We welcome your questions or concerns: support@functionpoint.com

0 Comments

Add your comment

E-Mail me when someone replies to this comment