Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
2Activity
0 of .
Results for:
No results containing your search query
P. 1
19Early Detection - Two Methods

19Early Detection - Two Methods

Ratings: (0)|Views: 13 |Likes:
Published by SRED Unlimited
Bruce Madole discusses two ways you can identify SR&ED claimable activities as they happen, so that you have better control over documenting them and proving that they occurred.
Bruce Madole discusses two ways you can identify SR&ED claimable activities as they happen, so that you have better control over documenting them and proving that they occurred.

More info:

Categories:Types, Brochures
Published by: SRED Unlimited on Dec 28, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

05/12/2014

pdf

text

original

 
Copyright 2010 Bruce MadoleEarly Detection of SR&ED
Early Detection of SR&ED: Two Methods
Detecting a possible SR&ED project early can gain you serious advantages in aquest to maximize your claims. (Of course, the very earliest method of “detection” is to plan a project as SR&ED, from the outset, and then proceed with it.) It all depends onwhether you are organized enough to take advantage of the opportunity. Here are twomethods you could use to detect a possible SR&ED project:
technology pain points
and
technology gap analysis
.
Technology Pain Points:
Look at your current project list and your list, if youhave one, of the technical problems, barriers or issues that you have been encountering.By a
technology pain point 
, I mean a technical problem that is impacting either your current operations, and individual project, or your attempts to achieve performanceimprovements or new and enhanced products or services. These are not just things thatmake you go “hmmm…” – these are also the things that make you smite yourself on theforehead and say “O God not that again” … or words to that effect. If you have none of these, then you are probably a happier person than some other people, and we can moveon to method number two, which is related.
Technology gap analysis
involves an attempt to foresee, in any project or productdevelopment effort you are planning or currently working on, a circumstance in whichthere is a gap between the known, existing capabilities of your current technologies, andwhere you need them to be in order to reach your performance and quality goals. It’s allabout the gap – from here, to there – and the recognition that all the hard work or thinking and investigation that you may have to do to move from one state to the other,
This document is the property of Bruce Madole, and is used by permission. All rights are reserved. The opinions expressed herein are personal, created for entertainment andinformation purposes, and are not intended to be relied on in place of professional counsel or advice. No part of this document may be re-used, transmitted or re-transmittedwithout the express prior written consent of the author, who can be contacted at: brucemadole@sympatico.ca 

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->